litellm-mcp
Allows interaction with local Ollama models through the LiteLLM gateway for single-turn and multi-turn queries.
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., "@litellm-mcpexplain the concept of recursion"
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.
litellm-mcp
MCP server that lets Claude Code dispatch tasks to the LiteLLM gateway
(192.168.10.175:4000) as worker agents. Unlike ollama-mcp (which reaches only the
local Ollama models directly), this shim reaches the full gateway model set — the
local Ollama models and the Anthropic-via-gateway models
(claude-sonnet-4-6, claude-haiku-4-5).
Tools
list_models()— model ids registered on the gateway.ask_model(prompt, model=None, system=None)— single-turn worker call. Defaults toqwen2.5:7b-instruct(a reliable non-reasoning local model — a safer headless default than the reasoning modelqwen3.5:4b).chat(messages, model=None)— multi-turn.
Related MCP server: mcp-local-llm
Credentials — per-request header (not at rest on Proteus)
This shim brokers spend on Anthropic, so the gateway master key is sensitive. It is not
stored in /etc/mcp/litellm-mcp.env on the shared Proteus host. Instead the key travels as a
per-request header from the client's ~/.claude.json:
"litellm": {
"type": "sse",
"url": "http://192.168.10.190:8107/sse",
"headers": { "x-litellm-key": "<LITELLM_MASTER_KEY from Infisical>" }
}The server reads x-litellm-key (or Authorization: Bearer ...) from each tool call. For
local/stdio use, LITELLM_API_KEY env is accepted as a fallback.
Config (non-sensitive, env file on Proteus)
Var | Default |
|
|
|
|
|
|
Tests
pip install -e ".[test]"
pytest -q # unit (respx-mocked)
LITELLM_API_KEY=... pytest -q # also runs live integration against the gatewayIntegration tests skip automatically when the gateway is unreachable or LITELLM_API_KEY
is unset (e.g. in CI on the GitLab runner). Deploy is via GitLab CI → Proteus
(/opt/mcp/litellm-mcp/, systemd litellm-mcp.service, port 8107).
This server cannot be deployed
Maintenance
Related MCP Connectors
Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
MCP server for AI dialogue using various LLM models via AceDataCloud
Synap (pool.linkrra.com/v1), Linkrra's OpenAI-compatible LLM API, as an MCP server.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceA simple MCP server that enables Claude to communicate with locally running LLM models via LM Studio.9MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that lets Claude Code delegate mechanical tasks to a local LLM for summarization, classification, extraction, and drafting.7 npm11MIT
- AlicenseAqualityDmaintenanceMCP server for Claude Code to interact with OpenClaw AI agents (Daemon, Soren, Ash, etc.) via the gateway API, providing tools to ask agents, list them, and check their status.3171 npmMIT
- AlicenseAqualityBmaintenanceAn MCP server that lets Claude Code delegate coding tasks such as code generation, review, refactoring, and test writing to a local Ollama instance running a Qwen3 model.9MIT