ama-mcp
An MCP server that coordinates multiple Claude Code sessions through kitty terminal remote control to enable a manager-worker delegation workflow. It supports task dependency tracking, inter-agent communication, and automated status monitoring across multiple terminal windows.
README
ama-mcp
MCP server that coordinates multiple Claude Code sessions through a shared state file and kitty terminal notifications.
Agents register at startup. A manager delegates tasks, workers receive them via MCP tools, and kitty sends a nudge ("doorbell") so agents know to check. All message content flows through the state file — kitty never carries the actual message, just the notification.
Requirements
- kitty terminal with
allow_remote_control socket-onlyandlisten_onconfigured - Claude Code CLI
- Node.js 18+
kitty config
# ~/.config/kitty/kitty.conf
allow_remote_control socket-only
listen_on unix:/tmp/kitty-sock-{kitty_pid}
Setup
npm install
Add to your Claude Code MCP config (~/.claude/settings.json):
{
"mcpServers": {
"agent-manager": {
"command": "node",
"args": ["/path/to/ama-mcp/index.mjs"]
}
}
}
Tools
All agents
| Tool | Description |
|---|---|
register(manager?, session_id?, name?) |
Register this agent. All agents call at session start. |
chat(message, to?) |
Send a message + kick recipient. Omit to for manager. |
wait_for_task(timeout?) |
Block until a task or message arrives. |
my_task() |
Show own task and read unread messages. |
task_done(agent?) |
Mark own task done, or another's (manager only). |
task_list() |
List active tasks and registered agents. |
Manager-only
| Tool | Description |
|---|---|
delegate(agent, description, message, after?, friendly_name?) |
Assign a tracked task + kick agent. |
name_agent(agent, friendly_name) |
Set a friendly name for an agent (e.g. "sims guy"). |
spawn(cwd?, win?) |
Launch a fresh claude agent in a new kitty tab. |
respawn(agent, win?) |
Resume a dead agent session in an idle kitty tab. |
unregister_manager(to?) |
Step down or hand off manager role. |
task_check(win) |
Read agent's kitty terminal (escape hatch). |
How it works
- Open several kitty windows, each running
claude. - Every agent calls
register()at startup. - One agent calls
register(manager=true)— becomes the manager, starts keepalive watcher. - Manager uses
delegate()to assign tasks — state file records the task, kitty kicks the agent. - Agent sees the kick, calls
wait_for_task()ormy_task()to get the task. - Agent works, uses
chat()to report back (kicks the manager). - Agent finishes, calls
task_done().
Task dependencies
delegate(agent=3, description="analyze results", message="...", after="w5-m1abc")
Task stays blocked until w5-m1abc is done, then activates and kicks the agent.
Notifications (📬)
Every kick sends ESC + 📬 + Enter to the agent's kitty window. The ESC interrupts blocking calls (wait_for_task). The 📬 appears as user input — when the agent sees it, it calls my_task() to read actual messages from the state file. No message content ever goes through the terminal.
Keepalive watcher
Background process (auto-started by register(manager=true)) polls every 45 seconds and kicks the manager when agents need attention. 5-minute cooldown between kicks.
State
Task and message state persists in ~/.claude/agent-tasks.json. Survives context compaction and session restarts. Agent registry tracks who's online and where to kick them.
Configuration
Add this to your CLAUDE.md (global or per-project) so every agent knows how to participate:
## Agent Manager
All sessions have the `agent-manager` MCP server. Call `register()` at session start. If you see **📬** as input, call `my_task()` — it means you have a new task or message.
If you're delegated a task but you're mid-work on something unrelated, push back via `chat()` — the manager can reassign.
Manager reference (optional)
managing-agents.md has detailed guidance for the manager session — tool usage, behavioral guidelines, intervention patterns. Symlink it and reference from your CLAUDE.md:
ln -s /path/to/ama-mcp/managing-agents.md ~/.claude/reference/managing-agents.md
- **managing-agents.md** — meta sessions, inter-agent communication, agent-manager MCP tools
Provenance
This was written almost entirely by Claude (Opus), with human direction on design and behavior. The code, docs, and commit messages are AI-generated. The human has not read the code.
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.