LLM Router MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@LLM Router MCP plan a microservice architecture"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
LLM Router MCP
Route prompts intelligently across Claude, Gemini, and GPT-4o — automatically picking the best model for every task while minimising token cost.
✨ What is this?
llm-router-mcp is a Model Context Protocol (MCP) server that acts as an intelligent dispatcher for your AI workloads. Instead of hardcoding a single LLM into your workflow, the router analyses the intent of each prompt and automatically selects the most cost-effective and capable model for that specific task type.
Your prompt ──► LLM Router ──► PLANNING → Gemini
├── SCAFFOLDING → Gemini
├── CODEGEN → Claude
├── REFACTOR → Claude
├── REVIEW → Claude
├── TESTING → GPT-4o
└── IMPLEMENT → GPT-4oRelated MCP server: ypollak2/llm-router
🚀 Features
Smart intent-based routing — classifies prompts into 8 task categories and dispatches to the optimal model
Three frontier models — integrates Claude (Anthropic), Gemini (Google), and GPT-4o (OpenAI) out of the box
Zero-config mock mode — works out of the box with no API keys; auto-enables mock mode when keys are absent
Session-aware context caching — maintains conversation context across turns within the same session
Explicit tool shortcuts — bypass auto-routing with dedicated
plan_workflow,generate_code, andimplement_featuretoolsMCP-native — drop it into any MCP-compatible host (Claude Desktop, Cursor, VS Code Continue, etc.)
📦 Quick Start
Option A — npx (no install needed)
npx llm-router-mcpOption B — Global install
npm install -g llm-router-mcp
llm-router-mcpOption C — From source
git clone https://github.com/Devatva24/LLM-Router-MCP.git
cd LLM-Router-MCP
npm install
npm run build
node dist/index.jsNo API keys? No problem. The server automatically falls back to mock mode and logs a helpful message. You only need keys when you want real model responses.
🗺️ Routing Logic
Task Category | Trigger Keywords | Routed To |
Planning | architecture, design, system design, strategy, workflow | ✦ Gemini |
Scaffolding | scaffold, boilerplate, setup, folder structure | ✦ Gemini |
Code Generation | write a function, implement, create a class, algorithm | ✦ Claude |
Refactor | refactor, clean up, improve, rewrite, restructure | ✦ Claude |
Code Review | review, debug, explain, what's wrong, critique | ✦ Claude |
Testing | unit tests, Jest, Vitest, test suite, test cases | ✦ GPT-4o |
Implementation | implement, add endpoint, build the, create the API | ✦ GPT-4o |
General | anything else | ✦ Claude (fallback) |
⚙️ Configuration
Set your API keys as environment variables to use real models:
# Mac / Linux
export ANTHROPIC_API_KEY=sk-ant-...
export GOOGLE_API_KEY=AIza...
export OPENAI_API_KEY=sk-...
# Windows (PowerShell)
$env:ANTHROPIC_API_KEY="sk-ant-..."
$env:GOOGLE_API_KEY="AIza..."
$env:OPENAI_API_KEY="sk-..."If any keys are missing the server auto-enables mock mode — no crash, no config needed.
🖥️ Editor Integration
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"llm-router": {
"command": "npx",
"args": ["llm-router-mcp"]
}
}
}Cursor
Add to your Cursor MCP settings:
{
"mcpServers": {
"llm-router": {
"command": "npx",
"args": ["llm-router-mcp"]
}
}
}VS Code (Continue extension)
Add to ~/.continue/config.json:
{
"mcpServers": {
"llm-router": {
"command": "npx",
"args": ["llm-router-mcp"]
}
}
}Ready-made config files for Cursor and Continue are included in the
cursor-config/and%USERPROFILE%/.continue/directories of this repo.
🧰 Available MCP Tools
route_prompt
Automatically classifies and routes a prompt to the best model.
{
"prompt": "Write a recursive function to flatten deeply nested objects",
"session_id": "my-session"
}plan_workflow
Explicitly routes to Gemini for high-level planning and architecture tasks.
{
"prompt": "Design a checkout flow for an e-commerce app",
"session_id": "my-session"
}generate_code
Explicitly routes to Claude for complex logic, algorithms, and refactoring.
{
"prompt": "Write a binary search tree with insert and delete",
"session_id": "my-session"
}implement_feature
Explicitly routes to GPT-4o for feature implementation and test generation.
{
"prompt": "Implement the /api/products CRUD endpoints",
"session_id": "my-session"
}clear_context
Clears the cached conversation context for a given session.
{
"session_id": "my-session"
}🧪 Running Tests
The test suite validates all routing decisions in mock mode — no API keys needed:
npm testExpected output:
🧪 LLM Router — mock test suite
✅ planning → Gemini
✅ codegen → Claude
✅ testing → GPT-4o
✅ review → Claude
✅ explicit plan_workflow
✅ explicit implement_feature
✅ context cache — 2nd turn
✅ clear_context
──────────────────────────────────────────
8 passed 0 failed (8 total)📁 Project Structure
LLM-Router-MCP/
├── src/
│ ├── index.ts # MCP server entrypoint & routing logic
│ ├── classifier.ts # Prompt intent classifier
│ ├── context-cache.ts # Session-aware context management
│ ├── mock.ts # Mock responses for zero-cost testing
│ └── logger.ts # Lightweight logger
├── dist/ # Compiled JavaScript (after npm run build)
├── cursor-config/ # Ready-made Cursor MCP config
├── test-router.cjs # End-to-end test suite (mock mode)
├── tsconfig.json
└── package.json🤝 Contributing
Contributions are welcome! Feel free to open an issue or submit a pull request for:
Adding support for additional LLM providers
Improving routing classification accuracy
Adding streaming response support
Writing more test coverage
📄 License
MIT — see LICENSE for details.
Available Tools
5 toolsclear_contextB
Clears the context cache for a session, starting fresh.
Inputs: session_id.
generate_codeB
Always uses Claude for complex code generation, logic-heavy tasks, or refactoring.
Inputs: prompt (required), session_id.
implement_featureC
Always uses GPT-4o for feature implementation, test generation, or repetitive coding tasks.
Inputs: prompt (required), session_id.
plan_workflowC
Always uses Gemini to plan a high-level workflow or architecture for a feature.
Inputs: prompt (required), session_id.
route_promptA
Routes a coding prompt to the best LLM (Claude, Gemini, GPT-4o) based on task type. Automatically classifies the task and selects the cheapest/most capable model.
Inputs: prompt (required), session_id.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
route_prompt overlaps heavily with plan_workflow, generate_code, and implement_feature, as those three are just specialized routing tools with predetermined models. Additionally, generate_code and implement_feature are similar enough (complex vs repetitive coding) that an agent may struggle to choose between them.
All tool names follow a consistent verb_noun pattern (route_prompt, plan_workflow, clear_context, generate_code, implement_feature). The naming is predictable and clearly indicates the action and target.
With 5 tools, the server is well-scoped for a specialized LLM routing purpose. Each tool has a distinct name and fits within the expected 3-15 range, making the tool surface easy to grasp.
The core workflow of routing, planning, generating, and implementing is covered, along with a context reset. Minor gaps exist, such as no tool to list available models or customize routing rules, but agents can work around these by using route_prompt for general tasks.
Maintenance
Related MCP Connectors
AI model routing on your own vendor keys: pick the best model per prompt, or route and run it.
Real-time, drift-verified LLM pricing across 31 providers with cost+quality model routing.
AI routing, memory, guardrails, and governance. Routes across Claude, GPT, Gemini.
Sourced AI-model pricing and capability data — compare and route to the cheapest capable model.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceCompare AI inference pricing across 9 providers in real time. Routing recommendations, spend tracking, and budget alerts for AI agents.95 npmMIT
- AlicenseAqualityAmaintenanceRoutes your AI tasks to the best available model across 20+ providers — automatically selecting based on task type, budget, and subscription pressure. Supports text, image, video, and audio with built-in cost optimization and fallback chains.60187 PyPI127MIT

DeepMyst MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceEnables intelligent LLM optimization and routing for Claude Desktop and HTTP clients, reducing token usage and automatically selecting the best model for each query.4MIT- FlicenseNot gradedqualityDmaintenanceAutomatically routes queries to the most suitable AI model based on task type, cost constraints, and performance needs, supporting multiple providers and customizable priorities.-