Skip to main content
Glama
quan2005

MCP Compact

by quan2005
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP Compact

No user-submitted related servers found.

    Related Servers

    • gtwmcp

      pcandido
      A
      license
      Not graded
      quality
      D
      maintenance
      Aggregates multiple MCP servers behind a single stdio interface, supporting stdio-based and HTTP SSE-based upstreams with OAuth.
      5 npm
      MIT

    • MCP Gateway

      cociweb
      A
      license
      Not graded
      quality
      C
      maintenance
      Aggregates multiple upstream MCP servers (stdio, streamable-http, sse, websocket) behind a single streamable-HTTP endpoint with declarative configuration, namespacing, filtering, and auto-reload.
      MIT

    • MCPDog

      QiuZwan
      A
      license
      Not graded
      quality
      B
      maintenance
      Aggregates multiple MCP sub-servers into a single unified entry point, supporting stdio and Streamable HTTP protocols, with a web-based management interface for configuration, routing, and tool management.
      41 npm
      MIT

    • mcp-gateway

      jj13jp
      F
      license
      Not graded
      quality
      D
      maintenance
      Aggregates multiple child MCP servers into a single MCP server endpoint, enabling clients to use various tools (e.g., filesystem, Brave Search) through one interface.
      38 npm
      -

    • mcp-gateway

      KaryawanSurga
      A
      license
      Not graded
      quality
      A
      maintenance
      Aggregates many MCP servers behind one local endpoint with namespaced tools, profiles, policy, budgets, audit logs, and a dashboard over stdio or HTTP.
      38 npm
      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

    A3.5/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools are clearly separated by purpose: invoke handles tool calls and read handles resource access. The descriptions provide explicit examples and modes to guide usage, though the generic proxy nature could occasionally blur the line between a tool and a resource.

    Naming Consistency5/5

    Both tool names are single-word verbs in a consistent imperative style, making them predictable and easy to remember. There is no mixing of conventions or misleading synonyms.

    Tool Count4/5

    With only two tools, the set is intentionally minimal but well-suited for a compact projection surface that forwards to a larger MCP ecosystem. While it feels thin compared to direct-integration servers, its purpose justifies the small count.

    Completeness3/5

    The server covers the core interaction patterns (invoking tools and reading resources) and includes validation/preview modes. However, it lacks an explicit discovery mechanism to list available servers, tools, or resource templates, which could be a significant gap for agents without prior knowledge.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources