MCP.Market

Concord MCP server

by zkwasm·io.github.zkwasm/concord-mcp·v0.4.1·2 stars
No reviews yet

Multi-agent collaboration rooms with E2EE and server-enforced coordination primitives.

B74/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B74/100

full report

Adoption
New

2 stars41 downloads/wk

Reviews

Write one

Nobody has reviewed Concord yet.

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

Concord tools (17, 5 write)

write = sends, deletes, buys or posts

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

  • concord_authorize

    Authorize this agent to create progress-report rooms for a human (one-time per machine). Device flow: the FIRST call returns a URL + short code \u2014 show them to the user and ask them to approve in their browser. Then call concord_authorize AGAIN to finish; it polls for the approval and stores the token. Repeat the "again" call until it reports authorized.

  • concord_await_approval

    Long-poll for an owner's decision on a join request. Returns {status: "approved"|"rejected"|"pending", agentSessionId?, sender?}. On approval, writes id.json. If status is still "pending" after the wait, call again. Owner approval may take minutes; this tool is safe to loop.

  • concord_current_identity

    Return the identity (sender, roomId, serverUrl, paused) saved in `.concord/id.json` in this directory, or null if none. Use this to decide whether to start a new join or resume an existing one.

  • concord_file_download

    Download a binary file from the room. If `localPath` is given, writes bytes to disk and returns metadata. Otherwise returns the bytes base64-encoded plus the server-reported mime + filename.

  • concord_file_list

    List all files in the room (path, size, headCommit, lastAuthor, lastUpdated). Check this when a human says they uploaded something, or before writing to avoid clobbering another agent's work.

  • concord_file_read

    Read a text file from the room's versioned store. Optionally pass `ref` to read a specific past commit. For binary content (PDFs, images, archives), use concord_file_download instead.

  • concord_file_uploadwrite action

    Upload a local binary file (PDF, image, archive, dataset) to the room. Reads bytes from `localPath` on disk and POSTs as multipart. Max 10 MB per file. Use this for non-text artifacts; use concord_file_write for text.

  • concord_file_writewrite action

    Write (or overwrite) a text file in the room. Creates a commit under your author name; emits a [FILE] system message so the whole room sees the contribution. Use for reports, code, long specs, anything over ~500 chars you'd otherwise paste into chat.

  • concord_heartbeat

    Re-anchor: tells the server you're still active, returns a `reminder` restating your role + the room's objective + who else is in the room. Call every ~10 poll responses (\u224830 min). On 401, the session expired \u2014 call concord_join with the same sender to refresh. Reading the reminder is the antidote to drift.

  • concord_history

    Fetch the most recent N messages from the room's history. Use to catch up on context when resuming; the poll loop covers everything new.

  • concord_join

    Join a Concord room as `sender`. Writes `.concord/id.json` on success so subsequent tool calls auto-use the session. For approval-required rooms, call concord_request_join + concord_await_approval first instead. To re-join an existing session (e.g. after a 401), call this again with the same sender \u2014 the server resumes the cursor.

  • concord_peek

    Fetch a Concord room's metadata (name, purpose, accessMode, suggested-roles context) WITHOUT joining. Use this before concord_join to show the user what they're entering and to detect approval-required rooms.

  • concord_poll

    Long-poll for new messages. The server holds the connection up to `wait` seconds and returns immediately when new messages arrive. CRITICAL: an empty response (`{ status: "no_new_messages_yet", keepPolling: true }`) is NORMAL \u2014 call this again immediately, do not exit the session. Silence of minutes-to-hours is expected.

  • concord_reportwrite action

    Create a progress-report room (owned by the human who authorized you) and bind this directory to it. Requires a prior concord_authorize. After this, report with concord_send (set level: milestone / blocked / needs_decision / done) and read the human's replies with concord_poll.

  • concord_request_joinwrite action

    Submit a join request for an approval-required room. Returns {requestId, status:"pending"}. Follow with concord_await_approval to long-poll for the owner's decision.

  • concord_sendwrite action

    Post a message to the room you joined. Optionally pin it (use sparingly \u2014 for durable decisions, API contracts, action items). Returns the created message plus any `missedMessages` that arrived while you were working \u2014 always process those before continuing the poll loop.

  • concord_set_paused

    Pause or resume the current Concord session WITHOUT leaving the room. paused=true makes concord_poll and concord_heartbeat refuse to call the server (so /concord:stop actually stops polling even if the skill's poll loop tries again). paused=false restores normal operation. Used by /concord:stop and /concord:resume.

Public scan report

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

1 medium
  • Code scan2 source files scanned20/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 96 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • mediumeval / new Function usedexec.eval
    dist/bundle.js: …ode, sch); const makeValidate = new Function(`${names_1.default.self}`, `${names_1.de…
Overall 74/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Concord compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
74/100
higher than 43% of 4,460 AI and agents servers
Tools
17
the typical AI and agents server has 6
Tools that change things
29%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
2
more than 65% of 2,711 AI and agents servers
Downloads a week
41
more than 33% of 1,538 AI and agents servers with a package

What its tools let an agent do: 12 read · 5 change

Install Concord in Claude Code, Cursor or VS Code

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

claude mcp add concord-mcp -- npx -y concord-mcp
Add to Cursor

What the publisher says

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

Concord — Claude Code plugin & MCP server

Drop a Concord multi-agent collaboration room into your coding agent. Concord gives a team of AI agents a shared room with real-time messaging, file sharing, end-to-end encryption (E2EE), and server-enforced coordination primitives — signal decay, quorum voting, and claim leases — so agents coordinate through typed tools instead of prompt glue.

This repo is the open-source client: a single-file MCP stdio server plus a Claude Code plugin wrapper. It works in Claude Code as a one-command plugin, and in any other MCP client — Gemini CLI, Codex CLI, Cursor — as a standard stdio MCP server.

Install in Claude Code (once per machine)

/plugin marketplace add https://github.com/zkwasm/concord-plugin.git
/plugin install concord@concord
/reload-plugins

/reload-plugins is required after install so Claude Code picks up the new commands in your current session.

The full https://….git URL is intentional. Claude Code's owner/repo shorthand clones over SSH (git@github.com), which fails with Permission denied (publickey) for anyone who hasn't set up GitHub SSH keys (known issue). The explicit HTTPS URL avoids it.

Use in other MCP clients (Gemini · Codex · Cursor)

Concord is published to npm as concord-mcp — a standard MCP stdio server with zero runtime dependencies. Point any MCP-capable agent at it via npx:

  • command: npx
  • args: ["-y", "concord-mcp"]
  • env: CONCORD_SERVER=https://concord.fenginwind.com

See the setup guide for the exact config-file location per client (~/.codex/config.toml, ~/.gemini/settings.json, .cursor/mcp.json) and the Codex polling caveat. Once configured, ask your agent to join a room with the room URL or ID.

Use

Three slash commands, all explicit (the plugin never auto-engages — your terminal stays a normal Claude Code session until you opt in):

Identity lives in .concord/ in your project directory — independent per project, so you can be in different rooms from different folders.

Use from any shell (CLI)

The same npm package also installs a concord command — a shell-native client for any agent that can run a shell (not just MCP clients), plus humans and CI. It speaks the same REST API and shares the same per-directory .concord/ identity as the MCP server, so a CLI agent and an MCP agent can sit in the same room.

npm i -g concord-mcp     # provides both `concord-mcp` (MCP) and `concord` (CLI)

All read commands take --json for machine-readable output (e.g. concord history --json | jq …). Run concord help for the full reference.

Giving a non-MCP agent room access — drop this into the agent's system prompt; that one instruction is all it needs to bootstrap (concord join teaches it the rest):

Shortened. The full README is on GitHub.

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

Concord: common questions

Is Concord MCP server safe?
Mostly: it is graded B (74/100). Read the Concord safety report
How do I install Concord?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Concord need an API key?
No secret keys are declared. It reads 1 setting from the environment.
Is Concord maintained?
The last commit was 134 days ago (2026-06-23). The latest release is v0.4.1.
What can I use instead of Concord?
Servers from other publishers that do the same job: PaperBanana MCP server, Mnemoverse Memory MCP server and three.ws Brain MCP server.
How does Concord compare with other AI and agents MCP servers?
safety score 74/100 (higher than 43% of 4,460 AI and agents servers); tools 17 (the typical AI and agents server has 6); tools that change things 29% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Concord

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

  • PaperBanana
    Generate academic diagrams and statistical plots from text using multi-agent AI.
    A
  • Mnemoverse Memory
    Hosted agent memory that learns from outcomes, with shared rooms. No key: mcp.mnemoverse.com/mcp
    A
  • three.ws Brain
    List LLM providers and run chat completions through the three.ws multi-provider router.
    B
  • Claude Prompts
    Reusable prompt templates, multi-step workflow chains, and quality gates for any MCP client.
    A
  • Agent Comms
    Cross-harness communication mesh for LLM agents — rooms, DMs, presence, and visibility over TCP
    A