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
- 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 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
- AlicenseAqualityAmaintenanceEnables 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
- AlicenseNot gradedqualityCmaintenanceEnables Claude and Codex agents to delegate implementation, testing, research, or review tasks to each other through local MCP tools, while supporting persistent sessions, isolated editing workspaces, and reviewed integration. It also allows progress tracking, cancellation, model selection, and management handoff between providers.2MIT
- AlicenseNot gradedqualityBmaintenanceA local-first MCP server for AI coding agents that shares structured execution state, routes context deltas, and provides preflight nudges to prevent conflicts and stale decisions.MIT
TDQS
Scored across 14 tools
Most tools are clearly distinct (queue, inspect, wait, approve, cancel, retry), but retry_fallback and escalate_task both handle failed read-only tasks with overlapping semantics, potentially causing misselection.
Predominantly follows a lowercase verb_noun pattern (delegate_task, get_task, list_tasks), with a few deviations like 'orchestrate' and 'doctor' that are still readable but break the pattern.
14 tools cover a complex orchestration lifecycle (planning, delegation, monitoring, control, retry) without redundancy; each tool serves a distinct operational need.
Covers the full task lifecycle: creation, retrieval, monitoring, approval, cancellation, retry strategies, plus diagnostics and telemetry. No obvious dead ends or missing core operations.