CLI Subagents MCP Server
Related Servers
Alternatives to CLI Subagents MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables any MCP host to delegate work to multiple coding-agent CLIs such as Codex, Claude Code, and Antigravity as subagents, preserving native sessions and supporting team-based supervision and agent-to-agent messaging.1721 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables any MCP client to launch and manage subagent sessions in installed coding agents like Codex, Claude Code, Grok, and OpenCode, using your existing logins and chosen models.21 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to spawn and manage collaboration-style external subagents with persistent sessions, queued messaging, nested delegation limits, and shared budget/concurrency controls, plus a bilingual Windows desktop control UI.1,309 npmMIT
- AlicenseBqualityBmaintenanceEnables a lead AI agent to spawn and coordinate manager agents, which can in turn run child agents across Codex/ChatGPT, Google Antigravity, Claude Code, and local OpenAI-compatible models. Provides messaging, waiting, transcripts, file exchange, and saved-conversation adoption so multi-agent workflows can be orchestrated from MCP hosts.14MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to delegate work to nested subagents running on Codex and Claude Code, keeping each task's session, turn history and results durable in SQLite while the main chat continues. Supports async or blocking waits, mid-session context updates, git worktree isolation, read-only-by-default permission inheritance, and cancelling whole subagent trees.MIT
- AlicenseAqualityBmaintenanceEnables an AI agent to delegate self-contained tasks to other agent CLIs already installed and signed in on the same machine — Claude, Codex, Gemini, or a local Ollama model — using their existing subscriptions with no API keys. Supports synchronous single-call delegation plus background tasks that can be started and polled for longer-running work.4MIT
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes: start, cancel, list, and accounts are unambiguous. However, wait, status, and result all relate to monitoring a job and could be confused—wait blocks for completion/messages, status is a snapshot, result is final output—but descriptions clarify intended usage.
All tools use the consistent subagent_ prefix with snake_case and clear action verbs. No deviations in style or convention.
8 tools is well-scoped for a subagent orchestration server, covering the full job lifecycle without redundancy. Each tool earns its place.
The surface covers starting, monitoring (wait/status/list), interacting (message), retrieving results, cancelling, and account management. A minor gap is the lack of a tool to retrieve full transcript/logs or delete jobs, but core workflows are covered.