Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/neon-solutions/add-mcp/llms.txt

Use this file to discover all available pages before exploring further.

The sync command (also available as unify) inspects all detected agent configuration files and ensures that every MCP server is consistently named and present across all agents. It groups servers by their URL or package identity, picks a canonical name for each group, renames outliers, and adds the server to any agents that are missing it.

​
Usage

npx add-mcp sync [options]
npx add-mcp unify [options]
unify is a full alias for sync — both subcommands behave identically.

​
Options

​
-g, --global
flag
Sync global (user-level) config files instead of the project-level configs in the current directory.
​
-y, --yes
flag
Apply the sync plan without asking for confirmation. The plan is still printed to the terminal before changes are made.

​
How sync works

  1. Group by identity — servers across all detected agents are grouped by their URL (remote) or package name (stdio). Each group represents one logical MCP server.
  2. Pick a canonical name — within each group, the shortest server name is chosen as the canonical name. Ties are broken by frequency (most-used name wins) and then alphabetically.
  3. Build a sync plan with three categories:
    • Renames — agents that have the server under a non-canonical name.
    • Additions — agents that are detected but missing this server entirely.
    • Skipped (conflicts) — groups where headers, env vars, or args differ across agents. These are skipped with a warning rather than silently overwriting config.
  4. Apply the plan — canonical entries are written first (renames and additions), then old aliases are deleted.
At least two detected agents are required for sync to run. If only one agent is detected, the CLI exits with an informational message.
Servers with conflicting configuration (different headers, environment variables, or arguments across agents) are skipped entirely and listed under “Skipped (conflicts)” in the sync plan. Review the conflict reason and reconcile the differences manually before re-running sync.

​
Sync plan display

Before applying any changes, sync prints a plan similar to this: 
┌─ Sync Plan ──────────────────────────────────────────────────┐
│ Renames:                                                      │
│   Cursor: ctx7 → context7                                     │
│                                                               │
│ Additions:                                                     │
│   Claude Code: + context7 (https://mcp.context7.com/mcp)     │
│                                                               │
│ Skipped (conflicts):                                          │
│   https://mcp.example.com/mcp: headers differ between        │
│   Cursor and VS Code                                          │
└───────────────────────────────────────────────────────────────┘
In interactive mode you are then asked to confirm before changes are written. Pass -y to skip the confirmation prompt. If there is nothing to do (all servers are already in sync), the CLI reports that and exits cleanly.

​
Examples

npx add-mcp sync
Run npx add-mcp list first to understand the current state of your agent configs before running sync. This makes it easier to predict what the sync plan will contain.

Build docs developers (and LLMs) love

Get started for freeTalk to us