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

    • mcp-router

      adeev-mardia
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables clients to connect once and access the union of multiple backend MCP servers' tools through a single unified interface, with namespaced tool routing, capability search, and health isolation.
      MIT

    • 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

    • MCP Proxy Server

      rberg59762
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables clients to connect through a unified MCP endpoint that aggregates and routes requests to multiple backend MCP resource servers, exposing their combined tools and resources with optional authentication and management.
      105 npm
      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.
      775 npm
      2,587
      Apache 2.0

    • MCP Nexus

      dsk-dev-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a single MCP endpoint that dynamically discovers, routes, policy-checks, and executes hundreds of MCP tools from any agent, with optional LLM-based routing.
      3 npm
      1
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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

    ActivityStale
    ResponsivenessNo issues

    Resources