claude-delegator

Claude Delegator exposes a managed MCP server within Claude Code that routes complex Claude Code tasks to a team of expert GPT and/or Gemini subagents. The plugin provides five specialist roles—Architect, Plan Reviewer, Scope Analyst, Code Reviewer, and Security Analyst—that can either analyze a request or implement changes directly. You can choose to leverage GPT (Codex) or Gemini, or both, and Claude will auto-route tasks to the appropriate expert based on the prompt and your configuration. Use multi-turn conversations to chain implementation steps, where the expert passes a threadId back to continue context across turns. This MCP server is designed to help with architecture decisions, security reviews, code quality improvements, and thorough reviews before implementing changes. To enable it, install the plugin in Claude Code, then configure MCP if needed and run the setup command to start delegating complex tasks to the experts.

Prerequisites:

• Access to Claude Code with marketplace plugin installation capabilities
• Either Codex CLI (for GPT) or Gemini CLI (for Gemini) installed globally on your system
• Node.js and npm (if using the Node-based MCP server endpoint)

Install steps:

1. Add the Claude Delegator marketplace plugin inside Claude Code:

   • Run: /plugin marketplace add jarrodwatts/claude-delegator

2. Install the plugin:

   • Run: /plugin install claude-delegator

3. Run the MCP setup for the server:

   • Run: /claude-delegator:setup

4. If you need manual MCP setup (alternative):

   • For Codex (GPT): claude mcp add --transport stdio --scope user codex -- codex -m gpt-5.3-codex mcp-server
   • For Gemini: claude mcp add --transport stdio --scope user gemini -- node /path/to/claude-delegator/server/gemini/index.js

5. Verify registration:

   • Run: claude mcp list
   • You can also send a health payload to the Gemini endpoint as shown in the README example.

Notes:

• Ensure your Gemini API key is available (GOOGLE_API_KEY) if using Gemini.
• If you run into authentication or server-not-found issues, restart Claude Code after setup and verify MCP registration with claude mcp list.

Tips and common issues:\n- Environment variables: set CLAUDE_PLUGIN_ROOT to the plugin directory; set GOOGLE_API_KEY if using Gemini.\n- If you switch providers (GPT or Gemini), Claude will auto-detect the configured provider and route tasks accordingly.\n- For multi-turn implementation flows, use the threadId mechanism described in the docs to preserve context across turns.\n- If the expert is not triggered, try explicit prompts such as 'Ask GPT to review...' or 'Ask Gemini to review...'.\n- Ensure the MCP server is registered under the correct transport (stdio) and scope (user or org) as per your workflow.\n- The Prompts for each expert live under prompts/ and can be customized if you fork the repo.