Concord MCP
Concord MCP is an MCP server published by Concord AI; its MCP spec-revision support has not been verified yet. It is the first-party server from Concord AI. Last verified 2026-09-15.
Does Concord MCP support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision Concord MCP supports (as of 2026-09-15).
Is Concord MCP a first-party (official) MCP server?
Yes. Concord MCP is the first-party MCP server published by Concord AI (last verified 2026-09-15).
How do I connect to Concord MCP?
Concord MCP is available via the package npm:@concord-ai/concord-mcp, the official MCP Registry under io.github.Get-Concord-AI/concord-mcp, the source repository at https://github.com/Get-Concord-AI/concord-mcp. Authentication: none. Transports: stdio.
What tools does Concord MCP expose?
Concord MCP exposes 5 tools, including start_work, inspect_work, update_work, transfer_work, finish_work (last verified 2026-09-15).
When were Concord MCP's facts last verified?
2026-09-15. Each fact on this page links to the sources used to verify it.
Which tools does Concord MCP expose?
5 tools verified.
start_workinspect_workupdate_worktransfer_workfinish_work
concord-mcp is a local-first communication and coordination layer for AI
coding agents: it lets agents send live messages across harnesses, detect
overlapping work before edits collide, share decisions, and hand off tasks
with evidence, through five tools (start_work, inspect_work,
update_work, transfer_work, finish_work). State is kept in a local
SQLite database under a .concord/ directory rather than a hosted service.
It runs over stdio only; installation is npm install -g @concord-ai/concord-mcp followed by a concord setup command that
registers the server into each client's own configuration file.
The publisher is Concord AI, a UK-based organization (GitHub org Get-Concord-AI, created 2026-07-14) whose own site at getconcord.ai links its "View source" control directly to this repository and instructs installing this exact npm package. That vendor-controlled surface, not merely the io.github.* namespace, is what establishes first-party authority: the org is the vendor of the product the server fronts.
No MCP specification revision is named in the README, per-client integration docs, or package metadata; the @modelcontextprotocol/sdk ^1.30.0 dependency is a version range rather than a stated revision, so spec_status is unknown. The repository has published no security advisories. It is a young project - the org and repository were both created 2026-07-14 - but shows an active release cadence of seventeen tags through v0.10.4 (2026-09-05).
How widely adopted is Concord MCP?
Ranked #223 in The MCP 500 with Adoption Index 50.37 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 335 | API · |
| GitHub stars | 325 | API · |
| GitHub forks | 14 | API · |
| Last push | 2026-09-11T12:25:26Z | API · |
| Repository archived | no | API · |
How was this verified, and what are the sources?
Verified · method: vendor-docs
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.Get-Concord-AI/concord-mcp, re-fetched 2026-09-15 via search - version 0.10.4, package npm @concord-ai/concord-mcp with stdio transport, websiteUrl https://getconcord.ai, status active - accessed
- GitHub organization Get-Concord-AI, fetched 2026-09-15 - type Organization, name "Concord AI", description "Give your agents a workspace", blog https://getconcord.ai, created 2026-07-14 - accessed
- Vendor site getconcord.ai, fetched 2026-09-15 - "View source" link points to https://github.com/Get-Concord-AI/concord-mcp; instructs "npm install -g @concord-ai/concord-mcp"; star count on the page (325) matches the repository's stargazers_count exactly - accessed
- Repository README, fetched 2026-09-15 - "The open-source, local-first communication and coordination layer for AI coding agents"; documents five tools (start_work, inspect_work, update_work, transfer_work, finish_work) and a local SQLite store under .concord/ - accessed
- npm registry metadata for @concord-ai/concord-mcp, fetched 2026-09-15 - dist-tags.latest 0.10.4, dependency @modelcontextprotocol/sdk ^1.30.0, sole maintainer "alexechoi" - accessed
- Repository metadata, fetched 2026-09-15 - Get-Concord-AI/concord-mcp, MIT, 325 stars, 14 forks, last push 2026-09-11, not archived, homepage https://getconcord.ai; owner is a GitHub Organization - accessed