@debugai/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUGAI_API_KEY | No | Your API key. Overrides api_key in the config file. | |
| DEBUGAI_API_BASE | No | Override for self-hosted or staging setups. | DebugAI production |
| DEBUGAI_TIMEOUT_MS | No | Per-request deadline in milliseconds. | 150000 |
| DEBUGAI_CONFIG_PATH | No | Alternate config file location. | ~/.debugai/config.json |
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 |
|---|---|
| debug_errorA | Analyze a runtime error, exception, or stack trace and return root cause + ranked fixes. Use whenever the user pastes an error, asks "why is this failing", "what does this error mean", "debug this stack trace", "fix this exception", "analyze this traceback", or shows a Traceback / TypeError / ReferenceError / AttributeError. Works for Python, JavaScript, TypeScript, Go, Rust. Returns root cause explanation plus up to 3 ranked fixes with machine-applicable code edits. After applying a fix, report whether it worked via the report_outcome tool. |
| report_outcomeA | Report whether a DebugAI fix actually worked after you applied it. Call this ONCE after applying (or abandoning) a fix from debug_error, passing the debug_log_id from that response. If the fix failed, include the new error text — failed-fix follow-ups directly improve future answers for this codebase, and confirmed rank-1 fixes are remembered for the whole team. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/1shizaan/debugai-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server