Skip to main content
Glama

Related Servers

Alternatives to McpHub

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding-agent clients to use one local MCP endpoint that routes calls to isolated per-account workers, shares a single tool surface across sessions, and applies per-account policies and key pools.
      10 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Presents multiple stdio backend tool servers to an MCP client as one aggregated server, sharing those backend processes across concurrent agent sessions through a background broker while namespacing and routing each tool call to the right backend. Servers can be run shared, per-session, or lazily, with automatic restart and request ID remapping so many sessions coexist without collisions.
      MIT
    • 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.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides any MCP-capable coding agent with shared, warm language-server intelligence and project-local configuration, so diagnostics, definitions, references, hover, symbols, code actions, formatting, rename, and sync behave consistently across harnesses and sessions. This lets users switch agent tools without reconfiguring LSP integrations or falling back to CLI verification.
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to list and call tools from multiple configured servers while each backend starts only on first use, is shared across sessions, and stops when idle. This reduces memory and process overhead without changing tool names or permissions.
      15 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to run declarative agents and DAG workflows as plain tools, with parallel nodes, review loops, and per-run least-privilege sandboxing.
      5 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct operation: lifecycle CRUD, restart, context setting, tool discovery, and proxied invocation. list/get and tools/call are clearly separated by scope, so misselection is unlikely.

    Naming Consistency4/5

    All tools use the mcp_ prefix and snake_case, and most follow a verb_noun or verb pattern. mcp_tools is noun-based while mcp_set_context is a longer verb phrase, which is a minor inconsistency.

    Tool Count5/5

    Nine tools are well scoped for a sub-MCP manager: lifecycle operations, context, discovery, and invocation are all covered without filler. The count matches the server's purpose.

    Completeness4/5

    The surface covers CRUD lifecycle management plus restart, context, tool discovery, and proxied calls. Minor gaps exist around diagnostics/logs or explicit enable/disable controls, but core workflows are complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues