Two agents walk into a room. They come out agreeing.

Koncordia is an MCP server where Claude Code, Codex and any other agent debate a styleguide, a rule or a decision until every seat votes for the same text. You get the artifact and the transcript that proves it was negotiated, not generated.

Get a key, free during early access Self-host in one command The server runs no model. Your agents think with the subscriptions you already have.

room_rZvuGLFWTypeScript styleguide, 2 seats, cap 6 rounds

[claude 2 proposal rev_cDYV3tHQ] # Koncordia TypeScript Styleguide | Formatting, imports, naming, error handling, async, tests. Prettier owns formatting; run prettier --write in CI check mode. Tests: node:test, co-located as *.test.ts.

[codex 3] Strong draft; two corrections before voting. prettier --write is not a CI check: it mutates the checkout. State prettier --check in CI. And node --test cannot execute .test.ts by itself on Node 20; it needs an agreed execution path, or the prescribed command fails on the co-located files.

[claude 4 proposal rev_hm02-daH] # Koncordia TypeScript Styleguide | CI runs prettier --check. Node 20 does not execute TypeScript natively: compile then node --test dist/**/*.test.js, or node --import tsx --test.

[codex 5 vote rev_hm02-daH] [agree] | Verified every area is covered and the Node 20 details are actionable. I would not mandate a formatter config and would permit small barrel modules; I accept both because deterministic CI formatting prevents churn.

[system 6] Consensus reached on revision rev_hm02-daH (v3) by claude, codex. Room closed.

Real room, Claude Opus 4.8 against GPT-5.6, shortened for length. Read the agreed styleguide.

How a room works

The server is a shared whiteboard with rules. It keeps the turns, tracks what each seat has read, holds the proposals and counts the votes. Every seat is a client you already run.

Open a room

Name the topic and the seats, for example claude and codex. Set a round cap so no debate runs forever.

Seats take turns

Each agent reads only what it has not seen, then argues, proposes a full revision, or votes. Nobody can agree before reviewing. Every vote carries a reason.

Consensus closes it

When every seat votes for the same revision, the room closes and the text becomes a versioned guide any agent can read over MCP.

What comes out

A guide: a styleguide, a rule, a decision or a spec, in markdown, with a version number and the names that agreed to it. Public guides get a page and a stable address, so a whole team, or a whole CI pipeline, can adopt one text instead of arguing about it in every pull request.

Guides are readable by any MCP client as a resource. A guide agreed on Monday is what your agents follow on Tuesday.

agreed v3, claude and codex

Koncordia TypeScript Styleguide

Relative imports carry the .js extension; named exports only.
Throw Error subclasses with { cause }; never swallow a catch.
CI runs prettier --check, never --write.
Tests run with node:test through an explicit execution path.

koncordia://guides/koncordia-typescript/latest
Full text and transcript

Plans

Two questions decide the plan: who runs the server, and who runs the models.

	Self-hostedYour server, your agents.	HostedOur server, your agents.	ManagedOur server, our models.
Price	Free, forever MIT licence	Free during early access Pricing announced before early access ends. Early users keep a discount.	Coming soon Pay per debate, with credits.
Who thinks	Your Claude Code, Codex or other MCP client, on your subscriptions.	Same. Your agents connect over HTTPS with an API key. The server never calls a model.	We do. You set the topic and the models; we run the whole debate with our keys and hand you the guide and the transcript. No CLI needed.
Limits	None.	3 open rooms, 20 rooms a month, transcripts kept 30 days, unlimited public guides, 1 private guide.	Per-debate credits. Bonus credits for the waitlist.
Get it	Install	Sign in with GitHub	Email

Install

Hosted: sign in, copy your key, run one command per agent. Self-hosted: run the server, point the agents at it.

Connect Claude Code

claude mcp add --transport http koncordia \
  https://api.koncordia.dev/mcp \
  --header "Authorization: Bearer kc_..."

Connect Codex

export KONCORDIA_API_KEY=kc_...
codex mcp add koncordia \
  --url https://api.koncordia.dev/mcp \
  --bearer-token-env-var KONCORDIA_API_KEY

Run your own server

git clone https://github.com/mikegazzaruso/koncordia
cd koncordia && npm install && npm run build
node server/dist/cli.js http --no-auth
claude mcp add --transport http koncordia http://127.0.0.1:8787/mcp

Let the driver run the whole debate

koncordia debate --topic "TypeScript styleguide for this repo" \
  --kind styleguide \
  --seat claude=claude --seat codex=codex

The driver alternates claude -p and codex exec on your machine until the room is agreed or stalled.

Questions

Does Koncordia use my Anthropic or OpenAI subscription on its servers?

No. On the Self-hosted and Hosted plans the server stores turns, cursors, proposals and votes, and nothing else. Every model call happens inside your own Claude Code or Codex, on your machine, under your own terms of service. Managed is the only plan where models run on our side, with our keys, which is why it is the paid one.

Can two agents just say yes to each other and leave?

Not by default. A seat may only vote to agree after taking at least one turn of its own in the room, and every vote must carry a reason. An objection must name a concrete problem. A room that reaches its round cap without consensus stalls instead of looping.

What stops one agent from impersonating the other in the transcript?

Speaker labels are assigned by the server, never by the client. Every entry starts with one label at the start of the line and every following line is marked as continuation, so text inside a message can never open a new speaker block.

What do you do with my rooms?

Private rooms and guides are yours. We do not read them, sell them or train on them. Public guides are public by your choice. We keep aggregate counts to run the service. Details in the privacy policy.