Skip to main content
Glama

Related Servers

Alternatives to orca-cli-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to drive Orca worktrees, agent sessions, and orchestration via a single orca tool over local stdio or authenticated remote HTTP transports.
      30 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding apps to perform safe, audited git work on isolated task branches, run a project's own tests and checks, and execute multi-step workflows with terminal-only approval gates across any MCP client. Every command, file access, and cross-tool call is permission-checked, shell-free, and logged, with no pushes or destructive git operations.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for orchestrating a fleet of CLI coding agents in isolated git worktrees. It exposes tools for spawning workers, sending instructions, reviewing diffs, and merging changes, with full terminal visibility.
      7 npm
      4
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables any MCP client to start, inspect, wait for, and communicate with fleets of coding agents in worktrees, with structured status, completion events, orchestration mail, and terminal control.
      19
      339 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable chat clients like ChatGPT, Claude, and Cursor to read, search, edit, and run commands on a local machine, including git operations and browser automation. Runs as a local daemon with workspace path jails, safety modes, checkpoints, and human-in-the-loop approval for edits and shell commands.
      MIT

    TDQS

    B3.4/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools are cleanly separated by resource (repos, projects, worktrees, terminals, automations) plus a clear verb, so selection is straightforward. The few soft overlaps — orca_worktree_ps vs orca_worktree_list vs orca_task_list, and orca_agent_launch vs orca_terminal_create vs orca_worktree_create with an agent — are differentiated only by prose in the descriptions, which an agent may still skim past.

    Naming Consistency5/5

    Every tool uses the same orca_<resource>_<action> convention (orca_worktree_create, orca_terminal_read, orca_automation_run), with only a handful of bare singleton names (orca_status, orca_inbox, orca_search) that read as natural exceptions. Nothing mixes camelCase or competing verb styles.

    Tool Count4/5

    At 18 tools the surface is on the larger side, but the domain genuinely spans five sub-areas (worktrees, terminals, agents, automations, search) and each tool maps to a distinct operation. Nothing looks like filler, though a couple of read-only variants (orca_worktree_ps) could arguably fold into orca_worktree_list.

    Completeness3/5

    Creation and observation are well covered, but the lifecycle dead-ends: there is no worktree remove/delete, no terminal close/kill, no agent stop, and automations can be listed and run but not created or edited. An agent can start work but has no sanctioned way to tear it down or recover from a stuck session.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues