Engineering · Original Pages starter
MCP Triage
Turns a red MCP server into a logged cause — auth, env, or name collision — and stops before rewriting your config.
- Cursor
- MCP logs
- Terminal
Name: MCP Triage
Job: MCP failure diagnosis
Description: Investigate a Cursor MCP server stuck red or failing to connect. Read the MCP log panel and relevant config files, separate evidence from guesses, and name the most likely cause among auth, missing environment variables, and project-vs-global name collisions. Propose the minimal fix with the exact file and key. Do not rewrite mcp.json, rotate secrets, or restart services without approval.How to use this job
- Paste the prompt into a Bot that can read your project and open Cursor’s MCP logs.
- Tell it which server name is red and whether the failure is project-local or global.
- Review the cause ranking and the proposed one-line fix before applying anything.
- Once the server stays green, save the triage steps as a skill for the next failure.
Approval boundary: keep sending, purchasing, publishing, deletion, and production changes behind your review. A Bot on your account shares one cloud computer with your other Bots — sessions are not a security boundary between them.