list_markets — Rubin Exchange MCP Tool Read-only
list_markets
(list markets) 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 list_markets from your client
- Claude Code Rubin Exchange list_markets run in your project directory
- Claude Desktop Rubin Exchange list_markets ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Rubin Exchange list_markets ~/.cursor/mcp.json
- VS Code Rubin Exchange list_markets .vscode/mcp.json
- Zed Rubin Exchange list_markets ~/.config/zed/settings.json
- Windsurf Rubin Exchange list_markets ~/.codeium/windsurf/mcp_config.json
- Cline Rubin Exchange list_markets ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Rubin Exchange list_markets ~/.gemini/settings.json
- Grok Rubin Exchange list_markets .mcp.json (in your project root)
- ChatGPT Rubin Exchange list_markets Settings → Connectors → Advanced → Developer mode
- Claude.ai Rubin Exchange list_markets Settings → Connectors → Add custom connector
- LangChain Rubin Exchange list_markets pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http exchange https://mcp.mainnet.rubin.trade/mcp
Other tools on this server
- whoami
- get_block_height
- 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
- batch_cancel
- 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.