DebugAI

Worth knowing before you run something that edits your editor config:

npx -y @debugai/mcp uninstall # removes the entry from every client config npx -y @debugai/mcp logout # removes the stored key

npx -y @debugai/mcp install --listprints every supported client, where its config lives on your OS, and whether DebugAI is already in it.

If your agent calls a DebugAI tool before you have signed in, the tool answers with a short code and a URL instead of an error. Confirm it in the browser, tell the agent to try again, and the call goes through. No config editing, and no client restart, because the key is re-read on every call.

Returns the root cause, up to 3 fixes ranked by confidence, the detected framework, and whether the answer came from cache. Since 2.0 each fix also carries, where derivable:edits(exact old/new strings your agent's edit tool can apply directly),unified_diff, andverify_with(a syntax-level check command to run after applying). Read-only: it never touches your files. Applying a fix is your agent's call, and yours.

Every fix is labeled with its verification state, and there are three of them, not two:verified(a mechanical check passed, currently parse and import classes),failed check(confidence capped hard), ornot verified(the confidence number is the model's own estimate, nothing checked it). We label the third case instead of hiding it.

Tell DebugAI whether an applied fix actually worked.

Confirmed rank-1 fixes are remembered per project, so the next hit on the same error starts from the confirmed fix. Failed-fix follow-ups are the feedback that improves future answers. Agents are asked to call this once per applied fix, through the same pipeline human feedback flows through in the VS Code extension.

Paste a traceback and ask "why is this failing?". Claude callsdebug_errorand gets back something like:

Root cause:db.sessionis used after the request context closed.Fix 1 (94% confidence):move the query inside the request handler...

The server tells connecting agents what it is for, but a rule in your project file is the deterministic version. Add this toCLAUDE.md,.cursorrules, or whatever your agent reads:

On any runtime error, exception, or failing test, call the debugai debug_error tool before attempting your own fix. After applying a fix, call report_outcome so the project's error memory stays accurate.

setupcovers this, andinstall --client=<id>covers the case where a client is installed somewhere unusual. If you would still rather edit the file yourself, the entry is the same everywhere:

Runnpx -y @debugai/mcp doctorfirst. It checks your Node version, whether a key is stored and where it came from, whether that key still authenticates against the API, the permissions on the config file, and which detected clients are missing the DebugAI entry. Most answers are in that output.

- "authentication failed": the key was rotated or revoked. Runnpx -y @debugai/mcp login --force.
- Tools do not appear in the client: the client was not restarted, or it reads a different config file.install --listshows which file was written.
- Nothing happens onnpx @debugai/mcp: correct. It is a stdio server waiting for an MCP client to speak first. Use--helpto verify the install.
- Timeouts: deep analyses can take up to 90s. If your client has its own tool timeout, raise it above that.

2.1.1: metadata only. AddsmcpNamefor official MCP registry ownership verification, fixes the npm package page's repository link.

2.1.0: one-command setup. Browser sign-in over a device link (no key pasting), automatic client config writing with backups,doctorfor diagnosing a broken setup, and in-conversation sign-in when an agent calls a tool before you have an account.

2.0.0:report_outcometool, ready-to-applyeditsper fix, and the three-state verification label.

npm install npm test # builds, then runs unit + spawned-process e2e tests

The client is MIT and complete: the stdio server, the device-link sign-in, the config writer, and the tests are all here. The analysis itself runs on DebugAI's servers and is not part of this package.

Issues and pull requests are welcome on that repository.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Create crafted UI components inspired by the best 21st.dev design engineers.

Bring agent evaluations, observability, and synthetic test set generation directly into your IDE for free with Galileo's new MCP server

An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .

MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent

ALAPI MCP Tools,Call hundreds of API interfaces via MCP

AI-powered SVG animation generator that transforms static files into animated SVG components using the Allyson platform

MCP server that gives AI assistants on-demand access to 1,500+ amCharts docs, ~300 code examples, and 1000+ class API references.

APIMatic MCP Server is used to validate OpenAPI specifications using APIMatic. The server processes OpenAPI files and returns validation summaries by leveraging APIMatic’s API.

One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.