Skip to main content
Glama
mcprating

MCP Gateway

by mcprating
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MCP Gateway

No user-submitted related servers found.

    Related Servers

    • Multi-MCP Proxy

      kfirtoledo
      A
      license
      Not graded
      quality
      D
      maintenance
      A flexible MCP proxy server that connects to and routes between multiple backend MCP servers over STDIO or SSE, enabling dynamic management and namespacing of tools.
      110
      MIT

    • relay-mcp

      yujoonko1
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables developers to expose any dev tool as a safe, audited MCP server with permission tiers, audit logging, and automatic argument validation.
      MIT

    • dynamic-mcp

      mcpland
      A
      license
      B
      quality
      C
      maintenance
      Dynamic MCP server for Node.js enabling runtime tool creation, management, and execution in isolated sandboxes (Docker or Node).
      8
      3 npm
      1
      MIT

    • proxy-mcp

      Rixmerz
      F
      license
      A
      quality
      D
      maintenance
      Universal MCP proxy server that discovers, searches, and executes tools across all configured MCP servers from a single entry point.
      7
      -

    • scriptit

      shreyjindal81
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to connect to remote MCP servers once, access their tools through a compact MCP endpoint, pair a CLI inside sandboxes, and create watches that turn command or tool output into pollable structured events.
      2
      -

    • yourco-mcp

      amitmohapatra
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables developers to build MCP servers with registry-managed tool metadata, runtime hot-reloading, pluggable authentication and authorization, per-audience tool views, and resilient stateless operation.
      -
    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

    A3.6/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (connect vs disconnect vs call vs audit vs sandbox). However, mcp_discover and mcp_recommend both surface servers to connect to, and mcp_server_info overlaps somewhat with mcp_discover and mcp_list_active for information retrieval, creating mild boundary ambiguity.

    Naming Consistency4/5

    All tools share a consistent 'mcp_' prefix and mostly follow an action-oriented pattern (mcp_discover, mcp_connect, mcp_call_tool). Minor deviations like mcp_gateway_health and mcp_server_info use noun_noun rather than verb_noun, but the set remains predictable and readable.

    Tool Count5/5

    13 tools is well-scoped for a gateway managing server discovery, connection lifecycle, sandboxing, auditing, and analytics. Each tool appears to earn its place with no obvious redundancy.

    Completeness4/5

    The surface covers discovery, connect/disconnect, listing, info, tool invocation, health, sandbox, audit, profiles, groups, usage, and recommendations—a strong lifecycle. Minor gaps exist, such as no explicit reconnect/refresh or per-server tool-schema introspection beyond what mcp_server_info implies.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources