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 gradedqualityBmaintenanceMCP 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.43 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.3MIT- 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 194 tools
Most tools are described with explicit contrast notes, but the set contains many near-sibling tools, especially the analytics family and the MCP integration/server/capability layers. An agent must read carefully to choose between tools like get_feedback_analytics, get_feedback_models_analytics, and get_feedback_scores_analytics.
Tool names consistently use snake_case with a verb_noun structure across get/list/create/update/delete/upsert/replace patterns. Long compound names are readable and no competing naming conventions are mixed.
194 tools is far beyond a manageable single MCP server surface and matches the rubric's extreme mismatch category. Even for broad enterprise administration, this should be split into multiple scoped servers.
The surface covers full lifecycle operations for most domains: API keys, workspaces, users, prompts, collections, integrations, MCP servers, guardrails, rate limits, usage limits, and analytics. Minor gaps remain, such as no general list-request-logs tool and no get operation for an individual prompt partial version.