bet_research — Arcgis Kingston MCP Tool
bet_research
(bet research) is one of 39 tools on the
Arcgis Kingston
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call bet_research from your client
- Claude Code Arcgis Kingston bet_research run in your project directory
- Claude Desktop Arcgis Kingston bet_research ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Arcgis Kingston bet_research ~/.cursor/mcp.json
- VS Code Arcgis Kingston bet_research .vscode/mcp.json
- Zed Arcgis Kingston bet_research ~/.config/zed/settings.json
- Windsurf Arcgis Kingston bet_research ~/.codeium/windsurf/mcp_config.json
- Cline Arcgis Kingston bet_research ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Arcgis Kingston bet_research ~/.gemini/settings.json
- Grok Arcgis Kingston bet_research .mcp.json (in your project root)
- ChatGPT Arcgis Kingston bet_research Settings → Connectors → Advanced → Developer mode
- Claude.ai Arcgis Kingston bet_research Settings → Connectors → Add custom connector
- LangChain Arcgis Kingston bet_research pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http arcgis-kingston https://gateway.pipeworx.io/arcgis-kingston/mcp
Other tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- scan_dependency
- 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
- search_datasets
- query_layer
- layer_info
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.