Other MCP agents

Cursor, Windsurf, Cline, Continue, Zed, and other MCP-compatible tools connect to devcoach with a standard MCP server entry. Add this to your agent's MCP config file:

{
  "mcpServers": {
    "devcoach": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "devcoach", "mcp"]
    }
  }
}

Agent	Config file
Cursor	`~/.cursor/mcp.json`
Windsurf	`~/.codeium/windsurf/mcp_config.json`
Cline (VS Code)	VS Code Settings → `cline.mcpServers`
Continue.dev	`~/.continue/config.json` → `mcpServers`
Zed	`.zed/settings.json` → `context_servers`

MCP Registry

devcoach is listed in the official MCP Registry as io.github.UltimaPhoenix/devcoach. If your client can browse or install servers from the registry, search for that name (or devcoach) and install it from there — the entry points at the npm package devcoach over stdio, so it runs exactly the same local server as the config above.

Gemini CLI and Codex CLI have first-class support

Gemini CLI (beta) and Codex CLI (beta) get the full coaching loop — automatic lesson hooks and the devcoach skill — via devcoach install --gemini / --codex. Use those pages instead of the generic config above.

note

The automatic stop hooks (a lesson after each task) exist only for Claude Code, Gemini CLI, and Codex CLI. The agents on this page still have full access to all MCP tools and resources — coaching can be triggered manually or by prompting your agent.

→ Next: Coaching in your agent.

MCP Registry​

MCP Registry