get_pool — Ekubo Protocol MCP Tool Read-only
get_pool
(get pool) is one of 99 tools on the
Ekubo Protocol
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_pool from your client
- Claude Code Ekubo Protocol get_pool run in your project directory
- Claude Desktop Ekubo Protocol get_pool ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Ekubo Protocol get_pool ~/.cursor/mcp.json
- VS Code Ekubo Protocol get_pool .vscode/mcp.json
- Zed Ekubo Protocol get_pool ~/.config/zed/settings.json
- Windsurf Ekubo Protocol get_pool ~/.codeium/windsurf/mcp_config.json
- Cline Ekubo Protocol get_pool ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Ekubo Protocol get_pool ~/.gemini/settings.json
- Grok Ekubo Protocol get_pool .mcp.json (in your project root)
- ChatGPT Ekubo Protocol get_pool Settings → Connectors → Advanced → Developer mode
- Claude.ai Ekubo Protocol get_pool Settings → Connectors → Add custom connector
- LangChain Ekubo Protocol get_pool pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http ekubo https://mcp.ekubo.org/mcpOther tools on this server
- list_tokens
- export_tokens
- get_token
- get_tokens
- get_quotes_with_plans
- get_value_transfer_status
- prepare_ve33_vote
- prepare_ve33_extend
- prepare_ve33_stake
- prepare_ve33_split
- prepare_ve33_claim_fees
- prepare_ve33_reinvest
- prepare_ve33_claim_all_fees
- prepare_ve33_clear_vote
- get_ve33_allocations
- get_stonx_allocation_recommendation
- prepare_ve33_reallocation
- get_positions_by_owner
- get_pool_liquidity
- list_pool_keys
- derive_pool_id
- decode_pool_config
- get_position
- get_position_pool_candidates
- prepare_lp_position_deposit
- prepare_lp_position_earnings_claim
- prepare_lp_position_withdraw
- prepare_wrap_unwrap
- prepare_transfers
- prepare_lp_position_transfer
- prepare_fix_pool_price
- prepare_twamm_order
- prepare_twamm_order_collection
- prepare_twamm_order_stop
- prepare_twamm_virtual_orders
- prepare_auction_create
- prepare_auction_complete
- prepare_auction_creator_proceeds
- prepare_manual_pool_boost
- prepare_oracle_capacity_expansion
- prepare_approval_revocations
- get_rewards_claims_by_owner
- prepare_rewards_claim
- prepare_revenue_buybacks
- prepare_ve33_increase_stake
- prepare_ve33_merge
- prepare_ve33_withdraw
- get_liquidity_opportunities
- prepare_pool_initialization
- get_aave_v3_markets
- prepare_aave_v3_supply
- prepare_aave_v3_withdraw
- prepare_aave_v3_borrow
- prepare_aave_v3_repay
- prepare_aave_v3_collateral
- prepare_aave_v3_emode
- get_morpho_vaults
- prepare_morpho_vault_deposit
- prepare_morpho_vault_withdraw
- prepare_morpho_vault_redeem
- get_sky_savings_deployment
- prepare_sky_savings_deposit
- prepare_sky_savings_withdraw
- prepare_sky_savings_redeem
- get_merkl_deployment
- prepare_merkl_claim
- get_aerodrome_deployment
- prepare_aerodrome_sugar_reads
- prepare_aerodrome_liquidity_deposit
- prepare_aerodrome_liquidity_withdraw
- prepare_aerodrome_gauge_deposit
- prepare_aerodrome_gauge_withdraw
- prepare_aerodrome_gauge_claim
- prepare_aerodrome_lock
- prepare_aerodrome_vote
- prepare_aerodrome_incentive_claim
- decode_uniswap_v4_position_info
- quote_uniswap_liquidity
- get_uniswap_deployments
- discover_uniswap_pools
- get_uniswap_pool
- get_uniswap_pool_ticks
- get_uniswap_charts
- prepare_uniswap_reads
- prepare_uniswap_v2_add_liquidity
- prepare_uniswap_v2_remove_liquidity
- prepare_uniswap_v3_add_liquidity
- prepare_uniswap_v3_remove_liquidity
- prepare_uniswap_v3_collect_fees
- prepare_uniswap_v4_add_liquidity
- prepare_uniswap_v4_remove_liquidity
- prepare_uniswap_v4_collect_fees
- get_lido_deployment
- prepare_lido_stake
- prepare_lido_wrap
- prepare_lido_unwrap
- prepare_lido_withdrawal_request
- prepare_lido_withdrawal_claim
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 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.