inspector-mcp connects your AI agent directly to your running NestJS process via Chrome DevTools Protocol. Instead of you manually debugging, the AI does it:

\- Your guard is rejecting requests but you don't know why → the AI sets a breakpoint inside the guard, hits the endpoint, and reads the request object itself

\- A service method is throwing a 500 → the AI reads the console logs, finds the error, traces it back to the source

\- A value looks wrong inside a pipe or interceptor → the AI steps through execution and inspects every variable in scope at that point

The AI connects, investigates, and comes back with actual runtime values — not guesses based on static code.

Setup:

    nest start --debug
    
    {
      "mcpServers": {
        "inspector": { "command": "npx", "args": ["inspector-mcp"] }
      }
    }

Works with any MCP-compatible client — Claude Desktop, Cursor, Claude Code, VS Code, and others.

Then just try something like:

    "My /api/users endpoint is returning 500. Connect to the process on port 9229,
    set a breakpoint at line 34 of src/routes/users.ts, and tell me what the
    database query result looks like when the error happens."

GitHub: [https://github.com/AbianS/inspector-mcp](https://github.com/AbianS/inspector-mcp)

inspector-mcp: full Node.js debugger for AI agents in NestJS — breakpoints, variable inspection and console access via CDP