Mcpgo
Turns Claude Code's MCP management into a conversational interface by exposing list, add, remove, and restart operations as tools. The real trick is the wrapper mode: it sits between Claude Code and your stdio MCPs, auto-respawning crashed processes without breaking the parent connection. That means you can restart a flaky MCP mid-session by just asking Claude to do it, no `/mcp` panel needed. Especially handy in Remote Control mode where the UI isn't available. Also handles Codex CLI configs. Setup requires a one-time wrap per server and a Claude Code restart, after which restarts are instant and transparent.
- tools
- 11
- transport
- STDIO
- last updated
- May 20, 2026
Tools
11 toolsPublic tool metadata for what this MCP can expose to an agent.
wrap_mcp_stdioWrap a Claude Code stdio MCP for reliable restarts.
Wrap a Claude Code stdio MCP for reliable restarts.
No parameter schema in public metadata yet.
unwrap_mcp_stdioRestore a wrapped MCP to its original config.
Restore a wrapped MCP to its original config.
No parameter schema in public metadata yet.
restart_mcp_processRestart a wrapped MCP's child process — wrapper auto-respawns it, Claude Code stays connected.
Restart a wrapped MCP's child process — wrapper auto-respawns it, Claude Code stays connected.
No parameter schema in public metadata yet.
check_mcp_healthCheck if an MCP is configured, wrapped, and its process is running.
Check if an MCP is configured, wrapped, and its process is running.
No parameter schema in public metadata yet.
wrap_codex_mcp_stdioWrap a Codex CLI MCP from `~/.codex/config.toml`.
Wrap a Codex CLI MCP from `~/.codex/config.toml`.
No parameter schema in public metadata yet.
restart_codex_mcp_processRestart a wrapped Codex CLI MCP.
Restart a wrapped Codex CLI MCP.
No parameter schema in public metadata yet.
list_all_mcpsList all configured MCP servers.
List all configured MCP servers.
No parameter schema in public metadata yet.
add_mcpAdd a new MCP server to `~/.claude.json`.
Add a new MCP server to `~/.claude.json`.
No parameter schema in public metadata yet.
remove_mcpRemove an MCP server.
Remove an MCP server.
No parameter schema in public metadata yet.
configure_mcpUpdate an existing MCP server's config fields.
Update an existing MCP server's config fields.
No parameter schema in public metadata yet.
get_mcp_detailsGet full config details for a specific MCP.
Get full config details for a specific MCP.
No parameter schema in public metadata yet.
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageReadme
mcpgo
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.
Installation
npm install -g @exfil/mcpgo
claude mcp add mcpgo --scope user -- mcpgo
Requirements: Node.js ≥ 18
Remote Control
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.
What it does
Reliable restarts
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.
Details
- Repository
- github.com/jschoemaker/mcpgo
- Package
@exfil/mcpgo- Transport
- STDIO
- Registry
- MCP registry, active