Skip to main content
Glama
igrybkov

mcp-hub

by igrybkov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-hub

No user-submitted related servers found.

    Related Servers

    • programmatic-mcp

      alesya-h
      A
      license
      Not graded
      quality
      C
      maintenance
      A meta MCP server that orchestrates other MCP servers by lazily connecting to them and exposing their tools as JavaScript libraries. It allows users to execute JavaScript code that programmatically interacts with multiple MCP servers within a unified environment.
      25 npm
      1
      MIT

    • mcp-unify

      MagnusCole
      A
      license
      Not graded
      quality
      C
      maintenance
      Unifies multiple MCP servers behind a single endpoint with lazy loading, auto-cleanup, Python plugins, and role-based filtering.
      2
      MIT

    • MetaMCP

      metatool-ai
      A
      license
      Not graded
      quality
      D
      maintenance
      MetaMCP is a MCP proxy that dynamically aggregates MCP servers into a unified endpoint, with middlewares and namespaces.
      2,695
      MIT

    • Multi MCP

      ItsJT5216
      A
      license
      B
      quality
      B
      maintenance
      A flexible proxy server that aggregates multiple backend MCP servers into a single interface using STDIO or SSE transports. It supports dynamic server management via an HTTP API and utilizes namespacing to prevent tool conflicts across connected services.
      3
      1
      MIT

    • MCPlexer

      OzTamir
      A
      license
      Not graded
      quality
      D
      maintenance
      A tiny MCP proxy for running multiple labeled instances of the same MCP server without tool-name collisions.
      7 npm
      1
      MIT

    • gateway

      KaryawanSurga
      A
      license
      Not graded
      quality
      A
      maintenance
      Aggregates multiple MCP servers behind a single endpoint so that clients can reach every one of their tools through one connection instead of configuring each server separately. It simplifies setup and keeps tool access in one place when many servers are in play.
      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.1/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct action: discovery (search/recommend_servers/list_servers), tool introspection (get_server_tools), execution (call_tool), lifecycle (reload), and auth (authenticate/auth_status). While search, recommend_servers, and list_servers all support discovery, their input modes and outputs are clearly differentiated. No two tools appear to do the same thing.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern: recommend_servers, list_servers, get_server_tools, call_tool. Minor deviations exist: search, reload, and authenticate are bare verbs, and auth_status is a noun phrase rather than get_auth_status, but overall the names are predictable and readable.

    Tool Count5/5

    Eight tools is a well-scoped size for an MCP hub, covering discovery, introspection, execution, reload, and authentication. Every tool addresses a distinct operational need with no redundant helpers or filler.

    Completeness4/5

    The tool surface covers the core hub lifecycle: discover servers, inspect tools, call tools, reload configuration, and manage authentication. Minor gaps exist, such as no explicit deauthentication/credential removal or direct server config editing, but these are reasonably handled via the host's config files and OS keychain.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources