debug_with_corpusfetch — CorpusFetch MCP Prompt
debug_with_corpusfetch
is one of 1 prompt on the
CorpusFetch
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke debug_with_corpusfetch from your client
- Claude Code CorpusFetch Prompt/debug_with_corpusfetch run in your project directory
- Claude Desktop CorpusFetch Prompt/debug_with_corpusfetch ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor CorpusFetch Prompt/debug_with_corpusfetch ~/.cursor/mcp.json
- VS Code CorpusFetch Prompt/debug_with_corpusfetch .vscode/mcp.json
- Zed CorpusFetch Prompt/debug_with_corpusfetch ~/.config/zed/settings.json
- Windsurf CorpusFetch Prompt/debug_with_corpusfetch ~/.codeium/windsurf/mcp_config.json
- Cline CorpusFetch Prompt/debug_with_corpusfetch ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI CorpusFetch Prompt/debug_with_corpusfetch ~/.gemini/settings.json
- Grok CorpusFetch Prompt/debug_with_corpusfetch .mcp.json (in your project root)
- ChatGPT CorpusFetch Prompt/debug_with_corpusfetch Settings → Connectors → Advanced → Developer mode
- Claude.ai CorpusFetch Prompt/debug_with_corpusfetch Settings → Connectors → Add custom connector
- LangChain CorpusFetch Prompt/debug_with_corpusfetch pip install langchain-mcp-adapters
Read from the server itself, by connecting to it and calling prompts/list on 11 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.