Get-Concord-AI/concord-mcp

View on GitHub ↗

"Google Workspace" for your AI Agents

234 ★9 forksTypeScriptUpdated 21d ago

What you need to know

Google Workspace for your AI agents — a shared, local-first workspace where coding agents (Claude Code, Codex, Cursor, etc.) coordinate work, preserve decisions and hand off cleanly, backed by an SQLite store at the repo root.

Install

npm install -g @concord-ai/concord-mcp
cd /path/to/your/repository && concord setup   # creates ./.concord/, registers MCP and writes instructions

Usage

  • Agents use start_work, inspect_work, update_work, transfer_work and finish_work for presence, task memory and handoffs
  • Humans/CLI agents use the same workspace via concord status, dashboard, who, tasks, handoff, review-packet
  • Run concord setup --agent-comms for live agent-to-agent prompt/reply over update_work

Key features

  • Live roster, task memory and versioned ownership with explicit accept/decline handoffs
  • Evidence-rich review packets and durable prompt/reply threads with idempotency keys
  • SQLite source of truth shared across sessions, Git worktrees and multiple agents in one repo
  • Local TUI dashboard (concord dashboard) for live agent/task monitoring

Best for

Teams running several coding agents on the same checkout who need shared coordination, ownership and review state rather than chat-history archaeology.

Caveats

  • Early stage and under active development — public surface is five workflow tools
  • Not an orchestrator, reviewer, hosted sync or autonomous agent; no universal /concord slash command
  • Sends anonymous product-usage metadata (disable with CONCORD_TELEMETRY_DISABLED=1)
Platforms: macOS · Linux · WindowsClients: Claude Code · Codex · Cursor · MCP clients

Reviewed 2026-08-11

Topics

agentic-codingai-agentsclaude-codecode-reviewcodexcoding-agentscursordeveloper-toolsdevtoolsmcpmodel-context-protocol
Stars
234★
Forks
9
Language
TypeScript
License
MIT
Created
2026-07-14
Last push
2026-08-14