Aave MCP: lending markets and wallet health in a chat

Connect Aave's 56 tools to your AI app

1. 1Click Connect Aave free. There's no sign-in, so its tools are ready at once.
2. 2Lookups like `get_reserve_details` and `get_interest_rate_model` only read data. Aave's server can also prepare transactions; if you want answers and nothing more, switch those tools off before anyone connects an AI app.
3. 3Add ContextGate to your AI app as a connector or MCP server. The steps for each app are on the Works with page.
4. 4Ask your AI app how a wallet's health factor has moved on Aave V4 this month, then open Activity to see the `get_user_summary_history` call.

Questions Aave's tools can answer

• Pull rates, caps, risk parameters and token addresses for one reserve with `get_reserve_details`.
• See the borrow and supply APY at each level of utilization for a V4 hub asset with `get_interest_rate_model`.
• Find out which wallets supply or borrow most of a V4 reserve with `get_reserve_holders`.
• Check V3 eMode categories, where correlated assets such as stablecoins borrow against each other at a higher LTV, with `get_emode_categories`.

These are 4 of Aave's 56 tools; ContextGate lists every one when you add the connection.

Guarding transaction preparation

• Switch off the transaction-preparation tools and keep the read-only market and wallet tools.
• A policy can warn or block before any transaction-preparation call goes through.
• Every Aave call from your team's AI apps is kept in Activity.

What you get with Aave and ContextGate

• Your AI apps can use AaveClaude, Cursor, ChatGPT and other AI apps reach Aave through the one ContextGate connection you add to them.
• You choose which tools they can useSwitch off any Aave tool you don't want used. It's hidden from your AI apps and refused if called.
• Every call is checked and recordedYour policies check each call (for example, personal data is hidden and secrets are blocked), and Activity keeps a record of it.

ContextGate sees only the tool calls that go through it, not your AI app's built-in tools or your chats.

Aave tools

Examples of what your AI apps can do in Aave. You'll see the exact list of tools after you connect it.

• get_chainsList chains Aave supports, on v3, v4, or both. A chain carrying 'notServed': true is one this API holds no market on: every market, position and rewards read co
• get_marketsList Aave markets/reserves (symbol, APY, caps, liquidity) on v3, v4, or both. Chain coverage: omit chainId and every response states the chains it read as 'chai
• get_emode_categoriesv3 only. eMode groups correlated assets (ETH-correlated, stablecoins) so they borrow against each other at a higher LTV, raising borrowing power at the cost of
• get_user_positionsA wallet's Aave positions (supplies and borrows) on v3, v4, or both. Omit chainId and both versions cover every chain they serve, stating which under 'chainsCov
• get_position_itemsv4 only. The individual supplies or borrows inside one v4 spoke: principal, accrued interest and what is withdrawable right now, per item, which the per-spoke a
• get_user_summaryA wallet's aggregate position and health factor. Omit chainId and both versions cover every chain they serve, stating which under 'chainsCovered'; there is no n
• get_transaction_processedv4 only. After sending a transaction, ask whether the Aave API has processed it. Use this instead of sleeping or polling an RPC: the API lags the chain, and pre
• get_reserve_detailsDeep detail for a single reserve (rates, caps, risk parameters, utilisation, the interest-rate curve, token addresses) on v3 or v4. Every rate and percentage is
• get_apy_historyHistorical supply or borrow APY for a reserve over time, on v3 or v4. Returns a time-series of {date, apyPct}, where apyPct is a percent ('3.32' means 3.32%). E
• get_user_activityA wallet's Aave transaction history (supply, borrow, repay, withdraw, collateral changes) on v3, v4, or both. Most recent first. v4 covers every chain; v3 reads
• get_protocol_historyv4 only. Aave v4 protocol-wide history: market size, total borrows and available liquidity per sample over a window. Omit chainId to cover every supported v4 ch
• get_user_summary_historyv4 only. How one wallet's net worth, supplied, debt and health factor moved over a window on Aave v4. Use it to answer 'how has my position changed' or to see h
• get_hubsv4 only. Aave v4 hubs: a hub holds the liquidity and global accounting that user-facing spokes draw from. Returns each hub's hubId, address, chain and totals. P
• get_hub_assetsv4 only. The assets held by one Aave v4 hub, with hub-wide supplied and borrowed totals, rates and utilisation. Get hubId from get_hubs (or the hubAddress on ge
• get_market_historyv4 only. Deposits, borrows, available liquidity and utilisation over a window, for one hub or one spoke. Pick the layer deliberately: a hub is the liquidity its
• get_asset_historyv4 only. One asset across every v4 reserve that holds it: 'price' is its oracle price per sample, 'supply' and 'borrow' are the amounts plus the APY spread acro
• get_reserve_holdersv4 only. The biggest wallets supplying or borrowing one v4 reserve, largest first, for questions about concentration: whether one address is most of a reserve's
• get_interest_rate_modelv4 only. The rate curve for one hub asset: borrow and supply APY at each level of utilisation, as points along the curve the protocol actually uses. This explai
• get_wallet_balancesv4 only. The tokens a wallet actually holds that v4 can take, per token and summed across chains, with 'perChain' saying where each sits, plus the best supply A
• get_risk_premiumv4 only. The per-collateral breakdown of one position's risk premium: how much of the position each token is, and the weight the protocol charges for it. 'curre