claude-teams
Click on "Install 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., "@claude-teamsCreate a team and spawn two agents to optimize database queries."
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.
claude-teams
MCP server that implements Claude Code's agent teams protocol for any MCP client.
https://github.com/user-attachments/assets/531ada0a-6c36-45cd-8144-a092bb9f9a19
Claude Code has a built-in agent teams feature (shared task lists, inter-agent messaging, tmux-based spawning), but the protocol is internal and tightly coupled to its own tooling. This MCP server reimplements that protocol as a standalone MCP server, making it available to any MCP client: Claude Code, OpenCode, or anything else that speaks MCP. Based on a deep dive into Claude Code's internals. PRs welcome.
Install
Pin to a release tag (e.g.
@v0.1.1), notmain. There are breaking changes between releases.
Claude Code (.mcp.json):
{
"mcpServers": {
"claude-teams": {
"command": "uvx",
"args": ["--from", "git+https://github.com/cs50victor/claude-code-teams-mcp@v0.1.1", "claude-teams"]
}
}
}OpenCode (~/.config/opencode/opencode.json):
{
"mcp": {
"claude-teams": {
"type": "local",
"command": ["uvx", "--from", "git+https://github.com/cs50victor/claude-code-teams-mcp@v0.1.1", "claude-teams"],
"enabled": true
}
}
}Requirements
Python 3.12+
At least one coding agent on PATH: Claude Code (
claude) or OpenCode (opencode)OpenCode teammates require
OPENCODE_SERVER_URLand theclaude-teamsMCP connected in that instance
Configuration
Variable | Description | Default |
| Comma-separated enabled backends ( | Auto-detect from connecting client |
| OpenCode HTTP API URL (required for opencode teammates) | (unset) |
| Spawn teammates in tmux windows instead of panes | (unset) |
Without CLAUDE_TEAMS_BACKENDS, the server auto-detects the connecting client and enables only its backend. Set it explicitly to enable multiple backends:
{
"mcpServers": {
"claude-teams": {
"command": "uvx",
"args": ["--from", "git+https://github.com/cs50victor/claude-code-teams-mcp@v0.1.1", "claude-teams"],
"env": {
"CLAUDE_TEAMS_BACKENDS": "claude,opencode",
"OPENCODE_SERVER_URL": "http://localhost:4096"
}
}
}
}Tools
Tool | Description |
| Create a new agent team (one per session) |
| Delete team and all data (fails if teammates active) |
| Spawn a teammate in tmux |
| Send DMs, broadcasts (lead only), shutdown/plan responses |
| Read messages from an agent's inbox |
| Read team config and member list |
| Create a task (auto-incrementing ID) |
| Update task status, owner, dependencies, or metadata |
| List all tasks |
| Get full task details |
| Kill a teammate's tmux pane/window and clean up |
| Remove teammate after graceful shutdown |
Architecture
Spawning: Teammates launch in tmux panes (default) or windows (
USE_TMUX_WINDOWS). Each gets a unique agent ID and color.Messaging: JSON inboxes at
~/.claude/teams/<team>/inboxes/. Lead messages anyone; teammates message only lead.Tasks: JSON files at
~/.claude/tasks/<team>/. Status tracking, ownership, and dependency management.Concurrency: Atomic writes via
tempfile+os.replace. Cross-platform file locks viafilelock.
~/.claude/
├── teams/<team>/
│ ├── config.json
│ └── inboxes/
│ ├── team-lead.json
│ ├── worker-1.json
│ └── .lock
└── tasks/<team>/
├── 1.json
├── 2.json
└── .lockLicense
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cs50victor/claude-code-teams-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server