sync-mcp-config

Synchronize MCP server configurations across multiple Agent tools.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/zv-louis/sync-mcp-config --skill sync-mcp-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-mcp-config
Source: https://github.com/zv-louis/sync-mcp-config/tree/main/sync-mcp-config
Command: npx skills add https://github.com/zv-louis/sync-mcp-config --skill sync-mcp-config

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the manual, error-prone work of keeping MCP server configurations in sync across Claude Code, VSCode, Claude Desktop, Codex, and Gemini CLI, saving time and reducing drift.

Core Features & Use Cases

  • Cross-Tool Synchronization: Read from a source tool's MCP config and apply to a target tool.
  • Safety First: Backups and validation before applying changes.
  • Format Conversion: Automatically maps MCP formats between tools.

Quick Start

Use this skill to synchronize MCP servers from Claude Code to Codex, ensuring both environments have identical server lists and settings.

Frequently Asked Questions about sync-mcp-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I synchronize MCP server configurations across Claude Code, VSCode, and other tools?

Synchronizing MCP server configurations across tools eliminates manual duplication. This Skill reads your source tool's MCP settings and applies them to target environments like VSCode, Claude Desktop, Codex CLI, and Gemini CLI, automatically converting formats and validating integrity before changes take effect.

Can I keep my MCP configurations in sync without manual updates?

Yes. Rather than manually updating each tool's MCP config separately, this Skill automates cross-tool synchronization, handling format conversion and OS-specific paths so all your environments stay aligned without drift or repetitive work.

What happens to my existing MCP settings when I sync configurations across tools?

The Skill creates backups before applying changes and validates configuration integrity across tools. This safety-first approach protects your existing settings while preventing conflicts during synchronization across Claude Code, VSCode, Claude Desktop, Codex, and Gemini CLI.

Does this work with different MCP configuration formats across tools?

Yes. The Skill automatically maps and converts MCP formats between different tools, so configurations from Claude Code translate correctly into VSCode's format, Codex CLI's structure, and other environments without manual reformatting.

Can I use this Skill if I work across multiple development environments?

Absolutely. If you use Claude Code, VSCode, Claude Desktop, Codex, or Gemini CLI together, this Skill synchronizes your MCP server settings across all of them, handling OS-specific paths and maintaining consistency regardless of your platform or tool combination.

What if there are conflicts when syncing MCP settings between tools?

The Skill includes conflict detection and resolution during synchronization. Backups are created before applying changes, and validation runs to catch issues, so you can safely resolve conflicts without losing your original configurations.