gum runs as an MCP stdio server. It does not open an HTTP listener.
gum setup --dry-run
gum mcp --stdio --help
gum doctor --format=jsonUse an absolute path if another program named gum is installed.
command -v gum
gum --versionFor common coding agents, let gum write the skill files and MCP config:
gum setup --target all --features skills,mcp --dry-run
gum setup --target all --features skills,mcp --yesUse one target when you only want one client:
gum setup --target codex --scope user --yes
gum setup --target claude --scope project --yes
gum setup --target cursor --scope project --yes
gum setup --target gemini --scope user --yesgum setup prints the files it writes and the next auth checks. Existing MCP
config is merged. Existing skill files are skipped unless you pass --force.
Edit claude_desktop_config.json.
macOS path:
~/Library/Application Support/Claude/claude_desktop_config.json
Config:
{
"mcpServers": {
"gum": {
"command": "/absolute/path/to/gum",
"args": ["mcp", "--stdio"]
}
}
}Restart Claude Desktop after editing the file.
Use a project .mcp.json or the user-level Claude Code MCP config.
{
"mcpServers": {
"gum": {
"command": "/absolute/path/to/gum",
"args": ["mcp", "--stdio"]
}
}
}Edit ~/.cursor/mcp.json.
{
"mcpServers": {
"gum": {
"command": "/absolute/path/to/gum",
"args": ["mcp", "--stdio"]
}
}
}At startup gum exposes a compact meta-tool surface plus selected convenience
tools. The meta-tools cover search, describe, read, write, destructive
confirmation, sandboxed code, gain/cache inspection, and polling. Use
gum mcp --stdio --help or gum describe <op_id> for the exact surface in the
binary you installed.
The server also exposes skills_list and skills_get. Agents can use those
tools to load the same guidance shipped by gum skills list and
gum skills show mcp.
The server also supports MCP resources, prompts, completions, roots-aware project lookup, cancellation, progress, and structured errors where the pinned MCP SDK supports them. It does not advertise unimplemented server capabilities.
If the client does not show gum tools:
- Run
gum mcp --stdio --help. - Run
gum doctor --format=json. - Replace
command: "gum"with an absolute path. - Restart the client.
- Read the client's stderr log. gum must not print normal logs to stdout in MCP mode before the JSON-RPC handshake.
If auth fails inside the MCP client, fix it in the terminal first:
gum auth status
gum login --service gmail,calendar
gum doctor