fusion-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENROUTER_API_KEY | Yes | OpenRouter API key required for authentication. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fusion_askA | Ask OpenRouter Fusion: a panel of models answers your prompt in parallel (with web search), a judge compares them, and one synthesized answer is returned — stronger than any single model. Use for research, expert critique, or any question where being wrong is costly. Costs more than a single call (panel + judge completions). |
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 1 tool
With only one tool, there is no possibility of overlapping or confusing tools. The single tool's purpose is clearly defined and distinct.
With a single tool, the naming is trivially consistent. The verb_noun pattern (fusion_ask) is clear and well-formed.
A single tool is too few for a typical MCP server, making the tool surface feel sparse. Even if the tool is powerful, the server lacks the breadth expected of a useful toolkit.
The server fully covers its stated purpose of asking a fusion panel, but there are minor gaps such as no configuration options or alternative request modes. The core functionality is complete, but some auxiliary features are missing.