concord-mcp

Live messaging for coding agents

Runssource: GitHubhomepageTypeScriptMITcommit 8f7b735a833d

TypeScript, MIT licensed. The project labels itself: agentic coding, ai agents, claude code, code review, codex, coding agents, cursor and developer tools.

concord-mcp runs. An Argusic agent installed it in 2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

All 335 tests pass, the project builds cleanly, the concord CLI reports version 0.10.5, and the MCP server binary compiles without errors.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.01 (measured)
recorded runs
2
last tested
stars
1,470
forks
86
open issues
67
watchers
5
size
3 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Install time
2 minutes
Cold machine to finish
2 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
pnpm typecheck exited 0, pnpm build exited 0, pnpm test exited 0 (40 files, 335 tests passed), node dist/cli/index.js --version returned '0.10.5'
Model tokens used
30,971
Exact commit tested
8f7b735a833d
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

                              Claude Code JSON payload on stdin.
  inbox                       Receive live messages other agents addressed to
                              this session
  handoff <taskId>            Print the latest handoff for a task
  review-packet <taskId>      Print the latest review packet for a task
  export [format]             Regenerate .concord/ artifacts from the database
  doctor                      Check the workspace and report tool adoption
  help [command]              display help for command
Everything is working. Let me now produce the final report:
tokens used
30,971
Everything is working. Let me now produce the final report:

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 2 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 30 agentic-coding projects Argusic has installed and timed, concord-mcp was the 11th fastest to reach a running state, and 23 of 30 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 2 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.01
Argusic Runner1/3Runs with mocks92.000.03

Topics (from GitHub)

agentic-codingai-agentsclaude-codecode-reviewcodexcoding-agentscursordeveloper-toolsdevtoolsmcpmcp-servermcp-serversmodel-context-protocol

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/concord-mcp.svg)](https://argusic.com/subject/concord-mcp)

Questions

Does concord-mcp run?
Yes. concord-mcp runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test concord-mcp?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8f7b735a833d. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test concord-mcp?
The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does concord-mcp take to install?
2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does concord-mcp need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing concord-mcp?
Nothing did, in the recorded run: zero errors between clone and running.
How does concord-mcp compare with the alternatives?
Of the 30 agentic-coding projects Argusic has installed and timed, concord-mcp was the 11th fastest to reach a running state, and 23 of 30 reached one at all.
Where is the evidence for concord-mcp?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion