AdaptOrch MCP
Related Servers
Alternatives to AdaptOrch MCP
No user-submitted related servers found.
Related Servers
- FlicenseBqualityNot gradedmaintenanceBridges Claude Code to a Cloud Orchestrator API, providing access to multi-AI consensus, web search, code execution sandboxes, long-term memory, knowledge graphs, deployment management, and 20+ integrated AI and developer tools.28-
- AlicenseNot gradedqualityAmaintenanceEnables evidence-gated, multi-session AI coding runs with plan-build-ship state management, coordinating Claude Code and Codex native agents.20 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to orchestrate opencode worker sessions by starting tasks, tracking status, sending follow-up messages, and managing git worktrees for review, merge, or discard.MIT
- AlicenseAqualityBmaintenanceEnables Claude Code to delegate tasks to OpenCode subagents asynchronously, with tools for starting tasks, polling status, and fetching results.7630 npm6MIT
- FlicenseNot gradedqualityBmaintenanceEnables programs and AI assistants to orchestrate coding-agent sessions such as OpenCode or Claude Code and obtain structured answers backed by verifiable citations, including support for long-running jobs and follow-up questions.1-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding providers to run structured multi-agent workflows with tracked tasks, document specifications, handoffs, health gates, and server-owned evidence across providers like Claude Code, Codex CLI, Cursor, Grok Build, and OpenCode.29 npmMIT
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: run submission, run retrieval, artifacts, listing, cancellation, metrics, capabilities, usage, and plan catalog. There is no meaningful overlap between run-management tools and account/capability tools.
All tools use the same adaptorch_ prefix and snake_case, making the surface predictable. Most names are noun-oriented rather than verb_noun, but the pattern is still consistent and readable.
Nine tools is well-scoped for a control-plane MCP server, covering run operations plus account/capability metadata without feeling bloated or thin.
The core run lifecycle is covered: submit, list, get, cancel, and retrieve artifacts, along with usage, capabilities, metrics, and plan catalog. Minor gaps may exist around richer run logs/events or retry behavior, but common workflows are well supported.