Graph Aave Mcp
Query Aave V2/V3 lending, liquidity, and governance data on seven chains through The Graph from your coding agent.
Overview
graph-aave-mcp is a MCP server for the Build phase that queries Aave V2/V3 lending and governance on seven chains through The Graph subgraphs.
What is this MCP server?
- AAVE V2 and V3 coverage for lending and governance queries
- Seven EVM chains reachable via The Graph subgraph endpoints
- npm package `graph-aave-mcp` with stdio MCP transport
- Requires GRAPH_API_KEY for authenticated subgraph access
- Purpose-built for agent-driven research bots, dashboards, and alerts
- AAVE V2 and V3 scope per server description
- Seven supported chains via The Graph subgraphs
- npm package version 1.0.0 with required GRAPH_API_KEY
Community signal: 1 GitHub stars.
What problem does it solve?
Building Aave-aware agents means wrestling with per-chain subgraph IDs, GraphQL, and API keys instead of shipping your actual product.
Who is it for?
Solo builders creating DeFi agents, risk dashboards, or governance assistants that need reliable Aave subgraph access.
Skip if: Builders with no GRAPH_API_KEY plan, non-EVM protocols, or products that only need static whitepaper summaries.
What do I get? / Deliverables
Your agent calls typed MCP tools to pull Aave lending and governance state across seven chains with one registered server.
- Chain-scoped Aave V2/V3 lending and liquidity query results
- Governance-related subgraph answers usable in agent prompts
- Repeatable Graph access without custom GraphQL client code in-repo
Recommended MCP Servers
Journey fit
Canonical shelf is Build because this MCP wires live DeFi subgraph data into products and agent workflows during implementation. Integrations matches a Graph-backed lending protocol connector that replaces bespoke subgraph clients in your codebase.
How it compares
Graph-integrated DeFi MCP server, not a generic blockchain RPC wrapper or a trading execution bot.
Common Questions / FAQ
Who is graph-aave-mcp for?
graph-aave-mcp is for developers and solo founders building MCP-enabled agents or apps that need structured Aave V2/V3 lending and governance data from The Graph.
When should I use graph-aave-mcp?
Use it during Build when you integrate live Aave metrics, positions, or governance context into agents, APIs, or analytics instead of hand-rolling subgraph queries.
How do I add graph-aave-mcp to my agent?
Install the npm package, set GRAPH_API_KEY from The Graph Studio, register the stdio MCP server in your client, and expose the tools to your agent session.