polymarket_kalshi_spread — Bts MCP Tool
polymarket_kalshi_spread
(polymarket kalshi spread) is one of 39 tools on the
Bts
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call polymarket_kalshi_spread from your client
- Claude Code Bts polymarket_kalshi_spread run in your project directory
- Claude Desktop Bts polymarket_kalshi_spread ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Bts polymarket_kalshi_spread ~/.cursor/mcp.json
- VS Code Bts polymarket_kalshi_spread .vscode/mcp.json
- Zed Bts polymarket_kalshi_spread ~/.config/zed/settings.json
- Windsurf Bts polymarket_kalshi_spread ~/.codeium/windsurf/mcp_config.json
- Cline Bts polymarket_kalshi_spread ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Bts polymarket_kalshi_spread ~/.gemini/settings.json
- Grok Bts polymarket_kalshi_spread .mcp.json (in your project root)
- ChatGPT Bts polymarket_kalshi_spread Settings → Connectors → Advanced → Developer mode
- Claude.ai Bts polymarket_kalshi_spread Settings → Connectors → Add custom connector
- LangChain Bts polymarket_kalshi_spread pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http bts https://gateway.pipeworx.io/bts/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
- bet_research
- polymarket_arbitrage
- polymarket_edges
- 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
- dataset_columns
- query_dataset
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.