Server Details
Multi-model AI debates: GPT-4o, Claude, Gemini & 200+ models discuss, then synthesize insight.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
13 toolsassess-tradeoffsInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | Background context — codebase, team, timeline, constraints | |
| options | No | Specific options to compare | |
| decision | Yes | The decision or question to evaluate | |
| priorities | No | What matters most (e.g., ["performance", "dx", "cost"]) | |
| webhook_url | No | Webhook URL to POST results to after completion | |
| thinking_level | No | Analysis depth | medium |
| session_context | No | Session IDs to use as context (max 3). Prior moderator summaries will be prepended. |
check-usageInspect
Check your remaining credits, usage limits, and plan info
| Name | Required | Description | Default |
|---|---|---|---|
| verbose | No | Include detailed per-window rate limit breakdown |
consult-councilInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Conversation mode: analyzing (research), brainstorming (ideas), debating (tradeoffs), solving (action plans) | debating |
| roles | No | Inline role names for participants (e.g., ["Security Architect", "Backend Engineer"]) | |
| format | No | Moderator output format: discussion (narrative), adr (architecture decision), comparison (table), pros-cons | discussion |
| models | No | Override specific model IDs. Min 3 models. Use list-models to see available options | |
| prompt | Yes | The question, topic, or problem to debate | |
| context | No | Additional background context for the debate (code, docs, requirements) | |
| knowledge | No | Reference knowledge to inject as context | |
| auto_route | No | Auto-select optimal models based on prompt analysis and historical performance | |
| webhook_url | No | Webhook URL to POST results to after completion | |
| thinking_level | No | Controls model quality and cost: low (fast/cheap), medium (balanced), high (maximum reasoning) | medium |
| session_context | No | Session IDs to use as context (max 3). Prior moderator summaries will be prepended. |
debug-issueInspect
Debugging council. Root Cause Analyst, Systems Engineer, and Edge Case Investigator collaboratively diagnose bugs, analyze errors, and propose fixes.
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | The relevant code where the bug occurs | |
| error | No | Error message, stack trace, or unexpected output | |
| problem | Yes | Describe the bug, failure, or unexpected behavior | |
| knowledge | No | Reference knowledge to inject as context | |
| webhook_url | No | Webhook URL to POST results to after completion | |
| thinking_level | No | Analysis depth | medium |
| session_context | No | Session IDs to use as context (max 3). Prior moderator summaries will be prepended. | |
| expected_behavior | No | What should happen vs what actually happens |
design-architectureInspect
Architecture design council. Systems Architect, Infrastructure Engineer, and DX Advocate evaluate your system design. Always uses high thinking for maximum depth. Output as ADR.
| Name | Required | Description | Default |
|---|---|---|---|
| scale | No | Target scale: startup (small team), growth (scaling), enterprise (large org) | startup |
| tech_stack | No | Preferred technologies | |
| description | Yes | What the system should do | |
| focus_areas | No | Priority areas (e.g., ["security", "performance"]) | |
| webhook_url | No | Webhook URL to POST results to after completion |
get-logsInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| event | No | Filter by event name (e.g., "debate_completed") | |
| level | No | Filter by log level | |
| limit | No | Max results | |
| offset | No | Pagination offset | |
| end_time | No | End timestamp (ms) for time range filter | |
| session_id | No | Filter logs for a specific session | |
| start_time | No | Start timestamp (ms) for time range filter |
get-sessionInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | The session ID to retrieve |
get-thread-linkInspect
Get the dashboard URL for a previous debate session. Returns the thread link and public URL if the thread is public.
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | The session ID to get the thread link for |
list-modelsInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| thinking_level | No | Filter to a specific thinking level |
list-sessionsInspect
List your previous MCP tool sessions. Returns session metadata including prompt, tool used, quality score, and credits consumed. Useful for reviewing past council discussions.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results to return | |
| offset | No | Pagination offset | |
| tool_name | No | Filter by tool name (e.g., "consult", "architect") |
plan-implementationInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| feature | Yes | The feature or change to plan | |
| knowledge | No | Reference knowledge to inject as context | |
| tech_stack | No | Current tech stack | |
| constraints | No | Constraints (e.g., ["no breaking changes", "must support offline"]) | |
| webhook_url | No | Webhook URL to POST results to after completion | |
| thinking_level | No | Planning depth | medium |
| session_context | No | Session IDs to use as context (max 3). Prior moderator summaries will be prepended. | |
| codebase_context | No | Relevant existing code, file structure, or architecture notes |
review-codeInspect
Code review council. Senior Engineer, Security Reviewer, and Performance Analyst analyze your code and a moderator synthesizes their findings.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | The code to review | |
| focus | No | Review focus areas (e.g., ["security", "performance"]) | |
| language | No | Programming language (auto-detected if not specified) | |
| webhook_url | No | Webhook URL to POST results to after completion | |
| thinking_level | No | Review depth: low (quick scan), medium (balanced), high (thorough) | medium |
set-thread-visibilityInspect
Set a thread as public or private. Public threads can be shared via URL. Use session_id from a previous debate session.
| Name | Required | Description | Default |
|---|---|---|---|
| is_public | Yes | Set to true to make the thread publicly accessible, false to make it private | |
| session_id | Yes | The session ID from a previous debate |
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!