<picture> <source media="(prefers-color-scheme: dark)" srcset="assets/readme/hero-dark.svg"> <source media="(prefers-color-scheme: light)"
. The llm router mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 1 defined tool rather than through you.
Everything the assistant can do here goes through one of these:
Category — ToolsBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 8 environment variables: OPENAI_API_KEY, GEMINI_API_KEY, OLLAMA_BASE_URL, OPENROUTER_API_KEY, LLM_ROUTER_POLICY, LLM_ROUTER_ENFORCE, LLM_ROUTER_PROFILE, LLM_ROUTER_BANDIT. 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.
Plenty of AI and media services 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. Llm Router's toolset — Category — is a fair guide to whether it matches your workflow. It is maintained by ypollak2; 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.
| Tool | What it does |
|---|---|
| Category | Tools |
{
"mcpServers": {
"llm-router": {
"command": "uvx",
"args": ["llm-routing"],
"env": {
"OPENAI_API_KEY": "your-value",
"GEMINI_API_KEY": "your-value",
"OLLAMA_BASE_URL": "your-value",
"OPENROUTER_API_KEY": "your-value",
"LLM_ROUTER_POLICY": "your-value",
"LLM_ROUTER_ENFORCE": "your-value",
"LLM_ROUTER_PROFILE": "your-value",
"LLM_ROUTER_BANDIT": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| GEMINI_API_KEY | Credential the server authenticates with. | Yes |
| OLLAMA_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| OPENROUTER_API_KEY | Credential the server authenticates with. | Yes |
| LLM_ROUTER_POLICY | Configuration value read at startup. | Optional |
| LLM_ROUTER_ENFORCE | Configuration value read at startup. | Optional |
| LLM_ROUTER_PROFILE | Configuration value read at startup. | Optional |
| LLM_ROUTER_BANDIT | Configuration value read at startup. | Optional |
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Give your assistant a voice — text-to-speech, voice cloning and audio tools from the ElevenLabs API.
Give your assistant a real code sandbox — isolated cloud VMs for actually running the code it writes.
The ML hub in your context window — search models, datasets, papers and run Spaces from the official server.