arete-mcp

One CLI to discover, health-check, and sync MCP servers across Claude Code, Cursor, Windsurf, and more.

---

The Problem

You use Claude Code, Cursor, and Windsurf. Each stores MCP servers in a different JSON file with a different schema.

~/.claude.json
~/.cursor/mcp.json
~/.windsurf/mcp_config.json

Your team can't share configs via git. Switching projects means manual copy-paste. One IDE has a server the others don't. You have no idea which servers are actually healthy.

mcp-manager gives you one CLI — and one .mcp-manager.yml in your repo — to rule them all.

---

30-Second Quickstart

# Install
pip install arete-mcp

# See every MCP server across every IDE
mcp-manager list

# Check if they actually work (not just "starts")
mcp-manager health --deep

# Scaffold a project config
mcp-manager project init

# Sync it to Cursor (dry-run first, then commit)
mcp-manager sync --ide cursor --dry-run
mcp-manager sync --ide cursor

---

What Makes This Different

	arete-mcp	Other Managers
Config lives in repo	✅ .mcp-manager.yml committed with your code	❌ Global per-IDE JSON files
Atomic write-back	✅ Backups + dry-run before touching IDE configs	❌ Direct overwrite, no rollback
Deep health checks	✅ Verifies tools/list responds, deps on PATH	❌ "Process started" only
Zero daemon	✅ CLI-only, no background services	❌ Some require persistent gateway/web UI
Python-native	✅ pip install, works wherever Python 3.11+ does	❌ Node/Go binaries, extra tooling
Cross-IDE discovery	✅ Reads Claude, Cursor, Windsurf, project-level .mcp.json	⚠️ Partial coverage

---

Features

🔍 Discovery

Reads MCP server configs from:

• Claude Code (~/.claude.json)
• Claude Desktop (~/.config/Claude/claude_desktop_config.json)
• Cursor (~/.cursor/mcp.json)
• Windsurf (~/.windsurf/mcp_config.json)
• Project-level (.mcp.json, walks parent dirs)

🏥 Health Checks

• Fast: Process spawn (stdio) or HTTP ping (SSE) — 10s timeout
• Deep: Dependency validation (node, python, docker on PATH) + verify tools/list returns non-empty
• Batch: Check all servers in parallel with mcp-manager health

📝 Config Write-Back (Atomic & Safe)

• Writes discovered/merged configs back to IDE-specific JSON files
• Atomic: temp file + rename (never corrupts your IDE config)
• Backups: .mcp-manager-backup created before any modification
• Dry-run: Preview changes without touching disk

🏪 Server Marketplace

Discover and install curated MCP servers without hunting through GitHub:

# Search for servers by name or category
mcp-manager search filesystem
mcp-manager search --category Database

# View details before installing
mcp-manager info postgres

# Add a server to your project config (interactive env var prompts)
mcp-manager install postgres
mcp-manager install slack --no-prompt  # skip prompts, keep ${VAR} placeholders

Shipped with 6 official MCP reference servers. Verified servers are shown by default; use --include-unverified to browse the full catalog.

📁 Project-Scoped Configs

Create .mcp-manager.yml in any repo root:

project: my-service
servers:
  postgres-local:
    command: node
    args: ["./mcp/postgres-server/dist/index.js"]
    env:
      DATABASE_URL: ${DATABASE_URL}
  stripe-mcp:
    command: npx
    args: ["-y", "@stripe/mcp"]
    env:
      STRIPE_SECRET_KEY: ${STRIPE_SECRET_KEY}

• Environment variables (${VAR}) resolved at load time
• Validated before write-back (missing env vars or commands caught early)
• Project config wins on merge conflicts with global registry

🔐 Version Pinning (Lockfile)

Pin exact MCP server versions for reproducible CI and team consistency:

mcp-manager lock                    # Resolve and write .mcp-manager.lock
mcp-manager lock --check            # Validate lockfile is current (CI gate)
mcp-manager lock --json             # Output resolved versions as JSON

The lockfile records the resolved npm version for each npx-based server so every developer and CI runner uses identical tooling.

🔄 Export / Import

Portable YAML/JSON for backup, sharing, and CI:

mcp-manager export servers.yaml
mcp-manager import servers.yaml

🖥️ Server Monitor (Auto-Restart)

Keep stdio MCP servers alive in development:

mcp-manager monitor --project .

• Watches server processes and restarts on crash
• Exponential backoff (1s → 2s → 4s ... max 30s)
• Graceful shutdown on Ctrl+C / SIGTERM
• JSON status output: mcp-manager monitor --json

🔒 CI Gate / GitHub Action

Validate .mcp-manager.yml on every PR:

# .github/workflows/mcp-validate.yml
- uses: AreteDriver/mcp-manager/.github/actions/mcp-manager-validate@main
  with:
    path: "."
    strict: "false"

Catches missing env vars, broken commands, and (with --strict) failing servers before merge.

---

Usage

# List all MCP servers across all IDEs
mcp-manager list

# Filter by IDE
mcp-manager list --tool cursor

# Health check all servers
mcp-manager health

# Deep health check — validate dependencies and verify tools/list
mcp-manager health --deep

# Show server-to-IDE mapping
mcp-manager map

# Search and install from the marketplace
mcp-manager search filesystem
mcp-manager info postgres
mcp-manager install postgres

# Export/import configs (portable YAML/JSON)
mcp-manager export servers.yaml
mcp-manager import servers.yaml

# Add/remove servers from the registry
mcp-manager add my-server --command "node server.js"
mcp-manager remove my-server

# Sync project config to IDE
mcp-manager sync --ide cursor --dry-run
mcp-manager sync --ide cursor

# Project-level MCP config
mcp-manager project init              # Scaffold .mcp-manager.yml
mcp-manager project validate          # Check env vars, commands on PATH
mcp-manager project export --ide cursor

# Keep stdio servers alive with auto-restart
mcp-manager monitor                   # Foreground monitor, Ctrl+C to stop

# CI gate — validate .mcp-manager.yml in CI
mcp-manager validate                  # Fast validation
mcp-manager validate --strict         # + deep health checks on all servers

# Lockfile — pin exact versions
mcp-manager lock                      # Resolve and write .mcp-manager.lock
mcp-manager lock --check            # Validate lockfile is current (CI gate)

---

Supported IDEs

IDE	Config Path	Write-Back
Claude Code	~/.claude.json	✅
Claude Desktop	~/.config/Claude/claude_desktop_config.json	✅
Cursor	~/.cursor/mcp.json	✅
Windsurf	~/.windsurf/mcp_config.json	✅
Project-level	.mcp.json (walks parent dirs)	✅

---

Transport Types

• stdio — local subprocess, JSON-RPC over stdin/stdout
• sse — Server-Sent Events over HTTP
• http — HTTP POST JSON-RPC

---

Status

• Read-only config discovery across 5 IDE configs
• Async health checks with timeout
• JSON registry with add/remove
• YAML/JSON export/import
• Protocol handshake testing
• Config write-back (atomic, with backups)
• Project-scoped .mcp-manager.yml support
• Deep health checks (dependency validation + tools/list verification)
• Server auto-restart monitor
• CI gate (mcp-manager validate + GitHub Action)
• Version pinning lockfile (mcp-manager lock --check)
• Server marketplace / remote registry

See ROADMAP.md for what's next.

---

Contributing

git clone https://github.com/AreteDriver/mcp-manager.git
cd mcp-manager
python -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"

Preflight Checklist (required before PR)

# 1. Linting & formatting
ruff check .
ruff format --check

# 2. Type checking
mypy src/mcp_manager

# 3. Tests with coverage (must be ≥80%)
pytest --cov=mcp_manager --cov-fail-under=80

# 4. Security audit
pip-audit

CI enforces all of the above. PRs that fail any gate will not merge.

---

Discord — Join the community

Part of the AreteDriver AI tooling ecosystem.