Multi-MCP

io.github.religaPublished by GitHub account religav0.1.1Updated Oct 24, 2026

Multi-model AI orchestration MCP server with code review, compare, and debate tools.

VerifiedSTDIODesktop onlyDeveloper ToolsAI & ML

Overview

AI-generated overview

A local MCP server that orchestrates several AI models for code review, multi-model comparison, debate and chat inside Claude Code or OpenCode.

What you can do
Run a systematic code review with OWASP Top 10 security and performance checks, optionally naming the models to use. Ask several models the same question in parallel and compare their answers. Run a debate workflow where models answer independently and then critique each other. Chat with a model with repository context, keeping a thread across steps. List the available models and aliases.
When to use it
Useful when you want a second and third opinion on code quality, security or architecture decisions without switching between provider tools, and when you already work in Claude Code or OpenCode and want multi-model consensus on demand.
Requirements
Runs as a local Python process (Python 3.11+) installed from PyPI or source, configured in the MCP client. At least one provider API key is required: OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY or OPENROUTER_API_KEY, set in the environment or a .env file. Optional DEFAULT_MODEL and DEFAULT_MODEL_LIST settings. CLI-based models need their own CLI tools installed.
Before you install
Sends your code and prompts to the AI providers whose keys you configure, so review data leaves your machine. API usage is billed by those providers. CLI models can run with full tool access, including file operations and shell commands, so choose them deliberately. The bundled CLI is marked experimental.

Installation

In SourceWeft

  1. Open Multi-MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Multi-MCP: Multi-Model Code Review and Analysis MCP Server for Claude Code

[CI] [PyPI] [Downloads] [License: MIT] [Python 3.11+] [GitHub stars]

A multi-model AI orchestration MCP server for automated code review and LLM-powered analysis. Multi-MCP integrates with Claude Code CLI and OpenCode to orchestrate multiple AI models (OpenAI GPT, Anthropic Claude, Google Gemini) for code quality checks, security analysis (OWASP Top 10), and multi-agent consensus. Built on the Model Context Protocol (MCP), this tool enables Python developers and DevOps teams to automate code reviews with AI-powered insights directly in their development workflow.

[Demo Video]

Features

  • 🔍 Code Review - Systematic workflow with OWASP Top 10 security checks and performance analysis
  • 💬 Chat - Interactive development assistance with repository context awareness
  • 🔄 Compare - Parallel multi-model analysis for architectural decisions
  • 🎭 Debate - Multi-agent consensus workflow (independent answers + critique)
  • 🤖 Multi-Model Support - OpenAI GPT, Anthropic Claude, Google Gemini, and OpenRouter
  • 🖥️ CLI & API Models - Mix CLI-based (Gemini CLI, Codex CLI) and API models
  • 🏷️ Model Aliases - Use short names like mini, sonnet, gemini
  • 🧵 Threading - Maintain context across multi-step reviews

How It Works

Multi-MCP acts as an MCP server that Claude Code or OpenCode connects to, providing AI-powered code analysis tools:

  1. Install the MCP server and configure your AI model API keys
  2. Integrate with Claude Code or OpenCode automatically via make install
  3. Invoke tools using natural language (e.g., "multi codereview this file")
  4. Get Results from multiple AI models orchestrated in parallel

Performance

Fast Multi-Model Analysis:

  • ⚡ Parallel Execution - 3 models in ~10s (vs ~30s sequential)
  • 🔄 Async Architecture - Non-blocking Python asyncio
  • 💾 Conversation Threading - Maintains context across multi-step reviews
  • 📊 Low Latency - Response time = slowest model, not sum of all models

Quick Start

Prerequisites:

  • Python 3.11+
  • API key for at least one provider (OpenAI, Anthropic, Google, or OpenRouter)

Installation

Option 1: From Source
bash
# Clone and installgit clone https://github.com/religa/multi_mcp.gitcd multi_mcp# Execute ./scripts/install.shmake install
# The installer will:# 1. Install dependencies (uv sync)# 2. Generate your .env file# 3. Automatically add to Claude Code / OpenCode config (requires jq)# 4. Test the installation
Option 2: Manual Configuration

If you prefer not to run make install:

bash
# Install dependenciesuv sync
# Copy and configure .envcp .env.example .env# Edit .env with your API keys

Add to Claude Code (~/.claude.json) or OpenCode (~/.opencode/opencode.json), replacing /path/to/multi_mcp with your actual clone path:

Claude Code:

json
{  "mcpServers": {    "multi": {      "type": "stdio",      "command": "/path/to/multi_mcp/.venv/bin/python",      "args": ["-m", "multi_mcp.server"]    }  }}

OpenCode:

json
{  "mcp": {    "multi": {      "type": "local",      "command": ["/path/to/multi_mcp/.venv/bin/python", "-m", "multi_mcp.server"],      "enabled": true    }  }}

Configuration

Environment Configuration (API Keys & Settings)

Multi-MCP loads settings from .env files in this order (highest priority first):

  1. Environment variables (already set in shell)
  2. Project .env (current directory or project root)
  3. User .env (~/.multi_mcp/.env) - fallback for pip installs

Edit .env with your API keys:

bash
# API Keys (configure at least one)OPENAI_API_KEY=sk-...ANTHROPIC_API_KEY=sk-ant-...GEMINI_API_KEY=...OPENROUTER_API_KEY=sk-or-...
# Azure OpenAI (optional)AZURE_API_KEY=...AZURE_API_BASE=https://your-resource.openai.azure.com/
# AWS Bedrock (optional)AWS_ACCESS_KEY_ID=...AWS_SECRET_ACCESS_KEY=...AWS_REGION_NAME=us-east-1
# Model ConfigurationDEFAULT_MODEL=gpt-5-miniDEFAULT_MODEL_LIST=gpt-5-mini,gemini-3-flash

Model Configuration (Adding Custom Models)

Models are defined in YAML configuration files (user config wins):

  1. Package defaults: multi_mcp/config/config.yaml (bundled with package)
  2. User overrides: ~/.multi_mcp/config.yaml (optional, takes precedence)

To add your own models, create ~/.multi_mcp/config.yaml (see config.yaml and config.override.example.yaml for examples):

yaml
version: "1.0"
models:  # Add a new API model  my-custom-gpt:    litellm_model: openai/gpt-4o    aliases:      - custom    notes: "My custom GPT-4o configuration"
  # Add a custom CLI model  my-local-llm:    provider: cli    cli_command: ollama    cli_args:      - "run"      - "llama3.2"    cli_parser: text    aliases:      - local    notes: "Local LLaMA via Ollama"
  # Override an existing model's settings  gpt-5-mini:    constraints:      temperature: 0.5  # Override default temperature

Merge behavior:

  • New models are added alongside package defaults
  • Existing models are merged (your settings override package defaults)
  • Aliases can be "stolen" from package models to your custom models

Usage Examples

Once installed in your MCP client (Claude Code or OpenCode), you can use these commands:

💬 Chat - Interactive development assistance:

Can you ask Multi chat what's the answer to life, universe and everything?

🔍 Code Review - Analyze code with specific models:

Can you multi codereview this module for code quality and maintainability using gemini-3 and codex?

🔄 Compare - Get multiple perspectives (uses default models):

Can you multi compare the best state management approach for this React app?

🎭 Debate - Deep analysis with critique:

Can you multi debate the best project code name for this project?

Enabling Allowlist

Edit ~/.claude/settings.json and add the following lines to permissions.allow to enable Claude Code to use Multi MCP without blocking for user permission:

json
{  "permissions": {    "allow": [      ...      "mcp__multi__chat",      "mcp__multi__codereview",      "mcp__multi__compare",      "mcp__multi__debate",      "mcp__multi__models"    ],  },  "env": {    "MCP_TIMEOUT": "300000",    "MCP_TOOL_TIMEOUT": "300000"  },}

Model Aliases

Use short aliases instead of full model names:

AliasModelProvider
minigpt-5.6-lunaOpenAI
nanogpt-5.6-lunaOpenAI
gptgpt-6-astraOpenAI
astragpt-6-astraOpenAI
solgpt-5.6-solOpenAI
terragpt-5.6-terraOpenAI
lunagpt-5.6-lunaOpenAI
codexgpt-5.3-codexOpenAI
fableclaude-fable-5-1Anthropic
opusclaude-opus-5Anthropic
sonnetclaude-sonnet-5Anthropic
haikuclaude-haiku-4.5Anthropic
geminigemini-3.1-pro-previewGoogle
gemini-3gemini-3.1-pro-previewGoogle
flashgemini-3.8-flashGoogle
flash-litegemini-3.5-flash-liteGoogle
azure-miniazure-gpt-5-miniAzure
bedrock-sonnetbedrock-claude-4-5-sonnetAWS

Run multi:models to see all available models and aliases.

CLI Models

Multi-MCP can execute CLI-based AI models (like Gemini CLI, Codex CLI, or Claude CLI) alongside API models. CLI models run as subprocesses and work seamlessly with all existing tools.

Benefits:

  • Use models with full tool access (file operations, shell commands)
  • Mix API and CLI models in compare and debate workflows
  • Leverage local CLIs without API overhead

Built-in CLI Models:

  • gemini-cli (alias: gem-cli) - Gemini CLI with auto-edit mode
  • codex-cli (alias: cx-cli) - Codex CLI with full-auto mode
  • claude-cli (alias: cl-cli) - Claude CLI with acceptEdits mode

Adding Custom CLI Models:

Add to ~/.multi_mcp/config.yaml (see Model Configuration):

yaml
version: "1.0"
models:  my-ollama:    provider: cli    cli_command: ollama    cli_args:      - "run"      - "codellama"    cli_parser: text  # "json", "jsonl", or "text"    aliases:      - ollama    notes: "Local CodeLlama via Ollama"

Prerequisites:

CLI models require the respective CLI tools to be installed:

bash
# Gemini CLInpm install -g @anthropic-ai/gemini-cli
# Codex CLInpm install -g @openai/codex
# Claude CLInpm install -g @anthropic-ai/claude-code

CLI Usage (Experimental)

Multi-MCP includes a standalone CLI for code review without needing an MCP client.

⚠️ Note: The CLI is experimental and under active development.

bash
# Review a directorymulti src/
# Review specific filesmulti src/server.py src/config.py
# Use a different modelmulti --model mini src/
# JSON output for CI/pipelinesmulti --json src/ > results.json
# Verbose loggingmulti -v src/
# Specify project root (for CLAUDE.md loading)multi --base-path /path/to/project src/

Why Multi-MCP?

FeatureMulti-MCPSingle-Model Tools
Parallel model execution✅❌
Multi-model consensus✅Varies
Model debates✅❌
CLI + API model support✅❌
OWASP security analysis✅Varies

Troubleshooting

"No API key found"

  • Add at least one API key to your .env file
  • Verify it's loaded: uv run python -c "from multi_mcp.settings import settings; print(settings.openai_api_key)"

Integration tests fail

  • Set RUN_E2E=1 environment variable
  • Verify API keys are valid and have sufficient credits

Debug mode:

bash
export LOG_LEVEL=DEBUG # INFO is defaultuv run python -m multi_mcp.server

Check logs in logs/server.log for detailed information.

FAQ

Q: Do I need all three AI providers? A: No, just one API key (OpenAI, Anthropic, or Google) is enough to get started.

Q: Does it truly run in parallel? A: Yes! When you use codereview, compare or debate tools, all models are executed concurrently using Python's asyncio.gather(). This means you get responses from multiple models in the time it takes for the slowest model to respond, not the sum of all response times.

Q: How many models can I run at the same time? A: There's no hard limit! You can run as many models as you want in parallel. In practice, 2-5 models work well for most use cases. All tools use your configured default models (typically 2-3), but you can specify any number of models you want.

Contributing

We welcome contributions! See CONTRIBUTING.md for:

  • Development setup
  • Code standards
  • Testing guidelines
  • Pull request process

Quick start:

bash
git clone https://github.com/YOUR_USERNAME/multi_mcp.gitcd multi_mcpuv sync --extra devmake check && make test

License

MIT License - see LICENSE file for details

Links

Source: README.md at commit 12dfd1d

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts