LiteLLM MCP server: MCP Gateway, plus admin tools
Gateway routing and gateway administration are separate MCP integrations.
Checked 3 October 2026 · from LiteLLM's LiteAdmin MCP setup page, its 23 September 2026 launch post, the liteadmin-mcp repository and the MCP Gateway docs
One of 91 guides to monitoring and developer tools. Each covers what an AI coding agent can get out of the tool through MCP, the protocol that lets the agent query the tool directly.
Summary
LiteAdmin MCP manages a running LiteLLM gateway through its management API. It is distinct from routing other servers through MCP Gateway.
The management connector requires a personal proxy_admin key, including for reads. Team-admin and proxy_admin_viewer credentials are not interchangeable with that role.
LiteLLM launched LiteAdmin MCP on 23 September 2026. It includes 65 reviewed admin operations and exposes the ones your gateway supports.
How LiteLLM works with MCP
LiteLLM can route model requests and external MCP tools. LiteAdmin adds an MCP surface for administration of the gateway itself.
The administration server calls your gateway’s management API. Your MCP client still runs its own agent/model; adding this connector does not change the client’s model-provider configuration.
Choose the route for your task
| Route | Data or action | Credential boundary |
|---|---|---|
| LiteAdmin MCP | Keys, model deployments, teams, budgets, spending and request logs | Personal proxy_admin identity |
| MCP Gateway | Tools from registered upstream MCP servers | Gateway policy plus each upstream server’s authentication |
Every vendor here gets the same four checks: official, maintained, distributed and usable. LiteLLM passes 3 of them.
| Check | Result | Evidence |
|---|---|---|
| Official | Pass | LiteLLM documents LiteAdmin MCP as its administration connector. |
| Maintained | Pass | BerriAI/liteadmin-mcp was last pushed on 1 October 2026, eight days after the 23 September launch. |
| Distributed | Pass | The vendor publishes a standalone connector with stdio and Streamable HTTP setup. |
| Usable | Unknown | Requires a running LiteLLM gateway and a personal virtual key whose user holds the proxy_admin role. |
| Part of the work | What LiteLLM has here | Can an agent reach it |
|---|---|---|
| AI cost management | Gateway budgets and spending | Administration tools, subject to gateway permissions |
| Agent observability & evals | Gateway activity and request logs | Available management operations; not every agent trace |
| Production observability | External MCP tools | Only the registered upstream server’s coverage |
Listing gateway budgets and querying a monitoring server are different operations. Select the connector and credential appropriate to each.
What can an AI agent do with LiteLLM?
Read-only mode still requires an administrator
LITELLM_ADMIN_READ_ONLY=true restricts exposed operations. It does not make a proxy_admin_viewer or team-admin credential acceptable.
Guard: Confirm the personal key’s role before diagnosing a transport failure.
Do you need the MCP server at all?
Use the gateway’s management API or administration UI for direct control. Use LiteAdmin when an agent should discover those management operations.
Use MCP Gateway for upstream tools; it does not substitute for the administration connector.
LiteLLM integration setup
Use the current vendor setup instructions for your client and operating system. The local connector requires uv and Python 3.12 or later, and must reach the gateway’s /openapi.json and management APIs.
Local stdio administration
Follow the official client configurations for Claude Code, Codex or Claude Desktop. Set LITELLM_BASE_URL and a personal LITELLM_API_KEY. Pin a reviewed release or commit when you need reproducible execution.
Restrict operations
Set LITELLM_ADMIN_READ_ONLY=true and, when appropriate, LITELLM_ADMIN_TOOLS=list_keys,list_teams. Restart the connection after changing restrictions. The administrator credential requirement still applies.
Hosted Streamable HTTP
Operate a trusted connector behind HTTPS, configure LITELLM_MCP_PUBLIC_URL, and let each client send its own personal bearer key. The documented endpoint is your hosted /mcp route; this setup does not supply browser OAuth login.
Read-only access, permissions and security
Treat the personal proxy-admin key as an administrative credential even when only read tools are exposed.
Keep gateway and provider keys out of chat and version control. Configure the client’s supported credential mechanism.
After a write times out, inspect the affected object before retrying; a timeout does not establish that the change failed.
Troubleshooting
- Unauthorized or forbidden
- Check the personal key’s active status and proxy_admin role. Read-only mode does not grant access to other roles.
- Missing management tools
- Check
/openapi.json, management API reachability and the operation catalog for your gateway version. Tool availability depends on the gateway schemas and entitlements.
What the vendor documents
LiteLLM's setup page lists four jobs for LiteAdmin: creating virtual keys, adding model deployments, managing teams and budgets, and checking spend and request logs.
Should you connect an agent to LiteLLM?
Yes, if you hold a personal proxy_admin key: LiteAdmin for gateway management, MCP Gateway for upstream tools. Best for gateway operators who can authorize and verify a scoped administration workflow.
- Strongest fit
- Yes, if you hold a personal proxy_admin key: LiteAdmin for gateway management, MCP Gateway for upstream tools.
- Main advantage
- An explicit administration surface exposes management operations to the agent.
- Main weakness
- Even read operations require a personal administrator identity.
- Operational risk
- Broad credentials and write tools require deliberate restrictions.
From Oodle
One platform for agent traces and infrastructure
Agent traces usually sit in a different product from the rest of your telemetry, so when a slow database makes an agent slow the symptom is in one tool and the cause is in another. Oodle keeps both in one query surface.
See agent observabilityFrequently asked questions
Does LiteLLM have an MCP server of its own?
Yes. LiteAdmin MCP is the documented gateway-management connector. MCP Gateway routing is a separate integration.
Can a viewer key use the read-only tools?
No. LiteAdmin requires proxy_admin for every tool, reads included. Read-only mode hides write tools but does not lower the role required.
Is the tool count fixed?
No. LiteAdmin ships 65 reviewed admin operations and exposes only those your gateway's /openapi.json supports.
