Skip to main content
Glama
Phoenixrr2113

Orchestrator MCP

by Phoenixrr2113
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Orchestrator MCP

No user-submitted related servers found.

    Related Servers

    • Codebase Intelligence MCP

      Saptak-cyber
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-grade MCP server providing advanced code intelligence capabilities such as semantic search, dependency analysis, and natural language Q&A across multiple programming languages.
      MIT

    • DevForge-MCP

      Sanket2329
      A
      license
      Not graded
      quality
      B
      maintenance
      A production-ready MCP server that enables AI assistants to intelligently understand, analyze, edit, navigate, and review software projects with multi-workspace support, Git integration, and semantic search.
      1
      MIT

    • ArchMCP

      ShubhamScript
      A
      license
      Not graded
      quality
      B
      maintenance
      A centralized remote MCP server that gives AI coding assistants real-time microservices architecture intelligence, including service search, database schema lookup, API discovery, and change blast-radius analysis.
      1
      MIT

    • portuni

      honzapav
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that provides a shared graph of an organization's projects, processes, areas, and principles, enabling consistent context for tools and AI agents.
      2
      Apache 2.0
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: ai_process handles orchestration and execution, ai_status focuses on health monitoring, and get_info provides system introspection. An agent can easily tell them apart based on their specific functions.

    Naming Consistency4/5

    The naming is mostly consistent with a clear pattern: ai_process and ai_status use a consistent 'ai_' prefix, while get_info deviates slightly with a 'get_' prefix. The tools are readable and follow a logical structure, though not perfectly uniform.

    Tool Count3/5

    With only 3 tools, the count feels thin for an 'orchestrator' server that claims to handle complex multi-step workflows across domains like file operations and web automation. This may limit functionality or require over-reliance on the ai_process tool.

    Completeness2/5

    There are significant gaps in the tool surface for an orchestrator domain: no tools for managing workflows (e.g., list, pause, cancel), no configuration or logging tools, and no way to interact with specific subdomains directly. This could cause agent failures when needing fine-grained control.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources