deep_research — Data Batonrouge MCP Tool
deep_research
(deep research) is one of 39 tools on the
Data Batonrouge
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call deep_research from your client
- Claude Code Data Batonrouge deep_research run in your project directory
- Claude Desktop Data Batonrouge deep_research ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Data Batonrouge deep_research ~/.cursor/mcp.json
- VS Code Data Batonrouge deep_research .vscode/mcp.json
- Zed Data Batonrouge deep_research ~/.config/zed/settings.json
- Windsurf Data Batonrouge deep_research ~/.codeium/windsurf/mcp_config.json
- Cline Data Batonrouge deep_research ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Data Batonrouge deep_research ~/.gemini/settings.json
- Grok Data Batonrouge deep_research .mcp.json (in your project root)
- ChatGPT Data Batonrouge deep_research Settings → Connectors → Advanced → Developer mode
- Claude.ai Data Batonrouge deep_research Settings → Connectors → Add custom connector
- LangChain Data Batonrouge deep_research pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http data-batonrouge https://gateway.pipeworx.io/data-batonrouge/mcpOther tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- datasets
- query
- metadata
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.