Skip to content
Aave MCP

Aave MCP

by Aave
Released
v1.0.0
BUSL-1.1
Repository Docs npm
Featured Payments & Commerce

Summary

Aave's official MCP server: live V3 and V4 markets, wallet positions and health factor, DAO governance, and unsigned transactions your own wallet signs.

Features

  • Aave V3 and V4 from one endpoint via a version argument
  • Wallet positions, net APY and the correct V4 health factor
  • Unsigned transaction and EIP-712 builders — the server never holds keys
  • preview_action simulates the resulting health factor before you build
  • Swap quoting and signed-order relay
  • DAO governance: proposals, quorum and voter history

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Aave MCP" tools will be available.
{
  "mcpServers": {
    "aave-mcp": {
      "command": "https://mcp.aave.com"
    }
  }
}

Description

The official Model Context Protocol server for Aave, published by Aave itself and reachable at https://mcp.aave.com over streamable HTTP. It answers questions about both Aave V3 and V4 through one endpoint — most reads take a version argument of v3, v4 or all, so a single connection can compare the two.

Authoritative, not reimplemented

It wraps the official @aave/client SDK, so numbers match app.aave.com (V3) and pro.aave.com (V4) — including V4-specific concepts like hub/spoke accounting, risk premium and the correct health-factor calculation. Third-party Aave servers that reimplement the maths get V4 wrong; this is the reason to prefer the first-party one.

Non-custodial by design

Read tools return data. prepare_* tools return an unsigned transaction or EIP-712 payload for the user's own wallet to sign. The server never holds keys and never submits anything on your behalf. preview_action simulates a supply, borrow, withdraw or repay and reports the resulting health factor before anything is built.

What it exposes

Around 25 tools: get_chains, get_markets (with a symbols filter), get_reserve_details, get_apy_history, get_protocol_history, get_hubs/get_hub_assets, get_user_positions, get_position_items, get_user_summary and get_user_summary_history, get_user_activity, get_user_rewards; the prepare_action, prepare_set_collateral, prepare_set_emode, prepare_liquidation and prepare_claim_rewards builders; swap quoting and order flow (get_swappable_tokens, get_swap_quote, prepare_order, submit_signed_order, prepare_cancel_order); plus get_transaction_processed to poll for confirmation instead of sleeping, and governance reads for proposals, quorum and voters.

Written for models, not for humans

Responses are compact and predictable — { data, next_actions } with typed structuredContent. Reserve detail is projected from roughly 17 KB of raw SDK payload down to about 1 KB, and asking about one asset does not return all ~70 reserves on a chain. Rejections come back verbatim and flagged non-retryable, so the model corrects its arguments instead of looping on a generic error. Amounts are in main units (10.5, never wei) and every rate carries a Pct suffix rounded to four decimal places.

Published to npm as @aave/mcp under a BUSL licence.

Covered in the Weekly

Related MCP Servers

MCP: Stripe

by Stripe

Stripe's official MCP server — manage customers, products, prices, payment links, invoices, and more via the Stripe API.

Payments & Commerce

MCP: CoinMarketCap MCP

by CoinMarketCap

CoinMarketCap's official MCP server — real-time prices and market caps for 10,000+ cryptocurrencies, technical indicators, on-chain metrics and crypto news.

Databases & Data

MCP: Binance

by Binance

Binance's official MCP server, part of Agent OS — spot and futures trading, live market data and account access, with per-agent permissions and funding limits.

Payments & Commerce
Browse all MCP servers →