Skip to main content
Glama
lleontor705

cli-orchestrator-mcp

by lleontor705
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to cli-orchestrator-mcp

No user-submitted related servers found.

    Related Servers

    • agent-pool-mcp

      rnd-pro
      A
      license
      A
      quality
      D
      maintenance
      Multi-agent orchestration server that enables parallel task delegation, sequential pipelines, cron scheduling, and cross-model peer review via CLI providers like Codex, Antigravity, OpenCode, and Claude Code.
      42
      7 npm
      5
      MIT

    • Zen MCP

      jray2123
      F
      license
      Not graded
      quality
      D
      maintenance
      An orchestration server that enables AI agents to collaborate across multiple AI models for advanced code analysis, debugging, and development workflows. It maintains context persistence across sessions, allowing agents like Claude to delegate subtasks to other models like Gemini or O3 seamlessly.
      41
      -

    • overmind-mcp

      DeamonDev888
      A
      license
      Not graded
      quality
      B
      maintenance
      Orchestrates and controls multiple AI agent CLIs (Claude-Code, Gemini-cli, etc.) via a unified MCP server, enabling complex multi-agent missions with shared memory and HTTP singleton architecture.
      344 npm
      2
      MIT

    • Multi-Provider LLM MCP Server

      itachiuchihadev
      F
      license
      A
      quality
      B
      maintenance
      Unified MCP server for querying multiple LLM providers (Gemini, OpenAI, Anthropic, etc.) with advanced routing, cost optimization, and fallback resilience.
      2
      3 npm
      -
    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.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: execution, statistics, listing, and routing. No overlap exists; an agent can easily distinguish them.

    Naming Consistency5/5

    All tools follow the consistent pattern 'cli_<verb>', with verbs (execute, stats, list, route) clearly describing the action. No mixing of conventions.

    Tool Count5/5

    Four tools is well-scoped for an orchestration server covering execution, monitoring, listing, and routing. Each tool earns its place.

    Completeness4/5

    Core workflows (execute, monitor, list, route) are covered. Missing provider installation/removal, but that may be out of scope for an orchestrator.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources