MCP Agents
Enhances Claude Code's Task tool with session resumption and independent agent execution, allowing autonomous subagents from .claude/agents/ with true parallel batch support.
README
MCP Agents
MCP server that enhances the Task tool with Claude Agent SDK, providing session resumption and independent agent execution.
IMPORTANT: Replaces Task Tool
When this MCP is active, it REPLACES the native Task tool. All agents defined in .claude/agents/ must be executed through run_agent, not through Task.
Why Use This Instead of Task?
| Feature | Task Tool | run_agent (MCP) |
|---|---|---|
| Session resumption | No | Yes |
| Follow-up prompts | No | Yes |
| Independent sessions | No | Yes |
| Auto-compaction | No | Yes (SDK) |
| Summary-only returns | No | Yes |
Agent Location
Agents are loaded from the same location as Claude Code's native agents:
~/.claude/agents/ ← User-level (global)
{cwd}/.claude/agents/ ← Project-level (overrides user-level)
No duplication needed. Your existing Claude Code agents work with this MCP.
Installation
cd mcp-agents
npm install
npm run build
Configuration
Add to your .mcp.json:
{
"mcpServers": {
"mcp-agents": {
"command": "node",
"args": ["/path/to/mcp-agents/dist/index.js"]
}
}
}
No AGENTS_DIR needed - agents are loaded from .claude/agents/ automatically.
MCP Tools
run_agent
Replaces the Task tool. Run an autonomous subagent.
// New task
run_agent(agent: "researcher", task: "Research rate limiting best practices")
// Follow-up prompt (resume session)
run_agent(agent: "researcher", task: "Focus on token bucket algorithm", resume: "session-id")
Parameters:
| Name | Required | Description |
|---|---|---|
agent |
Yes | Agent name from .claude/agents/ |
task |
Yes | Task prompt (or follow-up when resuming) |
resume |
No | Session ID for follow-up prompts |
fork |
No | Create independent branch |
Returns:
{
success: boolean;
session_id: string;
summary: string;
artifacts?: string[]; // Files created/modified
error?: string; // Present on failure
}
run_agents_batch
TRUE PARALLEL execution. Runs multiple agents concurrently using Promise.all().
run_agents_batch({
tasks: [
{ id: "research", agent: "researcher", task: "Find API docs" },
{ id: "analyze", agent: "analyzer", task: "Check patterns" },
{ id: "test", agent: "tester", task: "Run tests" }
]
})
Why use this?
- Multiple
run_agentcalls execute sequentially (Claude Code limitation) run_agents_batchexecutes ALL tasks in parallel- Total time = longest task, not sum of all tasks
Returns:
{
all_success: boolean;
succeeded: number;
failed: number;
total_duration_ms: number;
results: BatchTaskResult[]; // Each with id, success, session_id, summary
}
get_agent_sessions
List resumable sessions for follow-up prompts.
cancel_agent
Cancel a running agent session.
Agent Format
Same format as Claude Code agents:
---
name: my-agent
description: |
Description of what this agent does.
Examples:
- <example>
Context: When to use
user: "Example request"
assistant: "Example response"
</example>
---
# System Prompt
Your agent instructions here...
Key Features
Session Resumption
1. run_agent(agent="coder", task="Implement auth module")
→ session_id: "abc123"
2. run_agent(agent="coder", task="Add password reset", resume="abc123")
→ Agent continues with full context
Multiple Agent Calls
Multiple run_agent calls in one message run in independent sessions. Each agent's failure doesn't affect others.
Note: Execution is currently sequential due to Claude Code's MCP handling. True parallel execution depends on client-side support (MCP spec 2025-11 added parallel tool calls).
Auto-Compaction
The Claude Agent SDK handles context management for long-running tasks.
Environment Inheritance
Agents inherit environment from Claude Code session (uses subscription, not API key).
How It Works
- MCP loads agents from
.claude/agents/on each session start - Claude already has agent descriptions in context (from same folder)
- Tool description says "use run_agent, not Task"
- When
run_agentis called, MCP uses Claude Agent SDK'squery()function - Agent runs autonomously with all Claude Code tools
- Only summary is returned (not full conversation)
- Session can be resumed with follow-up prompts
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。