litellm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| litellm_versionA | Get the MCP server version and the LiteLLM service readiness.
|
| litellm_adminA | Proxy-global LiteLLM administration (high risk): proxy-global settings, allowed IPs, global spend reset, bulk user update. Call with operation="help" to list all available admin operations. Otherwise pass the operation name and a JSON object with parameters. Example: litellm_admin(operation="AddAllowedIp", params={"ip": "1.2.3.4"}) |
| litellm_deleteB | Delete LiteLLM resources (destructive, irreversible), including cache flushall. Call with operation="help" to list all available delete operations. Otherwise pass the operation name and a JSON object with parameters. Example: litellm_delete(operation="DeleteKeys", params={"keys": ["sk-..."]}) |
| litellm_executeA | Execute reversible actions on LiteLLM resources: block/unblock toggles, key regenerate/reset, connection tests, targeted cache delete. Call with operation="help" to list all available execute operations. Otherwise pass the operation name and a JSON object with parameters. Example: litellm_execute(operation="BlockKey", params={"key": "sk-..."}) |
| litellm_readA | Query LiteLLM proxy data (safe, read-only): lists, infos, spend/usage, health, settings reads, token/cost utils, MCP gateway registry reads. Call with operation="help" to list all available read operations. Otherwise pass the operation name and a JSON object with parameters. Example: litellm_read(operation="ListKeys") |
| litellm_write | Create or update LiteLLM resources (non-destructive): keys, teams, users, orgs, customers, budgets, models, credentials, tags, guardrails, fallbacks, MCP servers/toolsets, access groups. Call with operation="help" to list all available write operations. Otherwise pass the operation name and a JSON object with parameters. Example: litellm_write(operation="GenerateKey", params={"team_id": "..."}) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nikitatsym/litellm-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server