The October 9 announcement connects Aave’s transaction tools to MetaMask Agent Wallet. Developers can build agents that monitor lending markets and act within wallet permissions.
Aave announced on October 9 that developers can connect its Model Context Protocol (MCP) server to MetaMask Agent Wallet. The integration lets AI agents retrieve data from Aave’s lending markets and prepare transactions for the wallet to sign and submit onchain.
Aave described the division of work in its official post: “The Aave MCP prepares Aave actions, and the Agent Wallet signs and submits them.” The announcement did not disclose transaction volume, user numbers or a yield delivered by the integration.
Aave’s October 9, 2026 integration announcement
The post loads from X when you open it.
Aave prepares the transaction; the wallet signs
MCP is a protocol that connects AI applications to external data and tools. According to Aave’s documentation, the service can query V3 and V4 markets through one connection. Agents can inspect interest rates, available liquidity, wallet debt and collateral, then prepare supply, borrow, withdrawal and repayment transactions.
The documented process starts by finding a market and inspecting the position. A simulation then shows the proposed action’s effects, including the resulting health factor. That measure tracks a borrowing position’s collateral against its liquidation risk. Once a transaction request is built, signing and submission move to the wallet.
An agent could, for example, compare USDC supply rates across Aave markets and prepare a deposit into a selected market. Asking that question does not itself move the user’s assets. Aave MCP neither holds private keys nor signs transactions; the requests it prepares are returned unsigned.
What is new: Aave MCP did not launch this week. Aave Labs’s introductory post is dated September 8. The October 9 announcement concerns connecting those tools to MetaMask Agent Wallet.
Permissions are set in the wallet
MetaMask’s October 8 setup guide offers Guard Mode and Beast Mode for server-wallet users. Guard Mode applies protocol allowlists and a rolling 24-hour outflow limit. Actions outside those rules wait for two-factor user approval.
Beast Mode has fewer restrictions, but the guide says threat scanning remains active and transactions flagged as malicious still require approval. Wallet signing therefore does not mean a person must manually approve every individual action. The selected mode and permissions define what the agent can do.
Threat scanning is unavailable on some networks. MetaMask’s supported-chains list identifies which networks have Transaction Shield coverage.
Aave’s September 8 MCP introduction describes an agent that prepares repayment of USDC debt when a position’s health factor falls below a chosen level. This is an example of a workflow developers can build. The October 9 announcement did not introduce a separate service guaranteed to prevent liquidation.
The linked official MetaMask video was published on September 14, 2026. It covers Agent Wallet setup, permissions and funding; it is background material rather than an announcement of the Aave integration.
