Skip to main content
Glama
tpavelek

MCP-Hub-MCP Server

by tpavelek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to MCP-Hub-MCP Server

No user-submitted related servers found.

    Related Servers

    • hyper-mcp

      kranners
      A
      license
      Not graded
      quality
      F
      maintenance
      A configurable MCP server wrapper for Cursor that eliminates tool count limits when using the Model Context Protocol.
      15
      10
      GPL 3.0

    • octoport

      nullarch
      A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted MCP hub that unifies multiple MCP server configurations behind a single local endpoint, with a web dashboard for management, live tool-call logging, and per-person access tokens.
      4
      MIT

    • MCP of MCPs

      eliavamar
      A
      license
      Not graded
      quality
      D
      maintenance
      A meta-server that aggregates multiple MCP servers into a single interface, reducing token usage by 98%+ through progressive tool discovery and direct code execution that processes data between tools without consuming context window space.
      16
      10
      Apache 2.0

    • Agent Construct

      ai-mcp-garage
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server implementation that standardizes how AI applications access tools and context, providing a central hub that manages tool discovery, execution, and context management with a simplified configuration system.
      13
      -

    • mcp-context-hub

      coco4atJP
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables managing multiple MCP servers through a fixed set of hub tools, with on-demand server startup, tool discovery, and skill retrieval.
      Apache 2.0
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes with no overlap: one is for calling specific tools from servers, while the other is for listing all available tools. An agent can easily tell them apart as they serve different functions in the tool management workflow.

    Naming Consistency4/5

    The tool names follow a consistent verb_noun pattern (call-tool, list-all-tools) with clear actions and objects. The hyphenated style is used consistently, though 'list-all-tools' includes a modifier ('all') which is a minor deviation from a pure verb_noun structure.

    Tool Count2/5

    With only 2 tools, the server feels thin for its apparent purpose of managing MCP tools across servers. While it covers basic operations (call and list), more comprehensive tool management (e.g., discover servers, configure connections) is missing, making the scope underdeveloped.

    Completeness2/5

    The tool surface is severely incomplete for managing an MCP hub. It lacks essential operations such as discovering or connecting to servers, managing server configurations, or handling errors. The two tools provide only minimal functionality, leaving significant gaps that will hinder agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources