ConsultingAgents MCP Server

An MCP server that interfaces with OpenAI, Google, and Anthropic's APIs to give Claude Code "coworkers" to help it on difficult problems. The consultingagents mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 4 defined tools rather than through you.

What it actually does

A Model Context Protocol (MCP) server that allows Claude Code to consult with additional AI agents for code and problem analysis. This server provides access to Darren (OpenAI), Sonny (Anthropic), Sergey (OpenAI with web search), and Gemma (Google Gemini with repository analysis) as expert consultants, enabling multi-model perspective on coding problems.

• Darren — OpenAI expert coding consultant powered by o3-mini model with high reasoning capabilities
• Sonny — Anthropic expert coding consultant powered by Claude 3.7 Sonnet with enhanced thinking (Note: somewhat redundant now that Claude Code has native Extended Thinking mode)
• Sergey — OpenAI web search specialist powered by GPT-4o for finding relevant documentation and examples (Note: somewhat redundant now that Claude Code has native web search capabilities)
• Gemma — Google Gemini specialist powered by gemini-2.5-pro-exp-03-25 with 1M token context for comprehensive repository analysis
• MCP Integration — Seamless integration with Claude Code via MCP protocol
• Multiple Transport Options — Supports stdio (for direct Claude Code integration) and HTTP/SSE transport

Its toolset

Everything the assistant can do here goes through one of these:

• consult_with_darren — Uses OpenAI's o3-mini model with high reasoning to analyze code and provide recommendations
• consult_with_sonny — Uses Claude 3.7 Sonnet with enhanced thinking to provide in-depth code analysis
• consult_with_sergey — Uses GPT-4o with web search capabilities to find relevant documentation and examples
• consult_with_gemma — Uses Google's Gemini 2.5 Pro model with 1M token context window to analyze entire repositories and provide comprehensive development plans

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

You will need 3 environment variables: OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Python 3.8+ - OpenAI API key - Anthropic API key - Google API key - Claude Code CLI (for integration)

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. ConsultingAgents's toolset — consult_with_darren, consult_with_sonny, consult_with_sergey and 1 more — is a fair guide to whether it matches your workflow. It is maintained by MatthewPDingle; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the consultingagents mcp server does with a few real requests.