Converse MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port | 3157 |
| LOG_LEVEL | No | Logging level | info |
| XAI_API_KEY | No | X.AI API key | |
| CODEX_API_KEY | No | Codex API key (optional if ChatGPT login available) | |
| GEMINI_API_KEY | No | Google Gemini API key (takes priority over GOOGLE_API_KEY) | |
| GOOGLE_API_KEY | No | Alternative Google API key | |
| OPENAI_API_KEY | No | OpenAI API key | |
| MISTRAL_API_KEY | No | Mistral API key | |
| DEEPSEEK_API_KEY | No | DeepSeek API key | |
| MCP_TOOL_TIMEOUT | No | Tool timeout in ms (system-wide) | |
| OPENROUTER_TITLE | No | OpenRouter title | |
| ANTHROPIC_API_KEY | No | Anthropic API key | |
| CODEX_SANDBOX_MODE | No | Codex sandbox mode | read-only |
| OPENROUTER_API_KEY | No | OpenRouter API key | |
| OPENROUTER_REFERER | No | OpenRouter referer | |
| SUMMARIZATION_MODEL | No | Model for summarization | gpt-5-nano |
| CODEX_SKIP_GIT_CHECK | No | Skip git check | true |
| CODEX_APPROVAL_POLICY | No | Codex approval policy | never |
| MAX_MCP_OUTPUT_TOKENS | No | Max output tokens (system-wide) | |
| OPENROUTER_DYNAMIC_MODELS | No | Enable dynamic models | true |
| ENABLE_RESPONSE_SUMMARIZATION | No | Enable AI-generated summaries | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chatA | UNIFIED CHAT — talk to one or more AI models. mode "chat" (default): 1..N models answer independently in parallel. mode "consensus": ≥2 models answer, then refine after seeing each other. mode "roundtable": models answer sequentially, each building on the running transcript. Supports files, images, and continuation_id for multi-turn threads (you may switch modes on resume). Use model "auto" for automatic selection. IMPORTANT: use the "files" parameter to share code/file content instead of pasting into the prompt. |
| check_statusA | Check the status and progress of async jobs. Query specific jobs by continuation_id or list the 10 most recent jobs. Returns job status with start time and progress information. |
| cancel_jobA | Cancel a running async job by its continuation_id. Terminates queued or running jobs with graceful cleanup. Preserves partial results when available. |
| decideA | DECIDE — ask a decision model (OpenAI gpt-6-luna, TypeSafe Jev, Cloudflare Clef) typed questions about a state and get calibrated answers, not text. Question types: "noul" (yes/no → probability 0..1), "choice" (pick one of 2–255 named options → choice, per-option probabilities, confidence), "score" (ordered rubric of 2–10 levels → weighted position, per-level probabilities, confidence), "box" (where one target is in an image → left/top/right/bottom edges as 0..1 fractions of width/height, confidence; jev-1.14 / jev-preview only, needs an image, always returns a box, so pair it with a noul asking whether the target is there). Batch independent questions over the same state into one call: they are judged in parallel and in isolation, so none sees another's answer; each extra question adds its own input tokens. Best for fast semantic judgments (classify, route, select, verify, rank). Ask one narrow, coherent judgment per question, with its full meaning in the question; split independently useful dimensions, but a bounded action choice or contextual interpretation is a valid single question. Do counting, arithmetic, and date comparison in code. confidence measures how concentrated the distribution is, not permission to act: take the top option to pick a best, and treat a noul near 0.5 as "yes and no equally likely". No explanations are returned. Images work with gpt-6-luna (PNG/JPEG/WebP), Jev on TypeSafe (PNG/JPEG, 256–1568 px per side, upright pixels: EXIF rotation is ignored), and Clef (PNG/JPEG/WebP, up to 4, ~180 KB total); "auto" skips models that cannot take the images. gpt-6-luna may answer a question with type "refusal" instead of a value: treat it as unanswered, never as a no. Limits per model: Jev ~64k tokens per request (~32k for state plus the longest question), and on TypeSafe a request over that is resent once in long-context mode (262k, slower and less accurate; the result says "long context"); Clef ~64k tokens and at most 64 questions named with letters, digits, "_", ".", "-". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| help | Comprehensive guide for Converse MCP Server - tools, models, parameters, and configuration |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Help Documentation | Comprehensive guide for the Converse MCP Server including all tools, parameters, providers, and models |
TDQS
Scored across 4 tools
Each tool targets a distinct action: chat (free-form conversation), decide (typed structured judgments), check_status (query jobs), and cancel_job (terminate jobs). decide and chat both query models but the typed-output versus open-text distinction is clearly stated, and cancel_job vs check_status differ by action, so confusion risk is low.
Naming is uniformly lowercase snake_case with no style mixing. Two tools follow the verb_noun pattern (cancel_job, check_status) while decide and chat are single verbs, a minor deviation but still clear and predictable.
Four tools is a lean but defensible surface for a multi-model converse server, since chat and decide absorb broad functionality through parameters. It is slightly thin, with no discovery tool for models or job submission, but nothing feels redundant.
The surface covers the core lifecycle: initiate conversations/decisions (chat, decide) and manage resulting async jobs (check_status, cancel_job). Minor gaps exist—no explicit model-listing or job-submission tool—but the main workflows are workable.