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