Concord MCP server

by Get-Concord-AI·io.github.Get-Concord-AI/concord-mcp·v0.10.4

No reviews yet

Cross-harness communication and shared work-state for AI coding agents.

A91/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A91/100

full report

Adoption

Established

323 stars89 downloads/wk

Reviews

Write one

Nobody has reviewed Concord MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Concord MCP tools (5, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

finish_work
Record completion evidence and atomically leave the task active as a handoff, mark it
inspect_work
Read the workspace, one task, one agent communication inbox/outbox, or one durable
start_work
Enter one task before editing: register or refresh this agent, accept addressed work
transfer_workwrite action
Apply one versioned ownership action: assign, accept, decline, release, reassign,
update_workwrite action
Record task context or deliver a live prompt/reply to another promptable workspace agent.

Public scan report

scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it

no findings

Code scan186 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 2 days ago15/15
Maintainer identityregistry namespace matches repository owner7/10

Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

What the publisher says

From the Concord MCP repository's README, as published. We do not edit it. Read it on GitHub

Concord MCP

Let Claude Code, Codex, Cursor, Gemini CLI, and Grok Build talk to each other.

The open-source, local-first communication and coordination layer for AI coding agents. Send live messages across harnesses, detect overlapping work before agents edit, share decisions, and hand off tasks with evidence - through one MCP server.

Demo · Quick start · Supported agents · Website · Contributing

See it work

Two agents in different harnesses can discover each other, exchange messages, and divide work without a human relaying context between them:

Claude Code → Concord   Claim src/app/page.tsx
Codex       → Concord   Claim src/app/page.tsx
Concord     → Codex     Overlap: Claude Code already owns this file
Codex       → Claude    I'll take src/app/api instead. Does that work?
Claude      → Codex     Yes. I'll keep the page and use your API contract.

Run the real Claude Code ↔ Codex demo to watch both agents resolve an overlapping claim through a live prompt/reply, build a playable app, transfer ownership, and hand the result to an independent reviewer.

Quick start

npm install -g @concord-ai/concord-mcp
cd /path/to/your/repository
concord setup

Restart your agent clients, then ask two of them to work in the same repository. Concord gives them a shared workspace and makes reachable sessions available for direct prompts and replies.

What concord setup changes

concord setup creates the local .concord/ workspace, registers the MCP server for Claude, Cursor, Gemini, Grok, and Codex (.mcp.json, .cursor/mcp.json, .gemini/settings.json, .grok/config.toml, and ~/.codex/config.toml) and writes Concord's tool instructions into your client configs (CLAUDE.md, AGENTS.md, .codex/, .cursor/rules/). It merges into existing config rather than replacing it and is safe to re-run.

Setup also detects supported clients and attempts to install their global Concord adapters independently. Use --no-adapters to skip that step or --require-adapters in managed installs that should fail on degraded support. Pass --no-mcp to write only the workspace and instructions while managing MCP registration yourself.

Supported agents

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

Runs npx -y @concord-ai/concord-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add concord-mcp -- npx -y @concord-ai/concord-mcp

Add to Cursor

Concord MCP: common questions

Is Concord MCP server safe?: Yes, by our scan: it is graded A (91/100). Read the Concord MCP safety report
How do I install Concord MCP?: It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does Concord MCP need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Concord MCP maintained?: The last commit was 2 days ago (2026-09-18). The latest release is v0.10.4.
What can I use instead of Concord MCP?: Servers from other publishers that do the same job: Claudexor MCP server.

Alternatives to Concord MCP

Same job from other publishers: the closest match first, then the best rated.

Claudexor
Route coding work across Claude Code, Codex, Cursor, and OpenCode with shared context.
not reviewed
Established
A