Model Council MCP server

Model Council

<!-- mcp-name: io.github.Totti0135/model-council -->

English | 简体中文

An MCP server that seats other LLMs at your table. Your assistant asks them, reads their answers as tool results, relays those answers back and forth for critique, and gives you one merged conclusion — inside a single normal conversation, with no copy-paste.

Your assistant chairs the council. Any number of members, from any mix of OpenAI-compatible and Anthropic-compatible endpoints — a hosted API, a self-run gateway, a local server, or several of each.

Tools

Members are stateless and cannot see your conversation, so the chair passes everything they need in each call. That is exactly what makes cross-review work: it puts one member's answer inside another's prompt.

Giving the council something to read

A question is usually about something — a spec, a log, a diff, a screenshot. The obvious way to include it is to paste it into prompt, and that is the expensive one, in the place nobody watches: prompt is an argument the chair writes, so a long document costs a full copy of itself in generated tokens on every call, and what reaches the members is whatever the chair managed to reproduce. For forty pages that is not reliably the document. A council reviewing a paraphrase is not reviewing the thing, and nothing in the transcript would say so.

materials names it instead:

ask_all(
  prompt="Where would this break under load?",
  materials=[
    {"label": "The design", "path": "/abs/path/design.md"},
    {"label": "Latency graph", "path": "/abs/path/p99.png"},
    {"label": "My summary", "text": "…something with no file behind it…"},
  ],
  rounds=2,
)

The server reads each one and puts it ahead of the question, in the same place for every member and every round. The position is not presentation:

makes their disagreement about the document rather than about which version each was given.

• Identical bytes. Every member argues with the same copy, which is what

the same in every call of a discussion. The Anthropic format is told so explicitly, with one cache_control breakpoint at that boundary; endpoints that cache by prefix on their own get the shape they need either way. Set "cache": false on a member whose gateway rejects the field.

• A prefix that can be cached. Everything up to the end of the material is

document, and ask_all carries the material into round 2 and 3 by itself.

• The chair pays once. A path costs the chair a line, not a copy of the

Shortened. The full README is on GitHub.