Discover, monitor, and manage MCP servers across agentic IDEs.
MCP servers are configured per-IDE in different JSON files with different schemas. If you use Claude Code, Cursor, and Windsurf, your servers are scattered across three configs with no unified view.
mcp-manager gives you one CLI to see, health-check, and manage all of them.
pip install mcp-manager# 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
# Show server-to-IDE mapping
mcp-manager map
# 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| IDE | Config Path |
|---|---|
| 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) |
- stdio — local subprocess, JSON-RPC over stdin/stdout
- sse — Server-Sent Events over HTTP
- http — HTTP POST JSON-RPC
- 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 (edit IDE configs directly)
- Server auto-restart on failure
Discord — Join the community
Part of the AreteDriver AI tooling ecosystem.