Skip to Content
docs

Get Started with Aave MCP

Aave MCP is a remote server, so there is nothing to install and no key to manage. Point a client at https://mcp.aave.com and the tools appear in the next session.

Connect a Client

claude mcp add --transport http aave https://mcp.aave.com

Your First Questions

Ask in plain language. None of these need a chain or a market named first.

Read a wallet, or the protocol:

  • “What does wallet 0x… hold on Aave?”
  • “Am I net earning or net paying on this position?”
  • “Which Aave governance proposals are open for voting, and has each one met quorum?”

Compare venues, rates and history:

  • “Where can I earn the most on stablecoins across Aave right now? Tell me what you ruled out and why.”
  • “I have 10,000 GHO idle. sGHO, or supply it to a market?”
  • “Has USDC’s supply rate on Ethereum been stable this year?”

Simulate against the position, which commits nothing:

  • “What is the health factor of 0x… and how far can BTC fall before liquidation?”
  • “Review what 0x… holds on Aave V4, then simulate borrowing another 5,000 USDC and show the health factor before and after.”
  • “Explain E-Mode, and tell me whether it would help my position.”
  • “Quote 2x leveraged WETH funded by USDC debt on Aave V4, and show the health factor it would leave.”

Build a transaction to sign:

  • “Prepare a borrow of 1,000 USDC for 0x… on Aave V4.”
  • “Repay all of my USDC debt.”
  • “Swap 1 ETH for USDC and show me what it actually costs.”
  • “Pay down my USDC debt on Aave V4 from my WETH collateral in one step, without withdrawing it.”

Reads answer with live protocol data. Actions come back as an unsigned transaction for the user to sign in their own wallet.

Prompts and Guides

Clients that surface MCP prompts get five ready-made workflows: check_health, best_stablecoin_yield, prepare_supply, gho_savings, and review_position. Their arguments support completion, so a client can offer values as the user types.

The server also carries its own guidance for the model calling it. get_started answers a cold turn where the user has not asked for anything specific, and get_aave_guide serves one topic at a time:

TopicCovers
overviewWhat Aave is and the shape of a typical flow
v3, v4What each version needs in order to act
positions, health-factorThe rules that decide whether an action is possible
risksWhat a passive supplier is exposed to
ids, amounts, signingArgument formats and the execution-plan branches
pricesWhose price every USD figure is, and what follows from that
swaps, leverage, gho, governance, rewardsThe flows that have their own tools
tools, docsThe capability list, and where the protocol documentation lives

Each topic is also readable as an MCP resource at aave://guide/<topic>.

Call the Server Directly

The MCP endpoint is POST /, with /mcp as an alias. A plain GET there returns the server card as JSON, the same document served at /.well-known/mcp/server-card.json. A GET that asks for text/event-stream gets 405, since the server offers no SSE stream. GET /health returns a JSON status.

Terminal
curl -s -X POST https://mcp.aave.com/ -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_user_summary","arguments":{"user":"0x...","version":"v4"}}}'

tools/list on the same endpoint returns every tool with its parameter schema, which is the authority on arguments at any moment.

Protocol Revisions

The server serves the 2026-07-28 revision of the Model Context Protocol and the 2025 revisions. An initialize handshake negotiates a 2025 revision. A client on 2026-07-28 must send the Mcp-Method header, plus Mcp-Name on tools/call, or the request is refused.

Limits

The endpoint needs no key today. It is a shared service, so cache reads where a client can, poll get_transaction_processed and get_order_status at a sensible interval rather than in a tight loop, and handle 401 and 429 responses rather than assuming they cannot occur.

Next Steps