explain-exit-code — developer tools MCP Prompt
explain-exit-code
is one of 8 prompts on the
developer tools
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke explain-exit-code from your client
- Claude Code developer tools Prompt/explain-exit-code run in your project directory
- Claude Desktop developer tools Prompt/explain-exit-code ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor developer tools Prompt/explain-exit-code ~/.cursor/mcp.json
- VS Code developer tools Prompt/explain-exit-code .vscode/mcp.json
- Zed developer tools Prompt/explain-exit-code ~/.config/zed/settings.json
- Windsurf developer tools Prompt/explain-exit-code ~/.codeium/windsurf/mcp_config.json
- Cline developer tools Prompt/explain-exit-code ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI developer tools Prompt/explain-exit-code ~/.gemini/settings.json
- Grok developer tools Prompt/explain-exit-code .mcp.json (in your project root)
- ChatGPT developer tools Prompt/explain-exit-code Settings → Connectors → Advanced → Developer mode
- Claude.ai developer tools Prompt/explain-exit-code Settings → Connectors → Add custom connector
- LangChain developer tools Prompt/explain-exit-code pip install langchain-mcp-adapters
Other prompts on this server
developer tools also offers 200 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 5 November 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.