Concord Mcp

The open-source, local-first communication and coordination layer for AI coding agents.

share decisions, and hand off tasks with evidence - through one MCP server.

app, transfer ownership, and hand the result to an independent reviewer.

Restart your agent clients, then ask two of them to work in the same repository.

concord setup creates the local .concord/ workspace, registers the MCP server

Concord's tool instructions into your client configs ( CLAUDE.md , AGENTS.md ,

.codex/ , .cursor/rules/ ). It merges into existing config rather than replacing

--require-adapters in managed installs that should fail on degraded support.

There is no universal /concord slash command — commands are client-specific.

Live delivery depends on the receiving harness and session state. Run

Messaging gets agents talking. Concord's shared work-state keeps the resulting

Concord is not another autonomous agent or orchestrator. It is the shared layer

Writes accept an agent_id , which keeps presence live just by working.

client sessions once. A prompt uses update_work with operation: "prompt" , the

a busy turn or starts an idle turn. Hook-only integrations leave a durable pull

message and state that limitation in the result. Delivery fails immediately

probe result. concord adapters install , doctor , and uninstall provide the