Aave has launched an official server letting AI assistants read live protocol data and build transactions. The assistants cannot execute them.
Every transaction the server produces comes back unsigned, as a transaction request or EIP-712 typed data, for the user’s own wallet to sign. Aave Labs states the server holds no keys and cannot move funds.
Aave Labs announced the server on September 8, live at mcp.aave.com, accessible to any AI assistant that supports the Model Context Protocol and coveri ng both V3 and V4 through one connection.
What It Replaces
The stated reason for building it is that assistants were already being used to reach Aave, working from training data or third-party wrappers rather than the protocol itself.
Those wrappers exist in numbers. Independent MCP servers already read Aave V3 and V4 positions across chains, scan health factors, and in some cases run automated yield strategies. None carries the protocol’s own accounting.
Aave’s server is built on Aave Kit, which the company says means results carry the same math as the official Aave interfaces, including Hub and Spoke accounting and Risk Premium. That is the substantive difference between a first-party server and a wrapper: the numbers reconcile with what the protocol’s own front end shows.
What the Server Exposes
Read functions cover chains, markets, and reserves with rates, caps, and risk parameters, plus time-series data for APY, protocol deposits and borrows, and a wallet’s health factor over any window.
Position queries return supplies, borrows, aggregate health, and claimable rewards across supported chains and transaction history. On V4, positions carry per-position health, and Hub-level tools expose liquidity and accounting at the Liquidity Hub.
Transaction building covers supply, borrow, withdraw, repay, collateral toggles, eMode, rewards claims, and liquidations. A preview tool simulates any action and reports the resulting health factor before anything is prepared. Swaps run through quote, prepare, submit, and status tools, and governance tools search proposals, return quorum status, and list voters by voting power.
Most tools take a version argument of v3, v4, or all, with the last fetching both concurrently for comparison.
The Agent Example
The use case Aave puts forward is a liquidation-protection loop. An agent is told to repay USDC debt whenever the health factor drops below 1.5, monitors the position, prepares the repayment when the threshold is hit, and waits for a signature.
That pattern—read a position, simulate an action, prepare a transaction—is what the company says is enough to build such a tool without a custom integration. The signature requirement is what separates it from an agent with spending authority.
Aave also says responses are trimmed to the fields a model needs, taking reserve detail from roughly 17 KB to roughly 1 KB, and that rejected inputs return the reason verbatim so an assistant corrects its arguments rather than retrying.
Setup and Context
The server connects by adding the URL as a custom connector in Claude or ChatGPT or through a single command in Claude Code. Aave lists Cursor, VS Code, Windsurf, and Codex CLI as supporting the URL alone. Skills are published on GitHub and documented at aave.com/docs/mcp.
The launch follows a period of expansion for V4. Aave deployed it on Avalanche in July, its first network beyond Ethereum, introducing the Hub-and-Spoke architecture the MCP server’s V4 tools now expose. The protocol has also proposed a standardized technical framework for asset listings across V3, V4, and Horizon.
One claim in the announcement is not evidenced. Aave says a growing number of people reach the protocol through an assistant rather than a front end, which is the premise for building the server, but publishes no figures for it.
