This project provides an MCP server that reimplements Claude Code's agent teams protocol, making its advanced team orchestration capabilities accessible to any MCP client, including OpenCode and Claude Code itself. It targets developers and researchers seeking to integrate sophisticated multi-agent collaboration features into their existing coding environments without being tied to Claude Code's specific tooling, thereby enhancing productivity and enabling novel agent-based workflows.

How It Works

The server acts as a standalone MCP server, translating Claude Code's internal agent teams protocol into a format usable by various MCP clients. It leverages tmux for spawning individual agents as distinct panes or windows, each with a unique identifier and color. Communication occurs via JSON-formatted inboxes located in ~/.claude/teams/<team>/inboxes/, with a defined messaging hierarchy (lead can message anyone, teammates only the lead). Task management is handled through JSON files in ~/.claude/tasks/<team>/, supporting status tracking, ownership, and dependency management. Concurrency is managed using atomic file operations (tempfile + os.replace) and cross-platform file locking via the filelock library.

Quick Start & Requirements

• Primary install/run command: Pin to a specific release tag (e.g., @v0.1.1) using uvx. Example configurations for Claude Code and OpenCode are provided in the README.
• Non-default prerequisites:
  • Python 3.12+
  • tmux
  • At least one coding agent on PATH: claude (Claude Code) or opencode (OpenCode).
  • For OpenCode teammates: OPENCODE_SERVER_URL environment variable must be set.
• Configuration: Environment variables CLAUDE_TEAMS_BACKENDS (to explicitly enable claude and/or opencode backends) and USE_TMUX_WINDOWS (to use tmux windows instead of panes) are available.
• Links: Claude Code agent teams documentation: https://code.claude.com/docs/en/agent-teams.

Highlighted Details

• Enables Claude Code's internal agent teams protocol for external MCP clients.
• Supports flexible agent spawning via tmux panes or windows.
• Provides structured messaging and task management systems.
• Ensures data integrity through atomic writes and file locking.

Maintenance & Community

The project welcomes contributions via Pull Requests. No specific details regarding maintainers, sponsorships, or dedicated community channels (like Discord or Slack) are provided in the README.

Licensing & Compatibility

The project is licensed under the MIT license. This permissive license allows for commercial use and integration into closed-source projects without significant restrictions.

Limitations & Caveats

The project explicitly states that breaking changes occur between releases, necessitating pinning to specific tags. It relies on the presence and correct configuration of external coding agents (claude or opencode) and their respective environments. The architecture is based on reverse-engineering internal protocols, which may introduce fragility or require updates if the upstream protocols change significantly.