brainstorm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROQ_API_KEY | No | API key for Groq. | |
| OPENAI_API_KEY | No | API key for OpenAI. | |
| MISTRAL_API_KEY | No | API key for Mistral. | |
| DEEPSEEK_API_KEY | No | API key for DeepSeek. | |
| TOGETHER_API_KEY | No | API key for Together AI. | |
| BRAINSTORM_CONFIG | No | Path to the brainstorm.config.json file which defines AI providers and their settings. | |
| OPENAI_DEFAULT_MODEL | No | Default model ID for OpenAI used if no config file exists. | |
| DEEPSEEK_DEFAULT_MODEL | No | Default model ID for DeepSeek used if no config file exists. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| brainstormA | Run a multi-round brainstorming debate between multiple AI models. IMPORTANT: Before calling this tool, you MUST ask the user to choose a mode:
Present these two options to the user with a one-liner explanation, then proceed based on their choice. For API mode: set mode='api'. When participate=true (default), YOU also participate as a debater alongside external models via brainstorm_respond. For Hosted mode: set mode='hosted'. Ask the user which models to use, then spawn sub-agents for each model, collect responses, and call brainstorm_collect. |
| brainstorm_respondA | Submit YOUR (Claude's) response for the current round of an interactive brainstorm session. After the brainstorm tool returns external models' responses, call this tool with your substantive contribution. Read all responses carefully and engage with specific points — agree, disagree, build upon, or challenge ideas. Do not just summarize. After your response, the next round runs automatically (or synthesis if final round). |
| brainstorm_collectA | Submit collected model responses for a hosted brainstorm session. After receiving prompts from |
| brainstorm_quickA | Get instant multi-model perspectives on any question — no debate rounds, no synthesis delay. Fires all models in parallel and returns a compact comparison. Under 10 seconds. Use this for quick second opinions, snap decisions, or when you want diverse perspectives fast. For deeper analysis with multiple rounds and synthesis, use the |
| brainstorm_reviewA | Multi-model code review. Pass a diff and get structured findings with severity, file/line references, and a verdict (approve / approve with warnings / needs changes). Multiple models review independently, then findings are synthesized and deduplicated. Use this for PR reviews, code audits, or pre-commit checks. |
| list_providersA | List all configured AI providers and their default models for brainstorming. Includes locally installed agent CLIs (claude, codex, ...) which run on an existing subscription instead of metered API credits. |
| add_providerA | Add a new AI provider for brainstorming. Supports any OpenAI-compatible API, or a locally installed agent CLI (kind='cli') that runs on an existing subscription instead of API credits. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct role: the main brainstorm tool handles debate setup, with dedicated helpers for API (brainstorm_respond) and hosted (brainstorm_collect) modes. Brainstorm_quick is a fast parallel mode, brainstorm_review is code-specific, and list/add_provider manage providers. No overlapping purposes.
All tools follow a consistent snake_case verb_noun pattern. Core brainstorming actions are prefixed with 'brainstorm_', while provider management uses list_providers and add_provider. Naming is predictable and clear.
Seven tools is well-scoped for a brainstorming server. It covers the core debate workflow (main, respond, collect), a quick alternative, a specialized code review mode, and provider management, without unnecessary bloat or missing essentials.
The surface covers the full brainstorming workflow—multi-round debate, quick requests, code review, and provider setup. Minor gaps exist in provider management (no update/delete) and no explicit session management, but these are non-critical and easily worked around.