MCP Goose Subagents Server
Related Servers
Alternatives to MCP Goose Subagents Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityCmaintenanceAn MCP server that enables AI clients to delegate tasks to autonomous developer teams using Goose CLI subagents, supporting parallel or sequential execution of specialized agents for different development roles.41-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that turns multiple AI coding agents into a coordinated team that chats, debates, remembers, audits security, and works in parallel on the same project.MIT
- AlicenseAqualityCmaintenanceAn MCP server that turns independent AI agents into a coordinated engineering team with shared task board, context, review loop, and enforced plan-implement-review-iterate workflow.24MIT
- AlicenseBqualityCmaintenanceAn MCP server that lets any AI tool delegate tasks to the OpenCode CLI as a subagent, with multi-session orchestration, event tracking, and task contracts.286 npm1MIT
- AlicenseNot gradedqualityFmaintenanceAn MCP server that orchestrates AI coding assistants (Claude Code CLI and Gemini CLI) to perform complex programming tasks autonomously, allowing remote control of your local development environment from anywhere.4 npm139MIT
- AlicenseAqualityBmaintenanceThis MCP server enables LLM hosts to plan large tasks and delegate subtasks to specialized local CLI agents, such as Codex and Claude Code, using tools like delegate_task and get_agent_roster.2MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: create_goose_recipe focuses on recipe creation, delegate_to_subagents handles task delegation, get_subagent_results retrieves results, and list_active_subagents monitors subagent status. There is no overlap or ambiguity between these functions.
All tool names follow a consistent verb_noun pattern with clear, descriptive actions: create_goose_recipe, delegate_to_subagents, get_subagent_results, and list_active_subagents. The naming is uniform and predictable throughout the set.
With 4 tools, the count is reasonable for managing subagents, covering creation, delegation, monitoring, and result retrieval. It is slightly lean but well-scoped, as each tool serves a distinct role without redundancy.
The tool set covers core workflows for subagent management: creation, delegation, status listing, and result fetching. Minor gaps might include updating or deleting recipes or subagents, but these are not critical for basic operations and agents can work around them.