glama-gateway-mcp
Related Servers
Alternatives to glama-gateway-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to call any OpenAPI-defined API by automatically converting its operations into tools, with built-in support for authentication, rate limiting, and response handling.7Apache 2.0

GPTProto MCPofficial
AlicenseAqualityCmaintenanceEnables AI hosts to discover GPTProto models, retrieve live pricing, make documented API requests, submit custom generations, and poll asynchronous tasks through local MCP tools.913 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to browse products, look up orders, and place orders through MCP tools, with API-key authentication, rate limiting, and idempotent order operations.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.4MIT- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible applications to manage and use local or cloud-hosted models, including listing, pulling, generating, chatting, embeddings, and web search/fetch through a unified tool interface.897 npmAGPL 3.0
- -licenseCqualityNot gradedmaintenanceEnables interaction with OpenAI-compatible APIs (like Ollama) through MCP tools. Provides access to chat completions, model listings, and embeddings generation from local or remote OpenAI-style endpoints.3-
TDQS
Scored across 4 tools
list_models and request_status are clearly distinct, but chat_completion and stream_completion overlap in purpose as they both perform chat completions. The descriptions clarify streaming vs. non-streaming, so an agent can differentiate them, though some ambiguity remains.
All tool names share the glama_ prefix and follow a consistent snake_case verb_noun pattern. The naming is predictable and uniform across the set.
Four tools is well-scoped for a gateway-focused server covering model discovery, completion, streaming, and status lookup. Each tool has a clear, non-redundant role.
The core workflow of listing models and running both standard and streaming completions is covered, plus status lookup for async requests. Minor additions like request cancellation or model details would improve completeness, but no critical gap exists.