MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
Roundtable is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
13
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Multi-model AI council that debates a question and synthesizes an answer (13 tools incl. review_code, debug_issue).
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http roundtable-mcp https://mcp.roundtable.now/mcp
# 2 — ask your agent for something these tools do
# list-models, list-sessions, get-session and 10 more
Roundtable costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MRAll 1 server
mcp.roundtable.now1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http roundtable-mcp https://mcp.roundtable.now/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List available AI models grouped by thinking level (low/medium/high). Shows default models, credit costs, capabilities for each tier. Use this before consult to understand model options.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| thinking_level | string | no | Filter to a specific thinking level |
List your previous MCP tool sessions. Returns session metadata including prompt, tool used, quality score, and credits consumed. Useful for reviewing past council discussions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max results to return |
| offset | integer | no | Pagination offset |
| tool_name | string | no | Filter by tool name (e.g., "consult", "architect") |
Get full details of a previous MCP session by ID. Returns the complete result including participant responses and moderator synthesis. Use list-sessions first to find session IDs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The session ID to retrieve |
Query structured logs from your MCP tool executions. Filter by session, severity level, event type, and time range. Useful for debugging and monitoring tool usage.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| end_time | number | no | End timestamp (ms) for time range filter |
| event | string | no | Filter by event name (e.g., "debate_completed") |
| level | string | no | Filter by log level |
| limit | integer | no | Max results |
| offset | integer | no | Pagination offset |
| session_id | string | no | Filter logs for a specific session |
| start_time | number | no | Start timestamp (ms) for time range filter |
Check your remaining credits, usage limits, and plan info
| Parameter | Type | Required | Notes |
|---|---|---|---|
| verbose | boolean | no | Include detailed per-window rate limit breakdown |
Get the dashboard URL for a previous debate session. Returns the thread link and public URL if the thread is public.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The session ID to get the thread link for |
Set a thread as public or private. Public threads can be shared via URL. Use session_id from a previous debate session.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| is_public | boolean | yes | Set to true to make the thread publicly accessible, false to make it private |
| session_id | string | yes | The session ID from a previous debate |
Consult the AI coding council — multiple models discuss your engineering question sequentially (each sees prior responses), then a moderator synthesizes. Auto-mode by default — AI picks optimal models, roles, and conversation mode from your prompt. Provide explicit models to override (manual mode). Fully configurable: mode, format, roles, models, thinking level.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| context | string | no | Additional background context for the debate (code, docs, requirements) |
| format | string | no | Moderator output format: discussion (narrative), adr (architecture decision), comparison (table), pros-cons |
| mode | string | no | Conversation mode: analyzing (research), brainstorming (ideas), debating (tradeoffs), solving (action plans) |
| models | array | no | Override specific model IDs. Min 3 models. Use list-models to see available options |
| prompt | string | yes | The question, topic, or problem to debate |
| roles | array | no | Inline role names for participants (e.g., ["Security Architect", "Backend Engineer"]) |
| thinking_level | string | no | Controls model quality and cost: low (fast/cheap), medium (balanced), high (maximum reasoning) |
| webhook_url | string | no | Webhook URL to POST results to after completion |
| session_context | array | no | Session IDs to use as context (max 3). Prior moderator summaries will be prepended. |
| knowledge | array | no | Reference knowledge to inject as context |
| auto_route | boolean | no | Auto-select optimal models based on prompt analysis and historical performance |
Architecture design council. Systems Architect, Infrastructure Engineer, and DX Advocate evaluate your system design. Always uses high thinking for maximum depth. Output as ADR.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | yes | What the system should do |
| focus_areas | array | no | Priority areas (e.g., ["security", "performance"]) |
| scale | string | no | Target scale: startup (small team), growth (scaling), enterprise (large org) |
| tech_stack | array | no | Preferred technologies |
| webhook_url | string | no | Webhook URL to POST results to after completion |
Code review council. Senior Engineer, Security Reviewer, and Performance Analyst analyze your code and a moderator synthesizes their findings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The code to review |
| focus | array | no | Review focus areas (e.g., ["security", "performance"]) |
| language | string | no | Programming language (auto-detected if not specified) |
| thinking_level | string | no | Review depth: low (quick scan), medium (balanced), high (thorough) |
| webhook_url | string | no | Webhook URL to POST results to after completion |
Implementation planning council. Tech Lead, Senior Engineer, and QA Strategist break down a feature into actionable steps, identify risks, and define acceptance criteria. Output as ADR.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| codebase_context | string | no | Relevant existing code, file structure, or architecture notes |
| constraints | array | no | Constraints (e.g., ["no breaking changes", "must support offline"]) |
| feature | string | yes | The feature or change to plan |
| tech_stack | array | no | Current tech stack |
| thinking_level | string | no | Planning depth |
| webhook_url | string | no | Webhook URL to POST results to after completion |
| session_context | array | no | Session IDs to use as context (max 3). Prior moderator summaries will be prepended. |
| knowledge | array | no | Reference knowledge to inject as context |
Debugging council. Root Cause Analyst, Systems Engineer, and Edge Case Investigator collaboratively diagnose bugs, analyze errors, and propose fixes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | no | The relevant code where the bug occurs |
| error | string | no | Error message, stack trace, or unexpected output |
| expected_behavior | string | no | What should happen vs what actually happens |
| problem | string | yes | Describe the bug, failure, or unexpected behavior |
| thinking_level | string | no | Analysis depth |
| webhook_url | string | no | Webhook URL to POST results to after completion |
| session_context | array | no | Session IDs to use as context (max 3). Prior moderator summaries will be prepended. |
| knowledge | array | no | Reference knowledge to inject as context |
Tradeoff assessment council. Pragmatist, Skeptic, and Futurist evaluate options from different angles — short-term vs long-term, risk vs reward, simplicity vs flexibility. Output as pros-cons.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| context | string | no | Background context — codebase, team, timeline, constraints |
| decision | string | yes | The decision or question to evaluate |
| options | array | no | Specific options to compare |
| priorities | array | no | What matters most (e.g., ["performance", "dx", "cost"]) |
| thinking_level | string | no | Analysis depth |
| webhook_url | string | no | Webhook URL to POST results to after completion |
| session_context | array | no | Session IDs to use as context (max 3). Prior moderator summaries will be prepended. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Roundtable or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.5.0.
1.5.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Roundtable can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.