Stats
Actions
Tags
From sync-agent-config
Synchronize MCP (Model Context Protocol) server settings across different Agent tools. Use when you want to copy, apply, or sync MCP settings between multiple Agent environments like Claude Code, VSCode, Cursor, Claude Desktop, Codex, and Gemini CLI. Supports both full synchronization and selective synchronization of specific MCP servers.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sync-agent-config:sync-mcp-configThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides procedures for synchronizing MCP server settings across different Agent tool environments.
This skill provides procedures for synchronizing MCP server settings across different Agent tool environments.
MCP settings can exist at different scopes depending on the Agent tool:
| Agent Tool | Global (User-Level) | Project-Level |
|---|---|---|
| Claude Code | ~/.claude.json | .mcp.json |
| VS Code | User mcp.json | .vscode/mcp.json |
| Cursor | User mcp.json | .cursor/mcp.json |
| Gemini CLI | ~/.gemini/settings.json | .gemini/settings.json |
| Claude Desktop | ✅ Supported | ❌ Not Supported |
| Codex CLI | ✅ Supported | ❌ Not Supported |
| Antigravity | ✅ Supported | ❌ Not Supported |
When synchronizing settings, consider:
If the target Agent tool does not support project-level configuration, only global synchronization is possible.
Synchronize all MCP servers from the source to the target Agent tool.
Synchronize only specified MCP servers from the source to the target Agent tool. Users can specify:
filesystem)filesystem, github, slack)This is useful when:
Delete specified MCP servers from the target Agent tool's configuration. Users can specify:
filesystem)filesystem, github, slack)This is useful when:
Important: This operation does not require a source Agent tool - it operates directly on the target configuration.
Before starting the synchronization process, verify the current operating system environment using the Bash tool or by checking environment variables. This is important because:
\, Unix-like systems use /)Use appropriate methods to determine:
Before proceeding, confirm with the user using the AskUserQuestion tool:
For selective synchronization, present the list of available MCP servers from the source and confirm which servers to synchronize. For selective deletion, present the list of existing MCP servers in the target and confirm which servers to delete.
Since MCP configuration methods may vary depending on the Agent tool, first verify and understand the specifications of the MCP configuration files for both the source and target Agent tools.
Refer to the md documents in the following directory for specifications:
Available references:
If reference documentation is not available for the target Agent tool:
Read the configuration file containing the MCP server settings of the source Agent tool and check available MCP servers. The configuration includes the following information:
For selective synchronization, present the list of available MCP servers to the user and confirm which servers to synchronize.
Read the target Agent tool's MCP configuration file and apply the changes based on the operation mode.
After making changes, validate that the configuration file has no issues.
In the following cases, notify the user and stop processing:
In the following cases, use tools as necessary to handle the situation:
The target configuration file does not exist. Create a new target configuration file. (use Bash tool if necessary)
The MCP server settings are incompatible between the source and target Agent tools. Since configuration file formats and element names may differ, verify the specifications of both source and target, and rewrite the format so that the MCP server settings content remains the same. If there are unclear points, perform web searches to verify specifications. (use WebSearch WebFetch tool if necessary)
The following actions are prohibited when managing MCP server settings:
Example 1: "I want to apply Claude Code's MCP settings to Codex" (Full Synchronization)
Example 2: "Sync only the 'filesystem' and 'github' MCP servers from Claude Code to VS Code" (Selective Synchronization)
Example 3: "Add the 'slack' MCP server from Cursor to Claude Desktop"
Example 4: "Sync project-level MCP settings from VS Code to Cursor"
.vscode/mcp.json file.cursor/mcp.json fileExample 5: "Delete the 'filesystem' MCP server from Claude Code" (Selective Deletion)
Example 6: "Remove the 'github' and 'slack' MCP servers from VS Code's global settings"
Example 7: "Clean up unused MCP servers from Cursor"
npx claudepluginhub zv-louis/zv-plugin-marketplace --plugin sync-agent-configSearches, installs, configures, updates, and removes MCP servers across many coding agents (Claude Code, VS Code, Cursor, etc.). Supports npx add-mcp, the official registry, and direct config editing.
Manages Model Context Protocol (MCP) servers for Claude Code projects: installs/configures .mcp.json, OAuth remotes, runtime enable/disable, troubleshooting connections.
Configures MCP servers for Claude Code at project or user scope with best practices to prevent context pollution. Checks status, adds/removes servers via .mcp.json or ~/.claude.json.