DeltaRoute MCP Server
Related Servers
Alternatives to DeltaRoute MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding providers to run structured multi-agent workflows with document specifications, tracked tasks, handoffs, and server-owned health evidence. It coordinates task claims, repairs, reviews, and completion gates across Claude Code, Codex CLI, Cursor, Grok Build, and OpenCode.29 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables Codex to delegate bounded tasks to multiple AI model workers through a persistent OpenCode 2 service, with isolated Git worktrees and safe patch review and application.-
- AlicenseNot gradedqualityAmaintenanceGives AI coding providers a structured, provider-agnostic workflow for managing specifications, tracked tasks, handoffs, and health-gated completion evidence. Enables coordinated multi-role workflows in which tasks are claimed, logged, and verified by server-owned health checks before work is marked done.29 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding providers to run structured multi-agent workflows with specs, tracked tasks, handoffs, health gates, and audited repair mode.29 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables local, bounded routing and evidence judgments for Codex tasks, with tools for reading file context, checking outputs, and selecting registered workflows while keeping execution and review with the client.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding providers to run structured multi-agent workflows with shared documents, tracked tasks, handoffs, and health evidence, supporting providers such as Claude Code, Codex CLI, Cursor, Grok Build, and OpenCode.29 npmMIT
TDQS
Scored across 5 tools
list_workers and recommend_route are related but distinguishable (availability vs routing advice). submit_task, get_task, and cancel_task form a clear task lifecycle, though submit_task also bundles heavy-workflow subcommands, slightly blurring its scope.
All tool names follow a consistent snake_case verb_noun pattern: list_workers, recommend_route, submit_task, get_task, cancel_task. The convention is predictable and easy to scan.
Five tools cleanly cover worker listing, route recommendation, and task submit/get/cancel. The count is well-scoped with no obvious bloat or missing essential standalone operations.
The core delegation lifecycle is covered: discover workers, get a route recommendation, submit, retrieve, and cancel tasks. Minor gaps include no list_tasks/status browsing and heavy workflow operations folded into submit_task rather than exposed separately.