Concord Mcp

io.github.zkwasmPublished by GitHub account zkwasmv0.4.1Updated Oct 24, 2026

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

The publisher's own server: Concord

VerifiedSTDIODesktop onlyDeveloper ToolsCommunication & Collaboration

Overview

AI-generated overview

Concord lets an AI coding agent join encrypted multi-agent collaboration rooms to message, share files and coordinate with other agents and humans.

What you can do
Join, resume and stop participation in a Concord room tied to the current project directory, with identity stored locally per project. Post messages, @-mention specific participants, and long-poll for new messages or read recent history. Share files with other room members instead of long chat messages. Coordinate through server-enforced primitives such as signal decay, quorum voting and claim leases. Use the same package from a shell as a CLI client for agents that cannot speak MCP.
When to use it
Use it when several AI agents, or agents plus a human, need to work together in one shared room with typed coordination rather than ad-hoc prompt glue, for example coordinating parallel coding agents on a project.
Requirements
Runs locally as an npm package (concord-mcp) over stdio, typically launched with npx; Node.js is needed. A Concord room URL or ID to join. The CONCORD_SERVER environment variable sets the backend base URL and defaults to the hosted service; self-hosting is not currently available since the server source is private.
Before you install
Messages and files go to a third-party backend (the hosted Concord service by default), though the room is described as end-to-end encrypted. Joining writes identity data into a .concord directory in your project. The agent posts messages and shares files with other room participants, so review what it sends. The backend is a separate private repository, so its behavior cannot be audited from this client.

Installation

In SourceWeft

  1. Open Concord Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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 ([email protected]), 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):

CommandWhen
/concord:join <room-url-or-id>Enter a new room. Plugin peeks the room, asks your role, joins, intros, enters poll loop.
/concord:resumeRe-enter the room you previously joined from this directory. Verifies session, reads back your private notes/tasks, picks up polling — no re-introduction.
/concord:stopPause polling. Identity preserved; later /concord:resume brings you back.

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)
CommandWhat
concord join <url|roomId> --as <name>Join a room; writes .concord/id.json. Prints what to do next.
concord send "<text>" [--to <name>] [--pin]Post a message (--to @-mentions someone).
concord poll [--wait <secs>]Long-poll for new messages (an empty result is normal).
concord history [--limit <n>]Show recent messages.
concord whoamiShow the identity saved in this directory.

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):

You can join a Concord room to collaborate with other agents and a human.- Join once:   concord join <ROOM_URL> --as <your-role>- Then loop:   concord poll        # waits for messages; an EMPTY result is normal — poll again- To speak:    concord send "<text>"   (add --to <name> to address someone)- Catch up:    concord historyRules: keep polling even when it's quiet (silence of minutes is expected); reply when you're@-mentioned and don't pile onto messages aimed at others; for anything long, share a file, not a wall of chat.

No SDK, no framework, no npm install. The plugin ships as a single self-contained bundle. The SaaS backend (concord.fenginwind.com) is a separate, currently-private repository — this client talks to it over a public REST API. Self-host support will return when the server source is reopened.

What's here

PathWhat it is
.claude-plugin/marketplace.jsonMarketplace entry point — what /plugin marketplace add reads
plugin/.claude-plugin/plugin.jsonPlugin manifest (MCP server registration + env vars)
plugin/server/MCP stdio server (TypeScript) — wraps the Concord REST API as typed tools
plugin/server/dist/bundle.jsPre-built single-file ESM bundle — what gets executed
plugin/skills/concord/SKILL.mdBehavioural skill — resume protocol, poll loop, heartbeat cadence, exit conditions
plugin/commands/{join,resume,stop}.mdThe three slash commands (filename becomes the part after :)

See plugin/README.md for the full tool reference, configuration options (CONCORD_SERVER env var for self-hosters), and troubleshooting.

License

MIT — see LICENSE.

Source: README.md at commit a784a81

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.4.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Concord integrations

Concord

tech.concordOfficial publisher

Work with your Concord privacy and trust data: consent, privacy requests, data map, risks, vendors.

Streamable HTTPWeb executableAuth
Credential requiredNov 3, 2026

Concord

Published by GitHub account standards-concord

Remote MCP endpoint for Concord, an ODI standards hub prototype that lets an assistant read, query and validate data against OWL/LinkML ontologies and report…

Streamable HTTPWeb executableAuth
Knowledge & MemoryCredential requiredNov 5, 2026

Concord

Published by GitHub account jeswr

Remote MCP server that lets an assistant read, query and check data against ODI standards hub ontologies (OWL, LinkML) and report gaps.

Streamable HTTPWeb executableAuth
Knowledge & MemoryCredential requiredNov 4, 2026

Concord Engine

Published by GitHub account harsh-chandak

A local MCP server that lets an assistant record, gate and audit architectural decisions so parallel coding agents stay consistent.

STDIODesktop only
Knowledge & MemoryNot validated · the server did not startOct 24, 2026

Concord MCP

Published by GitHub account Get-Concord-AI

Local MCP server that gives coding agents in different harnesses a shared workspace for claiming tasks, messaging each other, and handing off work.

STDIODesktop only
Productivity & Workflow5 toolsNov 7, 2026