Mcpgo MCP server

by jschoemaker·io.github.jschoemaker/mcpgo·v0.1.6

No reviews yet

Manage your Claude Code MCPs by talking to Claude — list, restart, wrap, and more.

B82/100grade B

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

B82/100

full report

Adoption

New

0 stars55 downloads/wk

Reviews

Write one

Nobody has reviewed Mcpgo yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Mcpgo tools (11, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

add_mcp
Add a new MCP server to the user configuration (~/.claude.json).
check_mcp_health
Check the health of an MCP server — whether it is configured, wrapped, and its process is running.
configure_mcpwrite action
Update the configuration of an existing MCP server. Merges provided updates into the existing config.
get_mcp_details
Get the full configuration for a specific MCP server by name.
list_all_mcps
List all configured MCP servers from ~/.claude.json with their configuration. By default, values inside each server's 'env' field are redacted to '***' so this tool can't be used to exfiltrate API keys stored in MCP env. Pass show_env_values=true to reveal them when you legitimately need them.
remove_mcpwrite action
Remove an MCP server from the user configuration (~/.claude/mcp.json).
restart_codex_mcp_process
Restart a Codex CLI MCP server process. Works reliably only for wrapped MCPs (via wrap_codex_mcp_stdio) by killing the wrapped child PID from its pidfile; otherwise you typically need to restart Codex CLI.
restart_mcp_process
Restart the underlying process for an MCP server by finding and killing its process. For wrapped stdio MCPs (via wrap_mcp_stdio), the wrapper will respawn automatically; otherwise you typically need to restart Claude CLI.
unwrap_mcp_stdio
Unwrap a previously wrapped stdio MCP server, restoring its original command. Requires restarting Claude Code to take effect.
wrap_codex_mcp_stdio
Wrap a Codex CLI stdio MCP server (from ~/.codex/config.toml) so it can be restarted reliably. Rewrites the MCP entry to launch mcpgo's Node wrapper that respawns the original command. Restart Codex CLI to take effect.
wrap_mcp_stdio
Wrap a stdio MCP server so it can be restarted reliably. Updates ~/.claude.json to launch a Node wrapper that spawns the original command and respawns it when killed. Requires restarting Claude CLI to take effect.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings

Code scan47 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 130 days ago8/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Mcpgo compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 82/100; higher than 63% of 48,255 servers
Tools: 11; the typical server has 7
Tools that change things: 18%; typical: 0%. Fewer write tools means less an agent can break
Downloads a week: 55; more than 46% of 12,191 servers with a package

What its tools let an agent do: 6 read · 1 create · 1 change · 1 delete · 2 run or deploy

Install Mcpgo in Claude Code, Cursor or VS Code

Runs npx -y @exfil/mcpgo on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcpgo -- npx -y @exfil/mcpgo

Add to Cursor

What the publisher says

From the Mcpgo repository's README, as published. We do not edit it. Read it on GitHub

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.

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:

wrapmcpstdio — wraps the target MCP in config
Restart Claude Code (or disconnect + reconnect via /mcp)
Done — use restartmcpprocess anytime

After setup:

"restart github"     → instant, wrapper auto-respawns the child, Claude Code stays connected
"restart postgres"        → same

If you ever want to undo wrapping, use unwrapmcpstdio to restore the original config.

Tools

Process management

wrapmcpstdio

Wrap a Claude Code stdio MCP for reliable restarts.

"wrap github"
"wrap postgres"

unwrapmcpstdio

Restore a wrapped MCP to its original config.

"unwrap github"
"unwrap postgres"

restartmcpprocess

Restart a wrapped MCP's child process — wrapper auto-respawns it, Claude Code stays connected.

"restart github"
"restart postgres"

checkmcphealth

Check if an MCP is configured, wrapped, and its process is running.

"check github health"
"is postgres running?"

Codex CLI support

wrapcodexmcp_stdio

Wrap a Codex CLI MCP from ~/.codex/config.toml.

"wrap my codex mcp called postgres"

restartcodexmcp_process

Restart a wrapped Codex CLI MCP.

"restart the codex postgres"

Config management

listallmcps

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

Remove an MCP server.

"remove the my-tool mcp"

configure_mcp

Update an existing MCP server's config fields.

"change github's command to python3"

getmcpdetails

Get full config details for a specific MCP.

"show me the github config"
"get details for postgres"

How wrapping works

When you call wrapmcpstdio "github", the config entry changes from:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Mcpgo: common questions

Is Mcpgo MCP server safe?: Mostly: it is graded B (82/100). Read the Mcpgo safety report
How do I install Mcpgo?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Mcpgo need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Mcpgo maintained?: The last commit was 168 days ago (2026-05-20). The latest release is v0.1.6.
How does Mcpgo compare with other MCP servers?: safety score 82/100 (higher than 63% of 48,255 servers); tools 11 (the typical server has 7); tools that change things 18% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.