Local-first MCP coordination

SCRUM MCP turns multi-agent chaos into a dependable dev team.

SCRUM (Synchronised Claims Registry for Unified Multi-agents) is the coordination layer that keeps every agent honest and in sync. Declare intent, claim files, attach evidence, and stream realtime signals without phoning home.

Download v0.5.2 Get started Read docs

Works with Claude Code, Cursor, Continue, Gemini CLI, OpenCode, Antigravity MIT licensed | Local-first

5 Core signals

0 Phone home

1 Shared reality

New in v0.5.2

~50% fewer tokens per task.

Convenience tools combine common workflows into single calls. What used to take 10+ tool calls now takes 3.

scrum_context() Session startup in ONE call. Returns status, tasks, claims, board.

scrum_start_work() Begin work in ONE call. Does overlap → intent → claim.

scrum_finish_work() Complete work in ONE call. Does evidence → compliance → release.

Also new: Pre-commit hooks · Profile auto-detection (solo/team/full) · Orchestration tools · Sprint collaboration · Unified blocker/dependency/metrics tools · Compliance verification

Start here

From zero to coordinated in under 3 minutes.

Install SCRUM locally, point your agents at the MCP server, and watch intent, claims, and receipts appear in one shared lobby.

Clone the repo Download ZIP v0.5.2

Node 20+ required Runs on 127.0.0.1 by default

Install and run

npm install
npm run dev

Build MCP server

npm run build
npm run mcp

Connect your tool

Add SCRUM MCP to Claude Code, Cursor, or Continue in minutes.

IDE setup guide

Local endpoints

API: http://localhost:4177/api

WebSocket: ws://localhost:4177/ws

Dashboard: http://localhost:5174

Dashboard requires cd frontend && npm install && npm run dev

Quick CLI

npm run build
npm run cli -- status
npm run cli -- task create --title "First task"

The coordination surface

Every agent gets the same truth, in realtime.

SCRUM MCP is not another dashboard. It is the protocol level source of truth that keeps intent, ownership, and evidence from drifting apart.

Intent & Claims

Declare what you plan to change, then lock files while editing. No more surprise merges or conflicting changes.

Sprint Collaboration

Multiple agents working on the same task share context in real-time. Decisions, interfaces, questions—all coordinated.

Compliance Verification

Verify agents did what they declared. Block releases on undeclared files or boundary violations.

Evidence Receipts

Attach command output as proof. If it is not evidenced, it did not happen. Full audit trail.

Kanban & Metrics

Full board with dependencies, WIP limits, blockers. Track cycle time, velocity, and aging work.

Local-first Trust

SCRUM never phones home. Runs where your repo lives. Never edits without consent. MIT licensed.

MCP built in

Plug SCRUM into any MCP client in minutes.

SCRUM exposes its coordination layer as MCP tools so Claude Code, Cursor, Continue, and any MCP client can share intent and receipts instantly.

35 MCP tools: consolidated + token-optimized convenience tools
Profile discovery: solo (15), team (24), full (35) tools
Sprint collaboration, compliance verification, Kanban, metrics

MCP docs Browse repo

MCP config

npm install
npm run build
npm run mcp

# MCP config example
{
  "mcpServers": {
    "scrum": {
      "command": "node",
      "args": ["/absolute/path/to/scrum/dist/mcp.js"],
      "env": { "SCRUM_DB_PATH": "/path/to/.scrum/scrum.sqlite" }
    }
  }
}

A tighter loop

From intent to evidence in a single flow.

SCRUM enforces a workflow that prevents silent failures and forces clarity across every agent.

Post intent

Declare scope and acceptance criteria before edits begin.

Claim files

Hold short-lived ownership while you work.

Attach evidence

Capture command output and receipts for every change.

Release clean

Unlock claims only after evidence is attached.

Enforce at commit

Git hooks block non-compliant commits.

Pre-commit hooks validate SCRUM compliance before every commit. If you didn't declare intent, didn't claim files, or violated boundaries—the commit is blocked.

Blocks commits with undeclared files
Blocks boundary violations (DO NOT TOUCH files)
Warns if no evidence attached (strict mode blocks)
Graceful fallback when server not running

Hook docs

Install hooks

# Install the pre-commit hook
./scripts/install-hooks.sh

# Set your task context
export SCRUM_TASK_ID="task-abc123"
export SCRUM_AGENT_ID="claude-code-xyz"

# Commit as normal - hook validates compliance
git add src/feature.ts
git commit -m "Add feature"
# ✅ SCRUM compliance passed (score: 100/100)

# Or if you forgot to declare files...
# ❌ COMPLIANCE FAILED: Undeclared files modified

Ops ready

Every change leaves a trail.

Operations should not guess what happened at 3AM. SCRUM keeps a live ledger of tasks, intents, claims, and evidence.

Detect

Check /api/status and the event stream for drift.

Recover

Roll back by restoring the last known good build.

Audit

Inspect evidence receipts before you merge.

No surprises policy

SCRUM never auto-edits your repo, never phones home, and logs what it is doing and why. Anything destructive is behind an explicit command.

Security posture

Ship with evidence

Bring your agents into one shared room.

SCRUM MCP keeps the lights on for every agent, every task, every deploy. It is the coordination layer your team assumes already exists.

Download v0.5.2 GitHub repo