bridge_prepare_payment — Liquid Agent MCP Tool
bridge_prepare_payment
(bridge prepare payment) is one of 24 tools on the
Liquid Agent
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call bridge_prepare_payment from your client
- Claude Code Liquid Agent bridge_prepare_payment run in your project directory
- Claude Desktop Liquid Agent bridge_prepare_payment ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Liquid Agent bridge_prepare_payment ~/.cursor/mcp.json
- VS Code Liquid Agent bridge_prepare_payment .vscode/mcp.json
- Zed Liquid Agent bridge_prepare_payment ~/.config/zed/settings.json
- Windsurf Liquid Agent bridge_prepare_payment ~/.codeium/windsurf/mcp_config.json
- Cline Liquid Agent bridge_prepare_payment ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Liquid Agent bridge_prepare_payment ~/.gemini/settings.json
- Grok Liquid Agent bridge_prepare_payment .mcp.json (in your project root)
- ChatGPT Liquid Agent bridge_prepare_payment Settings → Connectors → Advanced → Developer mode
- Claude.ai Liquid Agent bridge_prepare_payment Settings → Connectors → Add custom connector
- LangChain Liquid Agent bridge_prepare_payment pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http liquid-agent https://api.liquidagent.ai/mcpOther tools on this server
- bridge_quote
- bridge_routes
- bridge_status
- bridge_referral_earnings
- stocks_basket
- stocks_buy_quote
- stocks_vault
- stocks_portfolio
- stocks_create_vault
- stocks_set_weights
- stocks_buy
- stocks_sell
- stocks_rebalance
- stocks_send
- stocks_signals_prepare
- polymarket_prepare
- stocks_publish_prepare
- usdc_balances
- cctp_status
- x402_check
- payment_readiness
- gas_sponsor_info
- liquid_guide
This list was read from the server itself, by connecting to it and calling tools/list on 29 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.