Skip to main content
Glama
rupinder2

mcp-orchestrator

by rupinder2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-orchestrator

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

    • mcp_proxy

      anjani78
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables centralized routing, discovery, namespacing, and execution of tools from multiple remote MCP servers over HTTP/SSE, aggregating them behind a unified MCP gateway with dynamic server management.
      -

    • super-mcp

      nidamen
      A
      license
      Not graded
      quality
      C
      maintenance
      A gateway that aggregates multiple MCP servers into a single endpoint, namespacing their tools and forwarding calls, so an agent connects to one MCP to access the entire stack.
      MIT

    • nexus

      likhithreddy
      A
      license
      Not graded
      quality
      D
      maintenance
      Acts as an MCP gateway aggregating multiple child MCP servers into a single namespaced interface, with an optional memory layer that caches tool results to reduce redundant calls.
      19 npm
      MIT

    • MCP Gateway (Parent MCP

      TomCat2357
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables centralized management and unified interface for multiple child MCP servers (filesystem, sqlite, etc.), allowing users to discover, launch, and execute tools across different MCP servers through a single gateway.
      -

    • tap

      fschrhunt
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to reduce tool noise by exposing only two meta-tools for searching downstream MCP servers and calling their tools on demand. Connections are lazy and tool lists are cached, so configured servers can be used without loading every tool upfront.
      387,930 npm
      MIT
    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.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one searches/disovers tools across servers, the other invokes a specific remote tool. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    Both names are snake_case and descriptive, but 'tool_search' follows a noun_verb pattern while 'call_remote_tool' follows verb_remote_noun. This is a minor inconsistency; renaming to 'search_tools' would make it perfectly uniform.

    Tool Count3/5

    With only 2 tools, the server feels slightly thin for an orchestrator role. The tool count is borderline below the typical 3-15 range, but the two tools cover core orchestration functions (discovery and invocation).

    Completeness3/5

    The pair covers the main workflow: search for tools and call them. However, missing operations like listing registered servers, checking server health, or managing registrations mean the surface is not fully complete for a comprehensive orchestrator, though workable for basic flows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources