Fluid MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLUID_RPC_BASE | No | Custom RPC for Base | |
| FLUID_RPC_POLYGON | No | Custom RPC for Polygon | |
| FLUID_RPC_ARBITRUM | No | Custom RPC for Arbitrum | |
| FLUID_RPC_ETHEREUM | No | Custom RPC for Ethereum |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fluid_get_all_ftokensB | List all fToken (Fluid lending token) addresses on a chain. fTokens are ERC4626-compliant and represent a user's share in the lending pool. |
| fluid_get_ftoken_detailsA | Get detailed information about a specific fToken including name, symbol, underlying asset, supply rate, rewards rate, total assets, and total supply. |
| fluid_get_all_ftokens_detailsA | Get details for ALL fTokens on a chain in a single call — names, rates, TVL, and underlying assets. Perfect for a lending dashboard. |
| fluid_get_user_lending_positionB | Get a user's position in a specific fToken lending pool. Returns fToken shares, underlying asset value, wallet balance, and allowance. |
| fluid_get_user_all_positionsA | Get all of a user's lending positions across all fTokens on a chain. Returns combined fToken details and user position data. |
| fluid_get_previewsA | Get conversion previews for deposit/mint/withdraw/redeem operations on an fToken. Useful for estimating output before transacting. |
| fluid_get_all_vaultsA | List all Fluid vault addresses on a chain. Returns vault addresses and their types (T1, T2, T3, T4). |
| fluid_get_vault_typeA | Get the type of a specific vault (T1, T2, T3, or T4). T1=10000, T2=20000, T3=30000, T4=40000. |
| fluid_get_vault_dataA | Get comprehensive data for a specific Fluid vault: supply/borrow tokens with symbols, rates as APY, human-readable collateral factor, liquidation threshold, LTV limits, total supply/borrow, and availability limits. |
| fluid_get_vault_positionB | Get a specific vault position by its NFT ID. Each Fluid vault position is represented as an NFT. Returns decoded supply (collateral), borrow (debt) in human-readable token amounts, liquidation status, vault config, and rates. |
| fluid_get_user_vault_nft_idsB | Get all vault position NFT IDs owned by a specific user address. |
| fluid_get_vault_by_nftB | Get the vault address and decoded position summary for a specific vault position NFT ID. |
| fluid_get_total_positionsA | Get the total number of vault positions (NFTs) across all vaults on a chain. |
| fluid_build_lending_depositA | Build an unsigned transaction to deposit assets into a Fluid fToken lending pool. Returns the transaction data that must be signed and sent by the agent's wallet. Uses the ERC4626 deposit() method. |
| fluid_build_lending_mintA | Build an unsigned transaction to mint a specific number of fToken shares by depositing underlying assets. |
| fluid_build_lending_withdrawA | Build an unsigned transaction to withdraw underlying assets from a Fluid fToken lending pool. Burns fToken shares in exchange for underlying assets. |
| fluid_build_lending_redeemA | Build an unsigned transaction to redeem fToken shares for underlying assets. Specify how many shares to burn rather than how many assets to receive. |
| fluid_build_lending_deposit_nativeA | Build an unsigned transaction to deposit native ETH into a Fluid fToken lending pool (for ETH-based fTokens). No approval needed. |
| fluid_build_lending_withdraw_nativeA | Build an unsigned transaction to withdraw native ETH from a Fluid fToken lending pool. |
| fluid_build_token_approveA | Build an unsigned transaction to approve an ERC20 token for spending by a Fluid contract (fToken, vault, DEX pool). Required before deposit/supply operations. |
| fluid_build_vault_t1_operateA | Build an unsigned transaction to interact with a Vault T1 (single-asset collateral, single-asset debt). T1 operate function is payable. |
| fluid_build_vault_t2_operateC | Build an unsigned transaction to interact with a Vault T2 (dual-asset collateral, single-asset debt). |
| fluid_build_vault_t3_operateB | Build an unsigned transaction to interact with a Vault T3 (single-asset collateral, dual-asset debt). |
| fluid_build_vault_t4_operateB | Build an unsigned transaction to interact with a Vault T4 (dual-asset collateral, dual-asset debt). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze-lending-rates | Analyze lending rates across all fTokens on a chain to find the best yield opportunities. |
| check-vault-health | Check the health of a specific vault position by NFT ID. |
| find-swap-route | Find the best swap route and estimate output for a token swap on Fluid DEX. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| supported-chains | |
| protocol-overview |
TDQS
Scored across 24 tools
Most tools are cleanly separated by resource and action, but fluid_get_vault_position and fluid_get_vault_by_nft overlap heavily since both resolve a vault position by NFT ID. The get_all_ftokens vs get_all_ftokens_details pair is also easy to confuse even though one returns only addresses.
All tools follow a consistent fluid_ prefix with either get_ or build_ followed by a descriptive noun phrase. Deposit/mint/withdraw/redeem and T1-T4 vault variants follow a clear, predictable pattern with no mixed conventions.
24 tools sits in the borderline heavy 16-25 band. The count is understandable for a server covering both fToken lending and vault operations, but some getters could be consolidated and the native-ETH lending variants add bulk.
The tool surface covers the full core lifecycle for both fToken lending and vaults: reading positions, fetching rates/config, previewing conversions, building approvals, and constructing deposit/mint/withdraw/redeem and vault operate transactions. Common workflows have no obvious dead ends.