Skip to main content
Glama
karun99

glama-gateway-mcp

by karun99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to glama-gateway-mcp

No user-submitted related servers found.

    Related Servers

    • openapi-to-mcp

      The-Swarm-Corporation
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      7
      Apache 2.0
    • GPTProto MCP by gptproto-ai

      GPTProto MCPofficial

      gptproto-ai
      A
      license
      A
      quality
      C
      maintenance
      Enables AI hosts to discover GPTProto models, retrieve live pricing, make documented API requests, submit custom generations, and poll asynchronous tasks through local MCP tools.
      9
      91 npm
      MIT

    • RanchHand

      anteew
      -
      license
      C
      quality
      Not graded
      maintenance
      Enables 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
      -

    • Relay

      adarshp14
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 4 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources