Back to collectionAave MCP Connects to MetaMask Agent Wallet
Aave says builders can connect its MCP server to MetaMask Agent Wallet so the server prepares protocol actions and the wallet signs and submits them.
Aave announced on October 9 that builders can connect the Aave MCP server to MetaMask Agent Wallet. In the described workflow, Aave MCP reads protocol data, simulates supported actions and prepares transactions; the agent wallet remains the signing and submission layer. The announcement identifies a working connection path, but does not report usage, assets managed or operating results.
Aave’s documentation says its MCP interface covers V3 and V4 market and position data and can prepare supply, borrow, withdraw, repay, collateral and other actions. Prepared transactions remain unsigned, and Aave says the MCP server holds no private keys. That separation limits the server’s authority, but it does not remove protocol, wallet-policy or agent-configuration risk; each action still depends on the wallet’s authorization and the user-defined controls around it.