get_portfolio — Rubin Exchange MCP Tool Read-only
get_portfolio
(get portfolio) 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 get_portfolio from your client
- Claude Code Rubin Exchange get_portfolio run in your project directory
- Claude Desktop Rubin Exchange get_portfolio ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Rubin Exchange get_portfolio ~/.cursor/mcp.json
- VS Code Rubin Exchange get_portfolio .vscode/mcp.json
- Zed Rubin Exchange get_portfolio ~/.config/zed/settings.json
- Windsurf Rubin Exchange get_portfolio ~/.codeium/windsurf/mcp_config.json
- Cline Rubin Exchange get_portfolio ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Rubin Exchange get_portfolio ~/.gemini/settings.json
- Grok Rubin Exchange get_portfolio .mcp.json (in your project root)
- ChatGPT Rubin Exchange get_portfolio Settings → Connectors → Advanced → Developer mode
- Claude.ai Rubin Exchange get_portfolio Settings → Connectors → Add custom connector
- LangChain Rubin Exchange get_portfolio 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_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.