critic_to_campfire — Bloody Hopes Historical Critic MCP Prompt

critic_to_campfire is one of 1 prompt on the Bloody Hopes Historical Critic MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke critic_to_campfire from your client

• Claude Code Bloody Hopes Historical Critic Prompt/critic_to_campfire run in your project directory
• Claude Desktop Bloody Hopes Historical Critic Prompt/critic_to_campfire ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Bloody Hopes Historical Critic Prompt/critic_to_campfire ~/.cursor/mcp.json
• VS Code Bloody Hopes Historical Critic Prompt/critic_to_campfire .vscode/mcp.json
• Zed Bloody Hopes Historical Critic Prompt/critic_to_campfire ~/.config/zed/settings.json
• Windsurf Bloody Hopes Historical Critic Prompt/critic_to_campfire ~/.codeium/windsurf/mcp_config.json
• Cline Bloody Hopes Historical Critic Prompt/critic_to_campfire ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Bloody Hopes Historical Critic Prompt/critic_to_campfire ~/.gemini/settings.json
• Grok Bloody Hopes Historical Critic Prompt/critic_to_campfire .mcp.json (in your project root)
• ChatGPT Bloody Hopes Historical Critic Prompt/critic_to_campfire Settings → Connectors → Advanced → Developer mode
• Claude.ai Bloody Hopes Historical Critic Prompt/critic_to_campfire Settings → Connectors → Add custom connector
• LangChain Bloody Hopes Historical Critic Prompt/critic_to_campfire pip install langchain-mcp-adapters

Bloody Hopes Historical Critic also offers 2 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 24 September 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.