litellm-admin-mcpofficial
A
licenseNot graded
qualityA
maintenanceEnables agents to administer a LiteLLM gateway by creating and managing keys, model deployments, teams, budgets, and spending through MCP.
MIT
Kong Admin API MCP Server
by Monohitoxx
Related Servers
Alternatives to Kong Admin API MCP Server
No user-submitted related servers found.
Related Servers
- 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-
- AlicenseDqualityDmaintenanceExposes all Dokploy API endpoints as MCP tools, enabling AI models and other clients to manage projects, applications, databases, and more on a Dokploy server.10016 npmApache 2.0
- FlicenseNot gradedqualityDmaintenanceDynamically exposes any OpenAPI/Swagger API as tools for AI assistants, automatically generating MCP tools from OpenAPI specs with authentication support.-
- AlicenseNot gradedqualityDmaintenanceExposes SAP AI Core APIs as MCP tools, enabling AI assistants to manage AI Core lifecycle and administration through natural language.7MIT
- AlicenseAqualityAmaintenancePortkey Admin API control-plane MCP server with Prisma AIRS interoperability guidance.184809 npm6MIT
TDQS
A4.1/5.0
Scored across 13 tools
Disambiguation5/5
Each tool targets a distinct action (configure, create, delete, get, list, update, upsert) or specific resource (workspaces, node info, node status, plugin schema). The generic kong_request tool fills gaps without overlapping with the CRUD tools. No two tools have ambiguous purposes.
Naming Consistency5/5
All tools follow the 'kong_<verb>' or 'kong_<verb>_<noun>' pattern consistently, using lowercase with underscores. Examples: kong_create, kong_list_workspaces, kong_node_info. This pattern makes prediction and selection straightforward for an agent.
Tool Count5/5
With 13 tools, the set is well-scoped for a Kong Admin API client. It covers connection management, CRUD operations, node diagnostics, plugin schema inspection, and a fallback generic request. No tool feels superfluous or missing.
Completeness5/5
The tools provide full lifecycle coverage for Kong entities (create, read, update, delete, upsert, list with pagination). The node info/status tools cover administrative monitoring, and the generic kong_request handles any API endpoint not explicitly exposed (e.g., RBAC, declarative config). No obvious gaps.
Maintenance
ActivityInactive
ResponsivenessNo issues