ln-004-agent-config-sync

Syncing MCP servers from Claude Code to Gemini and Codex involves a non-destructive merge that aligns configurations across all three tools. The process creates backups before writing and converts between JSON and TOML formats to ensure each CLI receives compatible configuration data.

Yes, you can synchronize skill symlinks across Claude, Gemini, and Codex. The sync process aligns symlinks from Claude Code to Gemini CLI and Codex CLI, ensuring consistent plugin and skill environments while eliminating configuration drift between the tools.

Syncing MCP settings between Claude, Gemini, and Codex supports cross-tool JSON and TOML conversion. The synchronization process automatically translates configuration formats as needed, ensuring each CLI receives properly formatted MCP server data during the non-destructive merge.

The best way to back up MCP configurations before migrating to Gemini CLI is to use a sync tool with built-in backup functionality. The agent-config-sync process automatically creates backups before writing any changes, ensuring your original Claude Code settings remain safe during the non-destructive merge.

Yes, you can do a dry run before syncing MCP plugins across Claude and Codex. The synchronization process supports dry-run planning, allowing you to preview how MCP server configurations and skill symlinks will be merged before any actual changes are written to your environments.

You should use cross-tool MCP configuration sync instead of manual setup during MCP changes, plugin installations, or initial Gemini CLI and Codex CLI setup alongside Claude Code. It eliminates configuration drift and ensures consistent environments without the risk of manual formatting errors.