Skip to main content
Glama
fyrlabs

mcp-nexus

by fyrlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-nexus

No user-submitted related servers found.

    Related Servers

    • MetaMCP

      WebpageFX
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables dynamic aggregation of multiple MCP servers into a unified endpoint with middleware, orchestration, and gateway capabilities.
      MIT

    • 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.
      547 npm
      2,426
      Apache 2.0

    • MCP Server Proxy

      hr98w
      A
      license
      Not graded
      quality
      D
      maintenance
      Aggregates multiple MCP servers into a single endpoint, enabling LLM clients to access tools, resources, and prompts from various backends through one connection.
      7 npm
      MIT

    • Master MCP Server

      Jakedismo
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Aggregates multiple MCP servers behind a single, secure endpoint with unified tool/resource discovery, OAuth authentication, and resilient request routing. Enables users to manage and interact with multiple MCP backends through one centralized interface with load balancing and circuit breakers.
      2
      -

    • Smart MCP Proxy

      Dumbris
      A
      license
      Not graded
      quality
      D
      maintenance
      Federating gateway for AI agents to discover and call tools from multiple MCP servers with intelligent search and dynamic tool registration.
      39
      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.8/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a clear operational role: searching servers, searching capabilities, describing schemas, and executing. search_servers and search_capabilities are adjacent but their descriptions clearly separate domain-level server ranking from capability-level search.

    Naming Consistency4/5

    All tool names follow a consistent verb_noun snake_case pattern. The only minor inconsistency is 'capabilities' being plural in search/describe but singular in execute_capability.

    Tool Count5/5

    Four tools is well-scoped for a gateway or meta-server: discover servers, discover capabilities, inspect schemas, and execute. There is no redundancy or unnecessary bloat.

    Completeness4/5

    The discover → describe → execute workflow is covered end-to-end. Minor gaps such as explicit list-all-server or dedicated server metadata retrieval are missing, but search_servers can largely cover discovery needs.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources