crashwebsite-mcp

An MCP server that exposes your plugin crash reports to Claude. It is a thin, read-only client over the crash site's JSON API (/api/...), authenticated by your personal API key and scoped to every plugin you can see across all your teams.

Tools

Crash/comment tools take an optional plugin (id, code, or name) — only required when you can access more than one plugin. The list tools also accept filters: ver, verop (=/>=/<=), os (win/mac/linux), app, limit. Write tools are permission-checked server-side: comments need team membership; adding/deleting a plugin needs owner/admin on the team, and delete_plugin requires confirm to equal the plugin's exact plugin_code.

Related MCP server: claude-oracle-mcp

Configuration

Set via environment variables:

• CRASH_API_KEY (required) — your personal API key. Generate it on the crash site's Account page. It grants read access to every plugin you can see; keep it secret, like a password.

• CRASH_API_BASE_URL (optional) — defaults to https://crashreports.rabiensoftware.com.

Install & build

Run it on your own machine — it talks to the public crash site by default, so there's no server-side setup.

git clone https://github.com/PluginCrashReports/crashwebsite-mcp.git
cd crashwebsite-mcp
npm install
npm run build

Use with Claude Code / Desktop

Claude Code, one line:

claude mcp add crashwebsite -e CRASH_API_KEY=your-plugin-crash-api-key \
  -- node /absolute/path/to/crashwebsite-mcp/dist/index.js

Or add to your MCP config (e.g. claude_desktop_config.json) directly:

{
  "mcpServers": {
    "crashwebsite": {
      "command": "node",
      "args": ["/absolute/path/to/crashwebsite-mcp/dist/index.js"],
      "env": {
        "CRASH_API_KEY": "your-plugin-crash-api-key"
      }
    }
  }
}

To point at a self-hosted instance instead of the public site, also set CRASH_API_BASE_URL.

Then ask Claude things like "what are the top crashes this week?", "show recent mac crashes for 1.0.7", or "open crash 3 and explain the stack".