
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.
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.
Installation
In SourceWeft
- Open Multi-MCP in the dashboard and add it to a workspace.
- 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.
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:
- Install the MCP server and configure your AI model API keys
- Integrate with Claude Code or OpenCode automatically via
make install - Invoke tools using natural language (e.g., "multi codereview this file")
- 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
Option 2: Manual Configuration
If you prefer not to run make install:
Add to Claude Code (~/.claude.json) or OpenCode (~/.opencode/opencode.json), replacing /path/to/multi_mcp with your actual clone path:
Claude Code:
OpenCode:
Configuration
Environment Configuration (API Keys & Settings)
Multi-MCP loads settings from .env files in this order (highest priority first):
- Environment variables (already set in shell)
- Project
.env(current directory or project root) - User
.env(~/.multi_mcp/.env) - fallback for pip installs
Edit .env with your API keys:
Model Configuration (Adding Custom Models)
Models are defined in YAML configuration files (user config wins):
- Package defaults:
multi_mcp/config/config.yaml(bundled with package) - 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):
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:
🔍 Code Review - Analyze code with specific models:
🔄 Compare - Get multiple perspectives (uses default models):
🎭 Debate - Deep analysis with critique:
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:
Model Aliases
Use short aliases instead of full model names:
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
compareanddebateworkflows - Leverage local CLIs without API overhead
Built-in CLI Models:
gemini-cli(alias:gem-cli) - Gemini CLI with auto-edit modecodex-cli(alias:cx-cli) - Codex CLI with full-auto modeclaude-cli(alias:cl-cli) - Claude CLI with acceptEdits mode
Adding Custom CLI Models:
Add to ~/.multi_mcp/config.yaml (see Model Configuration):
Prerequisites:
CLI models require the respective CLI tools to be installed:
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.
Why Multi-MCP?
Troubleshooting
"No API key found"
- Add at least one API key to your
.envfile - 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=1environment variable - Verify API keys are valid and have sufficient credits
Debug mode:
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:
License
MIT License - see LICENSE file for details
Links
Source: README.md at commit 12dfd1d
Tools
0Version history
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