Task Agents
This MCP server enables AI assistants to delegate specialized tasks to autonomous sub-agents defined in markdown files, bringing Claude Code-style workflows to any MCP-compatible tool.
Core Capabilities:
Agent delegation - Offload complex, multi-step, or specialized tasks (code reviews, test writing, security checks, refactoring) to autonomous agents using the
run_agentfunctionReusable agent definitions - Create custom agents as simple markdown files that are portable and reusable across projects and teams
Cross-tool compatibility - Use the same agent definitions in any MCP-compatible tool (Cursor, Claude Desktop, Windsurf, etc.)
Engine flexibility - Execute agents through
cursor-agentorclaudeCLI backends via theAGENT_TYPEenvironment variableContext isolation - Each agent runs with fresh, independent context to prevent interference between tasks
Session management - Optional persistent sessions (
SESSION_ENABLED) allow agents to maintain context and build upon previous executions for iterative workflowsExecution control - Configure working directories (
cwd), timeouts, and shell command permissions through allowlistsBatch operations - Handle systematic codebase analysis, fix multiple test failures, or perform refactoring across multiple files
Team collaboration - Share standardized agent definitions across teams regardless of IDE preferences
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Task Agents review this Python function for bugs and improvements"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Sub-Agents MCP Server
Run reusable coding agents from any MCP-compatible client.
Write a reviewer, test writer, or investigator in Markdown, then ask your assistant to use it. The MCP server runs that agent with the coding CLI you choose and returns the result to the same conversation.
What You Can Do
Delegate code review, test writing, investigation, and documentation to focused agents
Reuse the same agent definitions across MCP clients with one shared backend and model configuration
Continue the same agent across multiple calls for longer work
Related MCP server: Roundtable AI MCP Server
Quick Start
You need Node.js 22 or later, an MCP-compatible client, and one supported coding CLI installed and signed in. This example uses Codex.
1. Create an Agent
Create an agents folder anywhere on your machine, then add code-reviewer.md:
# Code Reviewer
Review code for bugs and maintainability issues.
## Task
- Find concrete problems in the requested changes
- Explain why each problem matters
- Point to the affected code
## Done When
- All requested files have been reviewed
- Findings include evidence and suggested next stepsThe filename becomes the agent name: code-reviewer.md becomes code-reviewer.
2. Add the MCP Server
Add the server to your client's MCP configuration. Replace AGENTS_DIR with the absolute path to the folder you created.
{
"mcpServers": {
"sub-agents": {
"command": "npx",
"args": ["-y", "sub-agents-mcp"],
"env": {
"AGENTS_DIR": "/absolute/path/to/agents",
"AGENT_TYPE": "codex"
}
}
}
}Restart or reconnect your MCP client after saving the configuration.
3. Run the Agent
Ask your assistant:
Use the code-reviewer agent to review the authentication changes.Your assistant runs the agent with Codex and returns the review to the conversation.
Examples
Use the test-writer agent to add unit tests for the auth module.Use the bug-investigator agent to find the cause of the failed checkout requests.Use the doc-writer agent to document the public API changes.Name both the agent and the work you want it to do.
When the MCP Server Fits
Use the MCP server when you want to share the same agents across MCP clients while keeping backend and model configuration in one place.
If you prefer a lighter installation or want each agent to choose its own backend and model, see Sub-Agents Skills.
Supported Backends
Set AGENT_TYPE to the backend you already use:
| Backend | Command |
| Codex |
|
| Claude Code |
|
| Cursor CLI |
|
| Command Code |
|
| GLM (Z.ai) |
|
| Kimi |
|
| Grok Build |
|
| Google Antigravity |
|
| Gemini CLI (compatibility) |
|
| OpenCode |
|
| MiniMax Code |
|
| Pi |
|
The selected CLI must be installed and configured before the MCP server starts.
GLM and Kimi require CLI_API_KEY in the MCP server environment. Other backends use the CLI's existing authentication.
For Google models, prefer Antigravity. Gemini CLI remains available for existing enterprise, API key, or Vertex AI configurations.
Shared Agent Settings
Set AGENT_MODEL to use one model for every agent. Omit it to use the backend's default.
AGENT_PERMISSION controls what agents may do:
read-only— review and investigationsafe-edit— edits allowed without approval (default)yolo— unrestricted execution
If an agent reports that an action was blocked, choose a less restrictive mode.
How strictly each level is enforced depends on the backend, so treat it as guidance rather than a security boundary.
Continue Work Across Calls
Set SESSION_ENABLED to "true" when you want an agent to remember earlier calls and continue a longer task. Your assistant must reuse the returned session_id on the next call to continue that session.
If It Does Not Start
Run the selected backend command directly and confirm that it is installed and signed in
Make sure
AGENTS_DIRis an absolute path and contains at least one.mdor.txtfileRestart or reconnect the MCP client after changing its configuration
License
MIT
Available Tools
1 toolrun_agentA
Delegate complex, multi-step, or specialized tasks to an autonomous agent for independent execution with dedicated context (e.g., refactoring across multiple files, fixing all test failures, systematic codebase analysis, batch operations). Returns session_id in response metadata - reuse it in subsequent calls to maintain conversation context continuity across multiple agent executions.
Inputs: cwd (required), agent (required), prompt (required), session_id.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or misselection between tools. The tool's purpose is clearly described and stands alone.
The single tool name 'run_agent' is clear and follows a conventional verb_noun style. There are no other names to contradict a consistent pattern.
A single tool for a server called 'Task Agents' is too few for the apparent scope. Users cannot list, manage, or monitor agents, making the toolset feel extremely thin.
The server provides only an invocation operation with no lifecycle management—no status checks, cancellation, listing, or result retrieval mechanisms. This is severely incomplete for a task-agent-oriented server.
Maintenance
Related MCP Connectors
Multiplayer for the coding agents your team already uses: shared tasks, decisions, skills and tools.
Discover available AI models and delegate analysis or code review from your existing agent.
Let your AI agents hand work to each other, share files, and use apps you approve.
Command center for developers coordinating AI coding agents across projects.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables a primary AI coding assistant to delegate tasks in parallel to specialized sub-agents such as Gemini, Claude, Codex, and Cursor, sharing project context and synthesizing their outputs into a single response from within the IDE. It runs entirely on existing local CLI tools and subscriptions with no added cost or markup.-
- FlicenseNot gradedqualityAmaintenanceEnables a primary AI coding assistant to delegate tasks to specialized local CLI agents such as Gemini, Claude, Codex, and Cursor, coordinating shared context, parallel execution, and synthesized responses from within an IDE.-
- FlicenseNot gradedqualityAmaintenanceEnables a primary AI assistant to delegate tasks in parallel to specialized AI sub-agents like Gemini, Claude, Codex, and Cursor from a single prompt, sharing project context and synthesizing their responses into one answer.-
- FlicenseNot gradedqualityAmaintenanceEnables a primary AI assistant in an IDE to delegate tasks to specialized CLI-based sub-agents such as Gemini, Claude, Codex, and Cursor, with shared context, parallel execution, and synthesized responses.-