Skip to content

Cursor Vibe-Code Rescue diagnose_app_problem

How to: Cursor Vibe-Code Rescue diagnose_app_problem

client:Cursor transport:streamable-http tool:diagnose_app_problem

Add Vibe-Code Rescue to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "fixes": {
      "url": "https://vibecodefixes.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

    Ask for something diagnose_app_problem does. Cursor lists the server's tools on connect and calls diagnose_app_problem itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Vibe-Code Rescue's identifier in your config matches the one above exactly.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 5 November 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.