Skip to main content
Glama

๐Ÿช‘ Roundtable

A council of frontier models โ€” for the decisions that matter.

License: MIT A Frontier Infra project Website CLI ยท MCP

One question โ†’ many minds โ†’ one decision.

Fan a question out to Grok, Codex/OpenAI, GLM, MiniMax, Claude, and Gemini in parallel, optionally deliberate to consensus with a chaired vote, and get back one decided answer โ€” from the command line or any MCP-capable coding harness.

curl -fsSL https://roundtable.sh/install.sh | bash

Why Roundtable?

Every model has a blind spot it can't see. Right before an irreversible call โ€” an architecture, a migration, a rewrite โ€” is exactly when one model's confident answer deserves a second (and third, and fourth) opinion.

Roundtable convenes a panel of frontier models. Each answers independently; then, for high-stakes calls, a multi-round deliberation lets every head read the whole table and revise until a Claude chair declares CONSENSUS or names the remaining disagreement. Disagreement is signal, not noise.

  • ๐Ÿ—ณ๏ธ Advisory (default) โ€” every head answers once, blind to the others. Raw, independent reads.

  • โš–๏ธ Deliberation (--rounds N) โ€” heads see each other and revise; a neutral chair rules CONSENSUS / CONTINUE and stops early on agreement.

  • ๐Ÿ”‘ API keys are enough โ€” no local CLIs required. Missing heads are skipped; the council runs on whatever subset you've configured.

  • ๐Ÿ“ฆ One binary, everywhere โ€” a CLI, an MCP server, and a one-command installer that wires itself into your coding harness.

Related MCP server: compare-mcp

Example

$ roundtable "Reply with exactly: OK three words" --heads claude,gemini

# ๐Ÿช‘ Round Table โ€” 2 heads โ€” advisory
## ๐Ÿ”ต Claude (claude-opus-4-8, Anthropic)      โ†’ OK three words
## โœจ Gemini (gemini-3.1-pro-preview, Google)  โ†’ OK three words

Add --rounds 3 and the heads deliberate; a chair prints VERDICT: CONSENSUS (or CONTINUE) with the points they agreed on and any dissent named.

Install

curl -fsSL https://roundtable.sh/install.sh | bash

Or pick your package manager โ€” all four deliver the same engine:

pip install roundtable
uv tool install roundtable
brew install frontier-infra/tap/roundtable

The installer places the engine under ${XDG_DATA_HOME:-~/.local/share}/roundtable, symlinks roundtable into ~/.local/bin, and prints a PATH hint if needed.

Quickstart

# 1. Configure keys (masked prompts; shows which heads are โœ“/โœ—). Stored chmod-600
#    in ~/.config/roundtable/config.env. Any subset works โ€” missing heads are skipped.
roundtable auth

# 2. Ask the council
roundtable "Postgres or SQLite for a single-tenant internal tool?"

# 3. Deliberate to consensus on a high-stakes call
roundtable ask -q "Should we rewrite the billing service in Go?" --rounds 3

roundtable doctor shows which heads are configured and pings each for reachability.

Flags

-q/--question ยท -c/--context <file> (shared background for every head) ยท --heads grok,codex,openai,glm,minimax,claude,gemini ยท --rounds N (deliberation) ยท --research (web on, multi-step) ยท --timeout <secs> ยท --out <file>.

Exit 0 if at least one head answered.

The heads

Head

Provider

Key / auth

๐Ÿค– Grok

xAI

XAI_API_KEY (or local grok CLI / Hermes OAuth)

๐Ÿง  Codex

OpenAI

local codex CLI (read-only)

๐Ÿง  OpenAI

OpenAI

OPENAI_API_KEY (direct API โ€” no local CLI needed)

๐ŸŸฃ GLM

Z.AI

ZAI_API_KEY

๐ŸŸ  MiniMax

MiniMax

MINIMAX_API_KEY

๐Ÿ”ต Claude

Anthropic

ANTHROPIC_API_KEY (also the deliberation chair)

โœจ Gemini

Google

GEMINI_API_KEY / GOOGLE_API_KEY

Heads with no key/CLI are skipped inline โ€” the council runs on whatever subset you've configured, so API keys alone are enough (no local CLIs required).

MCP + wire into your harness

Roundtable ships an MCP server as a subcommand of the one binary:

roundtable mcp serve     # stdio JSON-RPC; one tool: roundtable(question, heads?, rounds?, research?)
roundtable mcp config    # prints the server JSON block to paste manually

Auto-wire detected harnesses (idempotent โ€” backs up first, never clobbers):

roundtable install                  # detect + wire everything present
roundtable install --harness cursor,codex
roundtable install --all            # non-interactive

Wires Claude Code (skill + MCP), Cursor (~/.cursor/mcp.json), Codex CLI (~/.codex/config.toml), and prints a generic JSON block for anything else:

{ "command": "roundtable", "args": ["mcp", "serve"] }

Commands

roundtable "question"          shorthand for `ask`
roundtable ask                 run the council (all engine flags)
roundtable auth [provider]     configure API keys (masked, chmod-600)
roundtable models              per-head model picker
roundtable heads               enable/disable heads
roundtable doctor              which heads are configured + reachability ping
roundtable config              show / edit config.env
roundtable mcp serve|config    MCP stdio server / print config
roundtable install             auto-wire detected harnesses
roundtable version | update    show version / upgrade in place

For agents

Building on top of Roundtable? See AGENTS.md โ€” a concise guide for an AI agent to install, configure, run, and wire Roundtable into its own harness.

License

MIT ยฉ Frontier Infra

A
license - permissive license
-
quality - not tested
B
maintenance

Maintenance

โ€“Maintainers
โ€“Response time
โ€“Release cycle
1Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/frontier-infra/roundtable'

If you have feedback or need assistance with the MCP directory API, please join our Discord server