Code Council MCP Server

Multi-model AI code review server using OpenRouter - get diverse perspectives from multiple LLMs in parallel. Exposed over MCP by the code council mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Code Council runs your code through multiple AI models simultaneously, then shows you where they agree, where they disagree, and what only one model caught.

• One model — might miss a security issue another catches
• Unanimous findings — are almost certainly real problems
• Disagreements — highlight where you should look closer
• Single-model findings — might be noise, or might be the one model that saw something others missed

Adding it to your client

@klitchevo/code-council on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Its toolset

Everything the assistant can do here goes through one of these:

• Single — model findings** might be noise, or might be the one model that saw something others missed
• uses — actions/checkout@v4
• name — Run Code Council Review
• MCP — compatible client (Claude Desktop, Cursor, etc.)
• Scenario — Tool
• Level — Meaning
• Unanimous — All models agree
• Majority — Most models agree
• Disagreement — Models conflict

Configuration

You will need 2 environment variables: OPENROUTER_API_KEY, GITHUB_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js >= 18.0.0 - OpenRouter API key - MCP-compatible client (Claude Desktop, Cursor, etc.)

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Code Council.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the code council mcp server does with a few real requests.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Code Council's toolset — Single, uses, name and 6 more — is a fair guide to whether it matches your workflow. It is maintained by klitchevo; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.