get_bridge_balances — MetaLend MCP Tool Read-only
get_bridge_balances
(get bridge balances) is one of 19 tools on the
MetaLend
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_bridge_balances from your client
- Claude Code MetaLend get_bridge_balances run in your project directory
- Claude Desktop MetaLend get_bridge_balances ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MetaLend get_bridge_balances ~/.cursor/mcp.json
- VS Code MetaLend get_bridge_balances .vscode/mcp.json
- Zed MetaLend get_bridge_balances ~/.config/zed/settings.json
- Windsurf MetaLend get_bridge_balances ~/.codeium/windsurf/mcp_config.json
- Cline MetaLend get_bridge_balances ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MetaLend get_bridge_balances ~/.gemini/settings.json
- Grok MetaLend get_bridge_balances .mcp.json (in your project root)
- ChatGPT MetaLend get_bridge_balances Settings → Connectors → Advanced → Developer mode
- Claude.ai MetaLend get_bridge_balances Settings → Connectors → Add custom connector
- LangChain MetaLend get_bridge_balances pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http metalend https://mcp.metalend.tech/mcpOther tools on this server
- list_pools
- get_balances
- get_config
- get_default_config
- get_rewards
- get_transaction_costs
- get_token_info
- get_withdrawal_version
- get_auth_challenge
- submit_auth_verify
- prepare_deposit
- submit_deposit
- get_deposit_status
- prepare_withdrawal
- submit_withdrawal
- get_withdrawal_status
- prepare_config
- submit_config
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.