Install one MCP server across Claude Code, Cursor, Codex, and VS Code without manual config edits
<p>Use add-mcp when an agent needs to roll out, list, remove, or synchronize MCP server configs across multiple coding clients instead of hand-editing each config file separately.</p>
<p>Use add-mcp when an agent needs to roll out, list, remove, or synchronize MCP server configs across multiple coding clients instead of hand-editing each config file separately.</p>
npx skills add agentskillexchange/skills --skill install-one-mcp-server-across-claude-code-cursor-codex-and-vs-code-without-manual-config-edits
This skill is for the repetitive setup work around MCP adoption. An agent can install a remote MCP URL or local package into the right config files for supported clients, add required headers or environment variables, list what is already installed, remove stale entries, and synchronize server naming across tools. It is most useful when onboarding a server to several clients at once, standardizing team setup, or cleaning up drift between project and global configs.
The boundary is tight enough to be skill-shaped: the job is MCP configuration rollout and synchronization across agent clients. It is not a registry platform card, not an MCP server listing, and not a generic developer-tools bundle. Invoke it when the pain is manual config editing and config drift across clients, not when you need to build or host the server itself.