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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.