LiteLLM Proxy documentation describes an MCP Gateway that exposes list-tools, call-tools, prompts, and resources operations through a fixed endpoint while enforcing access by API key, team, or organization. Supported transports listed on docs.litellm.ai include Streamable HTTP, SSE, and stdio; operators can register HTTP, SSE, or stdio MCP servers through the LiteLLM UI or config.yaml after enabling database storage (`store_model_in_db` / `STORE_MODEL_IN_DB`). Release notes cited in the docs state LiteLLM v1.80.18 aligns with MCP protocol version 2025-11-25 and namespaces tools by MCP server name per SEP-986 naming rules for newly added servers. The gateway is positioned as a way to use MCP tools alongside all LiteLLM-supported chat models from Cursor or other OpenAI-compatible clients pointed at the proxy.
Use cases
- Centralize dozens of MCP servers behind one LiteLLM virtual key for a platform team
- Apply team-level budgets and guardrails before agents invoke third-party MCP tools
- Register Streamable HTTP or SSE MCP endpoints through the admin UI instead of per-developer JSON files
- Namespace tools per MCP server to avoid collisions when multiple catalogs are enabled
- Troubleshoot connectivity using the documented MCP troubleshooting guide after enabling DB storage
Key features
- Cursor
- VS Code
- Claude Desktop
- Codex
Frequently Asked Questions
- Do MCP servers persist without database storage?
- Docs require `store_model_in_db` / `STORE_MODEL_IN_DB=True` (or equivalent config.yaml) to store MCP definitions in the proxy database.
- Which MCP protocol version does LiteLLM cite?
- Documentation references MCP protocol version 2025-11-25 starting in LiteLLM v1.80.18, with SEP-986-compliant server names for new registrations.
- Can I mix stdio and remote HTTP MCPs?
- Yes—the overview lists Streamable HTTP, SSE, and stdio transports with separate UI walkthroughs for each pattern.
Related
Related
3 Indexed items
Apify MCP Server
Apify documents an official Model Context Protocol server hosted at https://mcp.apify.com that speaks Streamable HTTP in line with the current MCP specification; Apify warns that SSE transport was deprecated for removal April 1, 2026. Hosted clients authenticate through browser OAuth or by supplying Bearer tokens sourced from Console → Settings → Integrations (`APIFY_TOKEN`), can pin tool bundles via URL query (`?tools=actors,docs,apify/rag-web-browser` style examples reproduce Apify wording), optionally append `telemetry-enabled=false`, and benefit from inferred structured-output schemas surfaced for Actor tooling on hosted endpoints unlike the default stdio server. When MCP clients refuse remote transports, docs recommend `npx -y @apify/actors-mcp-server` with `APIFY_TOKEN` for stdio, Node.js ≥18, and adherence to documented per-user throughput (Apify cites up to thirty requests per second across Actor runs plus storage/documentation calls). Specialized payment modes (open x402 on Base plus Skyfire) appear as optional adjunct pages inside the broader integration handbook.
n8n MCP Server Trigger
The MCP Server Trigger is a first-party n8n core node that turns an n8n workflow into a Model Context Protocol server endpoint. Instead of chaining conventional trigger nodes, it connects only to tool nodes so remote MCP clients can list tools and invoke them over long-lived Server-Sent Events or streamable HTTP transports (stdio is explicitly unsupported). Each node exposes separate test and production MCP URLs, optional bearer or header authentication, and documentation explains how to proxy Claude Desktop through `npx mcp-remote` plus queue-mode caveats for multi-replica webhook deployments.
DuckDB MCP community extension (`duckdb_mcp`)
The DuckDB-distributed community extension `duckdb_mcp` embeds MCP client and server capabilities directly inside DuckDB. Installers load it via `INSTALL duckdb_mcp FROM community` followed by `LOAD duckdb_mcp`, after which SQL can attach remote MCP servers (stdio/TCP/WebSocket transports), enumerate resources (`mcp_list_resources`), invoke remote tools (`mcp_call_tool`), and wrap responses with `read_csv`/`read_json`/`read_parquet` URIs routed through `mcp://`. In reverse direction, DuckDB can publish tables, queries, and execution-bound tools (`mcp_publish_table`, `mcp_publish_query`, `mcp_publish_execution_tool`) while `mcp_server_start` exposes them to external MCP-compatible clients.