batch_cancel — Rubin Exchange MCP Tool
batch_cancel
(batch cancel) is one of 33 tools on the
Rubin Exchange
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call batch_cancel from your client
- Claude Code Rubin Exchange batch_cancel run in your project directory
- Claude Desktop Rubin Exchange batch_cancel ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Rubin Exchange batch_cancel ~/.cursor/mcp.json
- VS Code Rubin Exchange batch_cancel .vscode/mcp.json
- Zed Rubin Exchange batch_cancel ~/.config/zed/settings.json
- Windsurf Rubin Exchange batch_cancel ~/.codeium/windsurf/mcp_config.json
- Cline Rubin Exchange batch_cancel ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Rubin Exchange batch_cancel ~/.gemini/settings.json
- Grok Rubin Exchange batch_cancel .mcp.json (in your project root)
- ChatGPT Rubin Exchange batch_cancel Settings → Connectors → Advanced → Developer mode
- Claude.ai Rubin Exchange batch_cancel Settings → Connectors → Add custom connector
- LangChain Rubin Exchange batch_cancel pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http exchange https://mcp.mainnet.rubin.trade/mcpOther tools on this server
- whoami
- get_block_height
- list_markets
- get_market
- get_orderbook
- get_candles
- get_candles_multi
- get_balance
- get_equity
- get_positions
- get_open_orders
- get_portfolio
- get_position_risk
- get_fills
- get_pnl
- get_funding_status
- deposit_to_subaccount
- top_up_gas
- place_limit_order
- place_market_order
- cancel_order
- cancel_all_orders
- place_stop_loss
- place_take_profit
- close_position
- close_all_positions
- open_position
- get_news
- get_leaderboard
- get_my_rank
- get_fee_tier
- get_referral_program
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.