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
- AlicenseAqualityBmaintenanceMCP 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 gradedqualityFmaintenanceMCP server for Langfuse providing 50 tools for prompt management, observability, instance/organization management, and metrics tracking via natural language.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that provides tools to interact with the LiteLLM proxy API, enabling LLM completions, embeddings, image generation, and admin operations.MIT
- AlicenseNot gradedqualityCmaintenanceAn 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 gradedqualityBmaintenanceEnables agents to administer a LiteLLM gateway by creating and managing keys, model deployments, teams, budgets, and spending through MCP.5MIT- 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
Descriptions carefully cross-reference sibling tools, but with 194 tools there are many near-parallel surfaces that invite misselection: integration-level vs server-level capabilities/workspaces/user access, provider vs integration vs virtual key, rate-limit vs usage-limit, and prompt version vs publish vs promote vs migrate. Boundaries are mostly explained, yet the sheer density of similar list/get/update triplets makes confusion likely.
Almost all names follow a predictable verb_noun snake_case convention (list_*, get_*, create_*, update_*, delete_*), with reasonable variants like register_deployment, archive_deployment, rotate_api_key, and test_mcp_server. Minor deviations exist, such as get_cache_hit_latency/get_cache_hit_rate/get_cache_summary amid the *_analytics family, but the pattern remains clear.
194 tools is an extreme surface for a single MCP server, far beyond the rubric's 50+ threshold. Even though the platform domain is broad, this count creates excessive selection burden and suggests the surface should be partitioned or consolidated.
Coverage is very broad: CRUD for workspaces, users, invites, configs, deployments, API keys, virtual keys, providers, integrations, MCP integrations/servers, guardrails, access policies, rate limits, usage limits, prompts, collections, partials, labels, feedback, logs, and exports. Minor gaps remain, such as no obvious list/get/delete for feedback records and limited log retrieval beyond get_log, but most lifecycle workflows are represented.