Skip to main content
Glama
Consiliency

PMCP

by Consiliency
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to PMCP

No user-submitted related servers found.

    Related Servers

    • my-cool-proxy

      karashiiro
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server gateway that reduces context bloat through progressive tool discovery and Lua-based tool chaining, while centralizing multiple MCP servers into a single endpoint.
      15
      MIT

    • MCP Gateway

      MikkoParkkola
      F
      license
      A
      quality
      A
      maintenance
      A multiplexing gateway that aggregates multiple MCP servers into a single port, significantly reducing context token usage through a Meta-MCP discovery system. It enables dynamic tool discovery and invocation across various transport protocols including stdio, HTTP, and SSE.
      15
      75
      -

    • super-mcp

      nidamen
      A
      license
      Not graded
      quality
      C
      maintenance
      A gateway that aggregates multiple MCP servers into a single endpoint, namespacing their tools and forwarding calls, so an agent connects to one MCP to access the entire stack.
      MIT

    • Caplets

      spiritledsoftware
      A
      license
      Not graded
      quality
      A
      maintenance
      A progressive-disclosure gateway for MCP servers that keeps tool lists small by exposing one top-level tool per server, allowing agents to search, list, inspect, and call underlying tools within a selected domain.
      14
      MIT

    • MCPNexus

      KrzysztofAugiewicz
      A
      license
      A
      quality
      B
      maintenance
      A discovery and routing layer for MCP servers that loads tool definitions on demand, reducing token usage by keeping servers out of the context window until needed.
      4
      MIT

    • mcp-orchestrator

      rupinder2
      A
      license
      A
      quality
      D
      maintenance
      Enables connecting multiple downstream MCP servers into a single gateway, with unified tool search, namespacing, and deferred loading to preserve context window.
      2
      6
      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.6/5.0

    Scored across 26 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with descriptive names and detailed descriptions. Ambiguities like gateway.cancel vs gateway.tasks_cancel are explicitly resolved in the descriptions, so agents can reliably differentiate them.

    Naming Consistency5/5

    All tools follow a consistent `gateway.` prefix with lowercase snake_case verbs and nouns (e.g., list_pending, config_status, search_registry). The naming pattern is uniform and predictable across the entire set.

    Tool Count2/5

    With 26 tools, the count exceeds the recommended upper bound of 25 for a cohesive toolset. While the gateway domain is broad, several tools could be consolidated (e.g., merging status/check tools) to reduce cognitive overhead.

    Completeness4/5

    The tool surface covers core lifecycle operations: discovery, provisioning, invocation, task management, config, health, and feedback. Minor gaps exist (no explicit uninstall/remove server tool), but the common workflows are well-supported.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources