Skip to main content
Glama
ni-c

mcp-hub

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-hub

No user-submitted related servers found.

    Related Servers

    • mcphub

      samanhappy
      A
      license
      Not graded
      quality
      A
      maintenance
      A unified hub for centrally managing and dynamically orchestrating multiple MCP servers/APIs into separate endpoints with flexible routing strategies.
      795 npm
      2,452
      Apache 2.0

    • mcp-gateway

      R0Wi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables clients to access multiple backend MCP servers through a single endpoint, with OAuth 2.1 authorization, namespaced tools, and secure credential management.
      MIT

    • MCP Hub

      fuwei99
      F
      license
      Not graded
      quality
      B
      maintenance
      A multi-MCP server hub that hosts several independent MCP servers (e.g., DuckDuckGo, Zhihu, Doubao, Academic) with per-path authentication, deployable on Hugging Face Spaces.
      -

    • MCP Hub

      khareemnurulla
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      MCP Hub aggregates and proxies multiple Model Context Protocol servers into a unified Streamable HTTP interface. It allows users to combine diverse stdio, SSE, and HTTP-based servers while providing tool namespacing, health monitoring, and secure authentication.
      594 npm
      -

    • octoport

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

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: discovery (list_servers, list_tools), schema inspection, execution, and lifecycle management. No two tools overlap in purpose.

    Naming Consistency5/5

    All tool names follow the consistent verb_noun pattern with snake_case, making the API predictable and easy to navigate.

    Tool Count5/5

    Six tools is well-scoped for a hub server: discovery, schema access, execution, and on-demand lifecycle management. Each tool earns its place.

    Completeness5/5

    The tool set covers the full hub workflow: listing servers, listing and inspecting tools, calling tools, and managing server lifecycle. No obvious gaps for the stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources