TL;DR
- Aave launched an official MCP server that allows AI assistants to read live data and build transactions.
- The server covers both V3 and V4 versions under a single connection. It offers query tools, transaction construction, and governance.
- All transactions are returned unsigned, and the server holds no keys and cannot move user funds.
Aave Labs officially launched its MCP server, an infrastructure that allows any AI assistant compatible with the Model Context Protocol to read real-time protocol data and build transactions directly, without relying on outdated training data or third-party integrations.
Until now, AI assistants interacting with Aave did so through external wrappers or static information from their training datasets. The new server solves that problem: developers can connect an assistant to the protocol with a single line of code and receive responses based on real data, without needing to maintain their own bindings or re-implement the accounting logic already built into the protocol.
AI tools and agents can now interact with Aave through the official Aave MCP server.
Connect it to Claude, ChatGPT, or any MCP-compatible tool to build agents that can read protocol data, manage positions, and prepare transactions across every Aave deployment. pic.twitter.com/2mq3XBxDnx
— Aave (@aave) September 8, 2026
One Server, Two Versions, No Custodied Keys
The server unifies access to V3 and V4 under a single endpoint. Most tools accept a version argument —v3, v4, or all— and can query both protocols concurrently for direct comparisons. Read capabilities cover markets, reserves, rates, risk parameters, APY time series, transaction history, and the health factor of specific wallets. In V4, positions include health per individual position and Hub-level tools that expose liquidity and Liquidity Hub accounting.
On the security front, Aave was meticulous: every transaction built by the server is returned unsigned. The prepare_ tools return a transaction request or typed EIP-712 data, and signing remains exclusively in the hands of the user’s wallet. The server retains no private keys and has no ability to move funds.
Aave: Compatibility and Maximum Security
The transaction construction tools cover supply, borrow, withdraw, repay, collateral toggles, eMode, rewards claiming, and liquidations. The preview_action tool simulates any action and reports the resulting health factor before executing it. Governance tools are also available to search proposals, query quorum, and list voters by voting power.
The server was built on Aave Kit, meaning the calculations are identical to those used by the protocol’s official interfaces. Responses are optimized for language models: reserve detail is reduced from approximately 17 KB to around 1 KB, and input errors return the exact reason for rejection so the assistant can correct its arguments without blind retries.
The Aave integration is compatible with Claude, ChatGPT, Cursor, VS Code, Windsurf, and Codex CLI, among other clients that support remote streamable HTTP.
