MCP server for uploading debug incidents to Debug Memory
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"debug-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Debug Incident MCP Server An MCP (Model Context Protocol) server for uploading debug incidents to Debug Memory via Cursor. ## Installation ### 1. Install the MCP Server Clone or download this repository: ```bash git clone https://github.com/yourusername/debug-mcp.git cd debug-mcp ``` ### 2. Install Dependencies Using [uv](https://github.com/astral-sh/uv) (recommended): ```bash uv sync ``` This creates a virtual environment at `.venv` and installs all dependencies. Or install from PyPI using uv: ```bash uv pip install debug-mcp ``` ### 3. Get Your API Key 1. Go to your **Debug Memory** dashboard 2. Navigate to **Settings** → **API Keys** 3. Create a new API key 4. Copy the key (starts with `dm_`) ### 4. Configure Cursor See **[Cursor Setup Guide](cursor-setup.md)** for detailed instructions. Quick config - create or edit `.cursor/mcp.json` in your project: ```json { "mcpServers": { "debug-incident": { "command": "uvx", "args": ["debug-mcp"], "env": { "WORKSPACE_API_KEY": "dm_your_api_key_here" } } } } ``` **⚠️ Replace:** - `dm_your_api_key_here` with your API key from Debug Memory ### 5. Restart Cursor Close and reopen Cursor for the MCP server to load. ## Usage Once configured, the MCP server exposes these tools (see `docs/tools.md` for the full workflow and next_action behavior): ### 1) `ranked_solutions` - Search similar incidents and return **env-aware ranked solutions** - **Inputs**: `query_text` (required), `env` (required), `limit` (optional, default 5) - **Output**: lookup_id, ranked solutions, recommended solution, next_action ### 2) `add_incident` - Create a **new incident + solution + outcome** (blocks duplicates if a similar incident already exists) - **Inputs**: `title`, `summary`, `error_signature`, `tags`, `steps`, `env`, `worked`, `notes` (optional) ### 3) `add_solution` - Add a new fix (or env-specific variant) for an existing incident - **Inputs**: `incident_id` (required), `ste…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.