Key Highlights
- Aave announced that developers can connect its Model Context Protocol (MCP) server to MetaMask Agent Wallet.
- Aave founder Stani Kulechov and MetaMask confirmed the integration in separate posts on X.
- AI agents can prepare lending and other DeFi transactions, while the wallet handles authorization and submission.
Aave has connected its Model Context Protocol (MCP) server to MetaMask Agent Wallet, letting developers connect AI agents to Aave’s lending markets.
In an October 9 post on X, Aave said its MCP server prepares transactions, while MetaMask Agent Wallet handles wallet-side authorization and submission. Aave founder Stani Kulechov and MetaMask separately confirmed the integration.
Aave founder confirms the integration
Kulechov confirmed the connection in a post on X:
“MetaMask Agent Wallet now supports Aave MCP, expanding the reach of Agentic Aave.”
The post confirmed support for Aave MCP within MetaMask Agent Wallet but did not provide further technical details about the integration.
Aave launched MCP server in September
On September 9, Aave had launched its official MCP server to let AI assistants retrieve protocol data and prepare DeFi transactions.
Aave said transactions generated through the server are returned unsigned and that the server does not hold private keys. The connected wallet remains responsible for authorizing and signing transactions.
The MetaMask connection builds on that release by linking Aave’s transaction-preparation tools to a wallet that supports AI-agent transactions.
How the integration works
Aave MCP lets compatible AI assistants retrieve market data and prepare transactions. Its tools support supplying assets, borrowing, withdrawing, repaying loans, managing collateral and preparing token swaps. Agents can also check wallet positions, interest rates and health factors.
An agent could compare USDC supply rates across Aave markets and prepare a deposit transaction for the wallet to authorize.
Aave’s server returns unsigned transactions or typed data for wallet authorization. It does not hold private keys or sign transactions itself.
Aave MCP supports V3 and V4
Aave’s MCP server is available through the public endpoint https://mcp.aave.com. According to Aave’s documentation, developers can connect compatible AI assistants without an API key or separate signup.
The server provides access to Aave V3 and V4 data and transaction-building tools. The MetaMask connection allows the wallet to authorize and submit supported transactions prepared through these tools.
MetaMask provides transaction checks and spending controls
MetaMask describes Agent Wallet as a self-custodial wallet that allows AI agents to operate within user-defined rules. Users can set spending limits, restrict which protocols an agent can access and choose between Guard Mode and Beast Mode.
Supported EVM transactions can use MetaMask’s broader security features, including:
- Transaction simulation: Estimates a transaction’s expected effects.
- Threat scanning: Uses Blockaid-powered checks to identify potentially malicious activity.
- MEV protection: Helps protect supported transactions against certain forms of transaction reordering and value extraction.
These are broader MetaMask wallet features, not protections introduced specifically by the Aave integration. They do not eliminate risks associated with smart-contract vulnerabilities or incorrectly prepared transactions.
Aave’s recent focus on DeFi regulation
The integration follows Aave’s recent engagement with European policymakers over decentralized finance and stablecoin regulation.
On October 2, Aave founder Stani Kulechov questioned positions taken by the European Central Bank and European Banking Authority on stablecoin remuneration and DeFi access. A separate report covered Aave Labs’ response to the European Commission’s MiCA review, which called for rules that distinguish decentralized protocols from financial intermediaries.
Those regulatory discussions are separate from the MetaMask integration, which focuses on connecting AI agents with Aave’s existing DeFi tools.
Integration details remain limited
Aave and MetaMask have confirmed the integration, but their announcements do not detail how developers can configure permissions or borrowing limits for individual agents.
The connection lets AI agents prepare Aave transactions while the wallet handles authorization and submission. Users and developers still need to account for the risks associated with DeFi transactions.
Also Read: Blockchain.com Seeks CFTC Nod for Prediction Markets
