mcpgo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_all_mcpsA | 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. |
| get_mcp_detailsB | Get the full configuration for a specific MCP server by name. |
| check_mcp_healthA | Check the health of an MCP server — whether it is configured, wrapped, and its process is running. |
| restart_mcp_processA | 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. |
| restart_codex_mcp_processA | 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. |
| wrap_mcp_stdioA | 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. |
| unwrap_mcp_stdioA | Unwrap a previously wrapped stdio MCP server, restoring its original command. Requires restarting Claude Code to take effect. |
| wrap_codex_mcp_stdioA | 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. |
| configure_mcpC | Update the configuration of an existing MCP server. Merges provided updates into the existing config. |
| remove_mcpA | Remove an MCP server from the user configuration (~/.claude/mcp.json). |
| add_mcpB | Add a new MCP server to the user configuration (~/.claude.json). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool has a distinct purpose: listing, retrieving, health-checking, restarting, wrapping/unwrapping, configuring, adding, and removing MCP servers. The two restart tools and the two wrap tools are clearly differentiated by target client (Claude vs Codex), so there's no ambiguity.
All tools follow a consistent verb_noun pattern (list_all, get, check, restart, wrap, unwrap, configure, remove, add). The inclusion of client-specific modifiers (codex, stdio) is consistent and descriptive, and there are no mixed conventions or vague verbs.
With 11 tools, the server is well-scoped for managing MCP server configurations. Each tool covers a distinct operation needed for lifecycle management, and the count is right in the sweet spot for a focused administrative utility.
The surface covers core CRUD operations (add, get, list, remove, configure) plus health and restart. However, there is no unwrap_codex_mcp_stdio tool to complement wrap_codex_mcp_stdio, leaving a minor asymmetric gap that agents would need to work around.