mcps

Sync MCP server configs across agent harnesses. One manifest, all clients stay in sync.

The problem

When using multiple AI agent clients (Claude Code, IBM Bob, etc.), each one stores MCP server config separately. mcps keeps a single source of truth at ~/.mcp/servers.json and syncs it to every client.

Install

npm install -g @andyaaz/mcps

Quick start

# Add a server to your manifest
mcps add my-server node /path/to/server.js

# Sync to all detected clients
mcps sync

Commands

Add / remove servers

mcps add <name> <command> [args...]       # stdio server
mcps add <name> --type http --url <url>   # HTTP server
mcps remove <name>
mcps list

Sync manifest → clients

mcps sync                               # all detected clients
mcps sync --client claude-code          # one client only
mcps sync --scope user                  # user-level only
mcps sync --scope project               # project-level only

Import from an existing client

mcps import --from claude-code          # read ~/.claude.json → merge into manifest
mcps import --from bob                  # read ~/.bob/mcp.json → merge into manifest

After importing, run mcps sync to push to other clients.

Supported clients

| Client | Project config | User config | |---|---|---| | claude-code | .mcp.json | ~/.claude.json (mcpServers key) | | bob | .bob/mcp.json | ~/.bob/mcp.json |

Manifest

~/.mcp/servers.json — uses the standard mcpServers schema:

{
  "mcpServers": {
    "my-server": {
      "command": "node",
      "args": ["server.js"],
      "env": { "API_KEY": "..." }
    }
  }
}