diagnose_app_problem — Vibe-Code Rescue MCP Tool
diagnose_app_problem
(diagnose app problem) is one of 1 tool on the
Vibe-Code Rescue
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call diagnose_app_problem from your client
- Claude Code Vibe-Code Rescue diagnose_app_problem run in your project directory
- Claude Desktop Vibe-Code Rescue diagnose_app_problem ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Vibe-Code Rescue diagnose_app_problem ~/.cursor/mcp.json
- VS Code Vibe-Code Rescue diagnose_app_problem .vscode/mcp.json
- Zed Vibe-Code Rescue diagnose_app_problem ~/.config/zed/settings.json
- Windsurf Vibe-Code Rescue diagnose_app_problem ~/.codeium/windsurf/mcp_config.json
- Cline Vibe-Code Rescue diagnose_app_problem ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Vibe-Code Rescue diagnose_app_problem ~/.gemini/settings.json
- Grok Vibe-Code Rescue diagnose_app_problem .mcp.json (in your project root)
- ChatGPT Vibe-Code Rescue diagnose_app_problem Settings → Connectors → Advanced → Developer mode
- Claude.ai Vibe-Code Rescue diagnose_app_problem Settings → Connectors → Add custom connector
- LangChain Vibe-Code Rescue diagnose_app_problem pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http fixes https://vibecodefixes.com/mcp
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.