Error Debugging MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | The Node.js environment mode | development |
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
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| detect-errorsC | Detect errors from various sources (console, runtime, build, test) |
| analyze-errorC | Perform deep analysis of a specific error |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| explain-error | Generate a detailed explanation of an error |
| suggest-fix | Generate fix suggestions for an error |
| analyze-performance | Analyze performance issues and suggest optimizations |
| debug-guidance | Provide debugging guidance and strategies |
| code-review | Perform code review and identify potential issues |
| error-prevention | Suggest ways to prevent similar errors in the future |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Error Logs | Real-time error logs and history |
| Performance Metrics | Performance profiling data and metrics |
| Memory Usage | Memory usage statistics and leak detection |
| Debug Sessions | Active and historical debug sessions |
| Configuration | Server configuration and settings |
| Error Patterns | Known error patterns and signatures |
| Fix Suggestions | AI-generated fix suggestions for errors |
| Breakpoints | Active breakpoints and their status |
| Call Stack | Current call stack information |
| Variables | Variable values and watch expressions |
TDQS
Scored across 2 tools
detect-errors (finding errors across sources) and analyze-error (deep analysis of a specific error) have fairly distinct purposes and reasonable boundaries. There is some conceptual overlap since both operate on errors, but the detect-then-analyze split is understandable.
Both tools follow a consistent hyphenated verb_noun pattern (detect-errors, analyze-error). The only minor deviation is singular ('error') vs plural ('errors'), which does not harm readability.
Two tools is thin for a debugging server, though each earns its place. The scope feels borderline minimal—a couple more operations would round out the surface.
Detect and analyze cover discovery and diagnosis, but there are notable gaps: no way to resolve, suppress/ignore, or list/track errors, leaving the error lifecycle incomplete.