A
licenseA
qualityB
maintenanceAn MCP server that lets OpenAI Codex delegate tasks to Google Gemini agents as isolated background workers, with Git worktree isolation, loop detection, and security boundary enforcement.
7
1
MIT
sol-luna-orchestrator
by mahadansar
Related Servers
Alternatives to sol-luna-orchestrator
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server that splits coding work between ChatGPT web (planning, review) and Codex CLI (implementation), enabling agentic workflows over a local repo with risk-gated execution and safety rails.23MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that lets Codex supervise Claude Code or DeepSeek Harness as workers in isolated Git worktrees, with a bridge_run/bridge_respond/bridge_apply workflow for task delegation and safe cherry-pick integration.5 npmMIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server that enables Codex and other MCP clients to orchestrate native external coding-agent harnesses through a normalized lifecycle, with guarded execution and deterministic testing.191 PyPIMIT
- AlicenseAqualityCmaintenanceA local MCP server that lets Claude delegate scoped work to Codex with structured results and guardrails, supporting planning, code review, build, reverse engineering, and long-running background tasks.11MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that bridges Codex with DeepSeek Harness to delegate coding tasks into isolated worktrees, providing profile-based model routing, single/multi-agent orchestration, and reviewable artifacts.6 npm1Apache 2.0
TDQS
A4.4/5.0
Scored across 5 tools
Disambiguation4/5
The single, batch, continuation, preflight, and exploration tools have distinct purposes, but delegate_task and delegate_tasks overlap at the single-task boundary; the descriptions explicitly resolve this by directing single tasks to delegate_task.
Naming Consistency4/5
Most names follow snake_case verb_object style (delegate_task, deegate_tasks, continue_task), but routing_preflight is noun-leading and explore is a bare verb, breaking the otherwise predictable pattern.
Tool Count5/5
Five tools cover the core orchestration surface without redundancy: single delegation, batch delegation, continuation, preflight routing, and read-only exploration. The count feels intentionally scoped and appropriate.
Completeness4/5
Core lifecycle operations are covered: delegate, batch, continue, preflight, and explore. Minor gaps exist such as no explicit status/cancel/list tooling, but the parent-owned model makes these nonessential and workable.
Maintenance
ActivityMaintained
ResponsivenessNo issues