prepare_evidence_request — Batchloom Evidence MCP Tool
prepare_evidence_request
(prepare evidence request) is one of 11 tools on the
Batchloom Evidence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call prepare_evidence_request from your client
- Claude Code Batchloom Evidence prepare_evidence_request run in your project directory
- Claude Desktop Batchloom Evidence prepare_evidence_request ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Batchloom Evidence prepare_evidence_request ~/.cursor/mcp.json
- VS Code Batchloom Evidence prepare_evidence_request .vscode/mcp.json
- Zed Batchloom Evidence prepare_evidence_request ~/.config/zed/settings.json
- Windsurf Batchloom Evidence prepare_evidence_request ~/.codeium/windsurf/mcp_config.json
- Cline Batchloom Evidence prepare_evidence_request ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Batchloom Evidence prepare_evidence_request ~/.gemini/settings.json
- Grok Batchloom Evidence prepare_evidence_request .mcp.json (in your project root)
- ChatGPT Batchloom Evidence prepare_evidence_request Settings → Connectors → Advanced → Developer mode
- Claude.ai Batchloom Evidence prepare_evidence_request Settings → Connectors → Add custom connector
- LangChain Batchloom Evidence prepare_evidence_request pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http evidence https://batchloom-studio-0913.xuikatwsicrdsidm.chatgpt.site/v1/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.