LightWorker
Related Servers
Alternatives to LightWorker
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA local-first MCP orchestration server that uses Codex as lead planner and Antigravity as host to delegate and review bounded tasks with Git integration and persistent SQLite state.Apache 2.0
- AlicenseAqualityDmaintenanceAn 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 gradedqualityBmaintenanceEnables Codex to orchestrate multiple Claude Code sub-agents through a local MCP service, with automatic parallel scheduling, dependency handoffs, progress reporting, permission Q&A, acceptance review, and session recovery.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables local multi-agent Codex collaboration through a SQLite task graph, atomic task claiming and leases, isolated Git worktrees, append-only events and messages, and a local web Kanban board.MIT
- AlicenseNot gradedqualityBmaintenanceA local MCP control plane for Codex that manages task queues, dynamic roles, and side-panel team collaboration with persistence, dependency gating, and structured reporting.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to delegate scoped tasks across multiple providers like Codex, Claude Code, and Antigravity through a single local MCP server, with quota monitoring, notifications, and remote control via messaging apps.132Apache 2.0
TDQS
Scored across 18 tools
Most tools have a distinct resource/action: delegation (delegate_task, delegate_batch, orchestrate), task lifecycle (approve/cancel/retry/escalate), and native subagent lifecycle are separated. Boundaries are mostly clear, though retry_fallback vs escalate_task and the multi-step native_* flow require careful reading.
Names are overwhelmingly snake_case and follow verb_noun for most operations (get_task, list_tasks, cancel_task, delegate_batch). Exceptions like doctor, orchestrate, and the native_subagent_* resource_event pattern are minor deviations rather than chaotic.
18 tools is slightly above the typical 3-15 range, but the orchestration domain is broad and each tool maps to a distinct lifecycle step or diagnostic. It is heavy but not obviously bloated.
The surface covers delegation, orchestration, task inspection/waiting/events, approval, cancellation, fallback/escalation, diagnostics, cache metrics, and native subagent lifecycle. Minor gaps like explicit approval rejection or lease release are workaroundable, and some workflow references external host tools (spawn_agent, wait_threads).