AgentNave
Related Servers
Alternatives to AgentNave
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.1713 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables Cursor's main agent to delegate development tasks to Claude CLI subagents via MCP, supporting synchronous, asynchronous, and parallel task execution with monitoring and control.7ISC
- AlicenseAqualityAmaintenanceEnables orchestrator agents to route coding tasks to native CLI worker agents via MCP, providing tools for agent discovery, task submission, waiting, inspection, and cancellation.53MIT
- FlicenseNot gradedqualityCmaintenanceEnables ISLI agents and MCP clients to dispatch natural-language coding and terminal tasks to a locally-installed Claude Code CLI, supporting both one-shot execution and persistent sessions with workspace and security controls.-
- AlicenseNot gradedqualityAmaintenanceEnables 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.10 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to spawn and control Codex CLI and Claude Code sessions on the host machine, with session management and filesystem access.4MIT
TDQS
Scored across 9 tools
The tools mostly target distinct orchestration objects and actions: start_agent for CLI tasks, run_round for meetings, decide_answers for held answers, and handover for workspace transfer. Some overlap exists among list, list_members, and read_conversation, and wait spans multiple handle types, but the descriptions provide enough differentiation.
Most compound names follow imperative snake_case verb_noun patterns such as start_agent, list_members, run_round, decide_answers, and read_conversation. However, bare verbs wait/cancel/list and the noun-style handover break the predictable pattern, making it mixed but still readable.
The server exposes 9 tools, which is well within a reasonable range for an orchestration service. Each tool appears to earn its place by covering a distinct lifecycle or control operation, with no obvious redundant tools.
The surface covers task start/wait/cancel/list/read, meeting round creation/continuation, answer decisions, member inspection, and handover. Minor gaps exist, such as no explicit member configuration/update tool and no messaging to active tasks, but some of these appear intentionally out of scope.