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.
      2 npm
      MIT

    • MCP Gateway

      cociweb
      A
      license
      Not graded
      quality
      D
      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

    • Lazy-Loader

      aspirin106
      A
      license
      Not graded
      quality
      C
      maintenance
      Starts local MCP backend servers only when their tools are called, exposes their tools through a single stdio gateway, preserves stateful sessions, and can stop safely restartable backends after idle timeouts.
      3 npm
      MIT

    • MCPDog

      SIE-Operations-and-Maintenance-Team
      A
      license
      Not graded
      quality
      A
      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.
      17 npm
      MIT

    • MCP Proxy Server

      Nunes28
      A
      license
      Not graded
      quality
      A
      maintenance
      Aggregates multiple backend MCP servers (Stdio, SSE, and Streamable HTTP) into a single unified endpoint, exposing their combined tools and resources via SSE, Streamable HTTP, or Stdio. It also offers an optional web admin UI for managing server connections, tool enablement, and live configuration reloads.
      52 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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