portkey-admin-mcp
Related Servers
Alternatives to portkey-admin-mcp
- AlicenseAqualityDmaintenanceConnects Claude to Portkey's API for managing AI configurations, workspaces, analytics, and user access, providing comprehensive control over API usage and settings.94MIT
Related Servers
- AlicenseAqualityAmaintenanceMCP server for the LiteLLM proxy, enabling agents to administer resources like keys, teams, users, models, and proxy settings through risk-graded meta-tools.6MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Langfuse providing 50 tools for prompt management, observability, instance/organization management, and metrics tracking via natural language.9 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that provides tools to interact with the LiteLLM proxy API, enabling LLM completions, embeddings, image generation, and admin operations.14 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server suite for administering LiteLLM gateways, exposing tools to manage models, keys, teams, users, and spending, along with an admin GUI and an encrypted reverse proxy for secure access.MIT

litellm-admin-mcpofficial
AlicenseNot gradedqualityAmaintenanceEnables agents to administer a LiteLLM gateway by creating and managing keys, model deployments, teams, budgets, and spending through MCP.MIT- FlicenseNot gradedqualityDmaintenanceExposes LiteLLM Proxy admin APIs as MCP tools for managing internal users, virtual keys, and spend logs via streamable-http, enabling agents to administer LiteLLM without custom HTTP glue.1-
TDQS
Scored across 184 tools
Tools are generally well-differentiated by resource and action, and many descriptions explicitly cross-reference alternatives (e.g., 'use X instead of Y'). However, with 184 tools, some overlap remains, especially among the numerous analytics variants and the many CRUD sets for similar resources, which could cause occasional misselection.
The vast majority of tool names follow a consistent snake_case verb_noun pattern (create_, get_, list_, update_, delete_). There are a few domain-specific verbs (upsert_, replace_, rotate_, publish_, migrate_, reset_, disconnect_) that deviate slightly, but the overall convention is predictable and readable.
184 tools is far beyond the typical 3–15 range and qualifies as an extreme mismatch. Even for a comprehensive admin platform, this volume risks overwhelming agents and makes tool discovery and selection impractical without strong external filtering.
The surface covers an enormous breadth of the Portkey admin domain, including full CRUD for most resources, analytics, and specialized operations. Minor gaps exist, such as no list or delete for feedback and no list_logs (only get_log and insert_log), but overall coverage is remarkably complete.