debug-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG_MCP_PORT | No | HTTP server port (default: 3000) | 3000 |
| DEBUG_MCP_STORAGE_PATH | No | Storage directory (default: ~/.debug-mcp) | ~/.debug-mcp |
| DEBUG_MCP_RETENTION_DAYS | No | Report retention period in days (default: 7) | 7 |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_debug_reportsA | List all stored debug reports with metadata |
| get_debug_reportA | Get a specific debug report by ID including full logs, error, and screenshot reference |
| ask_user_questionsA | Send questions to browser user and wait for answers. Opens an interactive Q&A modal in the browser. |
| clear_old_reportsB | Delete debug reports older than specified days |
| list_backlogA | List queued debug reports in the backlog with statistics. Returns items sorted by priority (critical > high > medium > low) then by age. |
| get_next_backlog_itemA | Get the next highest-priority pending backlog item to process |
| process_backlog_itemA | Start processing a backlog item. Marks it as in_progress and returns the associated debug report. |
| resolve_backlog_itemB | Mark a backlog item as resolved (issue fixed) |
| dismiss_backlog_itemB | Dismiss a backlog item (not actionable or duplicate) |
| update_backlog_itemB | Update a backlog item's status, priority, or comment |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Latest Debug Report | Get the most recent debug report |
| Debug Report by ID | Get a specific debug report by ID |
| Screenshot by Report ID | Get screenshot image for a specific report |
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/developerlabsai/debug-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server