Mcpgo MCP Server

Manage your Claude Code MCPs by talking to Claude — list, restart, wrap, and more. That is what the mcpgo mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The tools it exposes

The server publishes 11 tools. What each one is for:

• wrap_mcp_stdio — Wrap a Claude Code stdio MCP for reliable restarts. "wrap github" "wrap postgres"
• unwrap_mcp_stdio — Restore a wrapped MCP to its original config. "unwrap github" "unwrap postgres"
• restart_mcp_process — Restart a wrapped MCP's child process — wrapper auto-respawns it, Claude Code stays connected. "restart github" "restart postgres"
• check_mcp_health — Check if an MCP is configured, wrapped, and its process is running. "check github health" "is postgres running?"
• wrap_codex_mcp_stdio — Wrap a Codex CLI MCP from ~/.codex/config.toml. "wrap my codex mcp called postgres"
• restart_codex_mcp_process — Restart a wrapped Codex CLI MCP. "restart the codex postgres"
• list_all_mcps — List all configured MCP servers. "list my mcps" "what mcps do I have?"
• add_mcp — Add a new MCP server to ~/.claude.json. "add an mcp called my-tool that runs python server.py"
• remove_mcp — The remove_mcp tool exposed by this server
• configure_mcp — Update an existing MCP server's config fields. "change github's command to python3"
• get_mcp_details — Get full config details for a specific MCP. "show me the github config" "get details for postgres"

Getting it running

cache on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Mcpgo's toolset — wrap_mcp_stdio, unwrap_mcp_stdio, restart_mcp_process and 8 more — is a fair guide to whether it matches your workflow. It is maintained by jschoemaker; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Mcpgo.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.