Swarm Protocol

🐝 Swarm Protocol

[](https://github.com/phuryn/swarm-protocol/actions/workflows/test.yml) [](https://github.com/phuryn/swarm-protocol/blob/main/LICENSE) [](https://github.com/phuryn/swarm-protocol/blob/main/CONTRIBUTING.md)

**Coordination protocol for agent-first teams. No UI. No sprints. No Jira. Just state sync.**

**Status: Alpha — building in public. [19 MCP tools](#all-19-tools) implemented, integration tests passing.**

The Coordination Loop

Drop [`COORDINATION.md`](claude-md/COORDINATION.md) into your repo's `CLAUDE.md` and agents coordinate automatically:

Agent starts session
  → get_team_status        "What's in flight?"
  → claim_work             "I'm taking this — here are my files"
  → check_conflicts        "Anyone else touching src/api/router.ts?"
  → heartbeat              "Still working" (every 10-15 min)
  → complete_claim          "Done — this unblocks intent_xyz"
                              ↳ intent_xyz status: blocked → open
                              ↳ Next agent picks it up automatically

Zero Slack messages. Zero status meetings. Agents coordinate through shared state.

What This Is

A headless coordination layer exposed as an MCP server — the same protocol Claude Code already speaks. No REST API. No dashboard. Agents query it to see what's in flight, claim work, detect file conflicts, and hand off unblocked tasks.

This is a **coordination protocol, not a project management tool.** Jira was built for humans clicking buttons. This is state synchronization infrastructure for teams where agents are the primary development interface.

The CLAUDE.md integration pattern is as important as the server itself. Agents coordinate automatically without humans configuring anything.