Quickstart

1. Install

uv tool install coordination-memory-mcp   # or: pipx install coordination-memory-mcp
comem --help

The package is coordination-memory-mcp; the command is comem. To run without installing: uvx --from coordination-memory-mcp comem --help.

2. Run the MCP server

COORDINATION_MEMORY_DB=/absolute/path/coordination.sqlite3 comem serve

serve speaks stdio and is normally launched by an MCP client, not by hand. Pick a database path outside every worktree so collaborating agents share one store. Never commit the SQLite file.

3. Configure your MCP client

{
  "mcpServers": {
    "coordination-memory": {
      "command": "comem",
      "args": ["serve"],
      "env": { "COORDINATION_MEMORY_DB": "/absolute/path/coordination.sqlite3" }
    }
  }
}

4. Teach your agents the protocol

comem init                 # AGENTS.md + all tool adapters
comem init --tools claude  # just the Claude Code skill

This writes a canonical protocol section into AGENTS.md (idempotently) plus per-tool adapters. See Set up your agent table for what lands where.

5. Open the dashboard

comem dashboard --db /absolute/path/coordination.sqlite3

Open http://127.0.0.1:8765/. Read APIs are read-only; the only write action is Archive workspace, a local soft status update.

The dashboard starts with Human Attention before the assignment lifecycle board. Red means an active run is blocked on a person, yellow can wait for the next digest, and green is resolved and collapsed by default. Open an assignment or run to see its latest Human Resume Brief.

For agent-authored updates, use:

checkpoint_run(...)       # refresh the human Brief; does not change run status
raise_attention(...)      # yellow/green, non-blocking
request_intervention(...) # red, blocking, may include a Decision Packet

Read the projections with get_human_brief and get_attention_board. See the worked example.

Next

• Understand the model: Concepts & governance.
• See it end-to-end: Examples.
• Look up exact fields and defaults: Tool reference.