proxyllm-mcp
Related Servers
Alternatives to proxyllm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceMCP server for OpenRouter's management API, enabling programmatic control of credits, inference keys, guardrails, and usage analytics from MCP-compatible clients.1675 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that provides tools to interact with the LiteLLM proxy API, enabling LLM completions, embeddings, image generation, and admin operations.12 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
- FlicenseAqualityDmaintenanceUnified MCP server for querying multiple LLM providers (Gemini, OpenAI, Anthropic, etc.) with advanced routing, cost optimization, and fallback resilience.213 npm-
- 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 gradedqualityCmaintenanceAn MCP server that functions as an intelligent gateway for multiple LLM backends including OpenAI, Claude, and Ollama. It supports automatic provider fallback, streaming responses via Server-Sent Events, and real-time monitoring for robust AI integration.MIT
TDQS
Scored across 9 tools
Each tool targets a distinct resource or action: savings calculation, model listing, key introspection, signup steps, account details, key creation/listing, and usage. There is no overlap; even the sequential signup tools are separated by stage.
All tools share the 'proxyllm_' prefix and most follow a verb_noun pattern (list_models, create_routing_key, verify_signup). However, a few are noun-only (account, usage, signup) and savings_calculator is noun_noun, creating minor inconsistency.
The 9 tools are well-scoped for a gateway management service, covering signup, key lifecycle, model discovery, usage, and savings estimation. It is neither too thin nor overloaded.
The set covers the core account and key lifecycle comprehensively, including signup, verification, key creation/listing, introspection, usage, and models. Minor gaps exist such as no delete or update routing key, but they can be worked around.