graph-aave-mcp
MCP server for querying
Exposes 14 tools and 5 guided prompts that any AI agent (Claude, Cursor, Copilot, etc.) can use to query lending markets, user positions, health factors, liquidations, flash loans, rate history, and AAVE governance — across 7 chains (Ethereum, Base, Arbitrum, Polygon, Optimism, Avalanche, Fantom) via 11 subgraphs covering both V2 and V3 deployments plus AAVE Governance V3.
Published to the MCP Registry as
io.github.PaulieB14/graph-aave-mcp
Supported Chains & Subgraphs
7 chains, 11 subgraphs — some chains have both V2 (legacy) and V3 deployments tracked separately.
Chain | Version | Deployment ID |
Ethereum | V3 |
|
Ethereum | V2 |
|
Base | V3 |
|
Arbitrum | V3 |
|
Polygon | V3 |
|
Polygon | V2 |
|
Optimism | V3 |
|
Avalanche | V3 |
|
Avalanche | V2 |
|
Ethereum | Governance V3 |
|
Fantom | V3 |
|
Prerequisites
You need a free Graph API key (takes ~2 minutes):
Go to The Graph Studio
Connect your wallet (MetaMask, WalletConnect, etc.)
Click "API Keys" in the sidebar and create one
Free tier includes 100,000 queries/month
Installation
npm install -g graph-aave-mcpOr use directly with npx (no install needed):
GRAPH_API_KEY=your-key npx graph-aave-mcpConfiguration
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"graph-aave": {
"command": "npx",
"args": ["-y", "graph-aave-mcp"],
"env": {
"GRAPH_API_KEY": "your-api-key-here"
}
}
}
}Claude Code (CLI)
claude mcp add graph-aave -- npx -y graph-aave-mcpThen set the environment variable:
export GRAPH_API_KEY=your-api-key-hereCursor
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"graph-aave": {
"command": "npx",
"args": ["-y", "graph-aave-mcp"],
"env": {
"GRAPH_API_KEY": "your-api-key-here"
}
}
}
}Other MCP Clients
Use stdio transport with npx graph-aave-mcp as the command and GRAPH_API_KEY as an environment variable.
Available Tools
Discovery
Tool | Description |
| List all supported AAVE chains with subgraph IDs, versions, and 30-day query volumes |
| Full GraphQL schema introspection for any chain's subgraph |
Lending Markets
Tool | Description |
| All active lending markets on a chain — TVL, supply APY, borrow APY, LTV, liquidation thresholds |
| Deep detail on one asset: lifetime stats, full config, token addresses |
| Historical snapshots of APY, utilization rate, and TVL over time |
User Positions
Tool | Description |
| Wallet's supplied assets, borrowed assets, collateral flags, and e-mode category |
| Simulate how a price change affects a user's health factor — e.g. "ETH drops 20%" |
Protocol Events
Tool | Description |
| Recent borrow events — filterable by user address or asset symbol |
| Recent supply/deposit events (handles V2 |
| Recent liquidations — filterable by liquidated user or liquidator address |
| Recent flash loans with amounts and fees paid |
Governance
Tool | Description |
| AAVE Governance V3 proposals with titles, states, for/against vote counts |
| Individual voter breakdown for a specific proposal by voting power |
Advanced
Tool | Description |
| Raw GraphQL escape hatch — execute any query against any chain |
Guided Prompts
Prompts are pre-built multi-step workflows that guide any AI agent through common AAVE analysis tasks:
Prompt | Description |
| Full wallet analysis: supplied/borrowed assets, health factor, liquidation risk |
| Protocol overview for a chain: top markets, rates, recent activity |
| Compare supply/borrow APY for one asset across all supported chains |
| Analyze liquidation patterns, top liquidators, and at-risk markets |
| Recent governance proposals, voting results, and active decisions |
Rate Conversion
AAVE stores interest rates in RAY units (27 decimal precision). To convert to human-readable APY:
Supply APY % = liquidityRate / 1e27 * 100
Borrow APY % = variableBorrowRate / 1e27 * 100Token amounts are stored in native token units. To convert:
Human amount = rawAmount / 10^decimalsHealth Factor
A user's health factor determines liquidation risk:
HF = Σ(collateral_i × price_i × liquidationThreshold_i) / Σ(debt_i × price_i)HF > 1.0 — position is safe
HF = 1.0 — liquidation threshold reached
HF < 1.0 — position is liquidatable
Use simulate_health_factor to test how price movements affect a specific wallet's HF.
Example Prompts for AI Agents
Once connected, an AI agent can answer questions like:
Markets & Rates
"What are the top AAVE markets on Ethereum by TVL?"
"What is the current USDC supply APY on Base?"
"Compare WETH borrow rates across all AAVE V3 chains"
"Which chain has the cheapest stablecoin borrowing right now?"
User Positions
"Analyze the AAVE position for wallet 0x..."
"What is the health factor for address 0x... on Arbitrum?"
"Show me what 0x... has supplied and borrowed on Polygon"
"If ETH drops 30%, will address 0x... get liquidated?"
Protocol Activity
"Show me the last 20 liquidations on Ethereum AAVE"
"Who are the most active liquidators on Arbitrum this week?"
"What are the biggest flash loans on Base recently?"
"Show me recent USDC borrows on Optimism"
Governance
"What are the latest AAVE governance proposals?"
"Is there anything currently up for a vote in AAVE governance?"
"Show me who voted on proposal #185 and how"
"What governance proposals have passed recently?"
Development
git clone https://github.com/PaulieB14/graph-aave-mcp.git
cd graph-aave-mcp
npm install
npm run build
GRAPH_API_KEY=your-key node build/index.jsTo test with a specific chain:
# Start the server and query it with a GraphQL client or MCP inspector
GRAPH_API_KEY=your-key npx @modelcontextprotocol/inspector node build/index.jsSchema Notes
Lending subgraphs (V3) use AAVE-native schema:
reserves— individual asset marketsuserReserves— user positions per assetborrows,supplies,repays— transaction eventsliquidationCalls— liquidation eventsflashLoans— flash loan eventsreserveParamsHistoryItems— historical rate snapshots
Lending subgraphs (V2) use the same schema but with deposits instead of supplies.
Governance subgraph uses a separate schema:
proposals— governance proposals with votes and payloadsproposalVotes_collection— individual voter recordsproposalMetadata_collection— proposal titles and contentpayloads— on-chain execution payloadsvotingPortals,votingConfigs— governance configuration
License
MIT