search_corpus — Bloody Hopes Historical Critic MCP Tool Read-only
search_corpus
(search corpus) is one of 13 tools on the
Bloody Hopes Historical Critic
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call search_corpus from your client
- Claude Code Bloody Hopes Historical Critic search_corpus run in your project directory
- Claude Desktop Bloody Hopes Historical Critic search_corpus ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Bloody Hopes Historical Critic search_corpus ~/.cursor/mcp.json
- VS Code Bloody Hopes Historical Critic search_corpus .vscode/mcp.json
- Zed Bloody Hopes Historical Critic search_corpus ~/.config/zed/settings.json
- Windsurf Bloody Hopes Historical Critic search_corpus ~/.codeium/windsurf/mcp_config.json
- Cline Bloody Hopes Historical Critic search_corpus ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Bloody Hopes Historical Critic search_corpus ~/.gemini/settings.json
- Grok Bloody Hopes Historical Critic search_corpus .mcp.json (in your project root)
- ChatGPT Bloody Hopes Historical Critic search_corpus Settings → Connectors → Advanced → Developer mode
- Claude.ai Bloody Hopes Historical Critic search_corpus Settings → Connectors → Add custom connector
- LangChain Bloody Hopes Historical Critic search_corpus pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http bloodyhopes-campfire https://bloodyhopes.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.