MCP AI Bug Helper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENROUTER_API_KEY | Yes | Personal OpenRouter API key (required) | |
| OPENROUTER_APP_NAME | No | Optional custom analytics tag for OpenRouter | MCP AI Bug Helper |
| OPENROUTER_REFERRER | No | Optional referrer URL for OpenRouter dashboard |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask-coding-advisorsB | Queries three OpenRouter coding specialists (free tier) and falls back to premium models when rate limited. |
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 ambiguity or overlap between tools. The tool has a distinct purpose of querying coding specialists, so an agent cannot misselect between non-existent alternatives.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The tool name 'ask-coding-advisors' follows a clear verb_noun pattern, but consistency cannot be assessed across a set of one.
One tool is generally too few for a server's purpose, as it limits functionality and suggests an incomplete or trivial scope. For a bug helper server, a single tool is insufficient to cover typical operations like analyzing, fixing, or testing code, making it feel thin and under-scoped.
The server's purpose as a bug helper implies a need for tools to handle various aspects of debugging, but with only one tool for querying advisors, there are significant gaps. Missing operations like code analysis, error detection, or solution implementation make the surface severely incomplete for the domain.