trial_evidence — Batchloom Evidence MCP Tool
trial_evidence
(trial evidence) 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 trial_evidence from your client
- Claude Code Batchloom Evidence trial_evidence run in your project directory
- Claude Desktop Batchloom Evidence trial_evidence ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Batchloom Evidence trial_evidence ~/.cursor/mcp.json
- VS Code Batchloom Evidence trial_evidence .vscode/mcp.json
- Zed Batchloom Evidence trial_evidence ~/.config/zed/settings.json
- Windsurf Batchloom Evidence trial_evidence ~/.codeium/windsurf/mcp_config.json
- Cline Batchloom Evidence trial_evidence ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Batchloom Evidence trial_evidence ~/.gemini/settings.json
- Grok Batchloom Evidence trial_evidence .mcp.json (in your project root)
- ChatGPT Batchloom Evidence trial_evidence Settings → Connectors → Advanced → Developer mode
- Claude.ai Batchloom Evidence trial_evidence Settings → Connectors → Add custom connector
- LangChain Batchloom Evidence trial_evidence 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.