jschoemaker/mcpgo
MCP server that manages your other MCP servers — wrap, restart, add, remove, and health check from within your CLI.
Platform-specific configuration:
{
"mcpServers": {
"mcpgo": {
"command": "npx",
"args": [
"-y",
"mcpgo"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
Manage your Claude Code MCPs by talking to Claude — list, restart, wrap, and more.
Works everywhere Claude Code works, including Remote Control where /mcp isn't available.
npm install -g @exfil/mcpgo
claude mcp add mcpgo --scope user -- mcpgoRequirements: Node.js ≥ 18
Claude Code's Remote Control mode has no access to /mcp. That means you can't list, restart, or manage MCP servers remotely — unless you have mcpgo.
Because mcpgo is itself an MCP server, it's available everywhere Claude Code is:
"list my mcps"
"restart github"
"check postgres health"No /mcp UI needed.
Claude Code connects to stdio MCP servers via pipes it creates at launch. If a server crashes or you want to restart it, Claude Code marks it as failed with no auto-recovery.
mcpgo solves this with a wrapper: a long-lived process that sits between Claude Code and your MCP. Claude Code talks to the wrapper (which stays alive), and the wrapper spawns the real server as a child — auto-respawning it whenever it's killed.
Wrapping is optional — you can use mcpgo just for listing, adding, or removing MCPs without wrapping anything. Wrapping is only needed if you want reliable restarts without touching /mcp.
One-time setup per MCP:
wrap_mcp_stdio — wraps the target MCP in config/mcp)restart_mcp_process anytimeAfter setup:
"restart github" → instant, wrapper auto-respawns the child, Claude Code stays connected
"restart postgres" → sameIf you ever want to undo wrapping, use unwrap_mcp_stdio to restore the original config.
wrap_mcp_stdioWrap a Claude Code stdio MCP for reliable restarts.
"wrap github"
"wrap postgres"unwrap_mcp_stdioRestore a wrapped MCP to its original config.
"unwrap github"
"unwrap Loading reviews...