Graph MCP Server

AAVE V2/V3 lending & governance MCP — 7 chains via The Graph subgraphs. That is what the graph mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Covers lending markets, user positions, health factors, cross-chain liquidation risk monitoring, liquidations, flash loans, governance, V4 hubs/spokes, exchange rates, swap quotes, rewards, and protocol history.

The tools it exposes

The server publishes 8 tools. What each one is for:

• get_v4_hub_flows — Hub↔Spoke routing events (Add, Remove, Draw, Restore, RefreshPremium, ReportDeficit, TransferShares) with AaveKit-joined spoke names and asset symbols
• get_v4_user_risk_trajectory — Per-user risk-premium snapshot history — every RefreshPremium event for a user, plus the latest premium and the spoke it was set on
• get_v4_liquidation_postmortem — Full liquidation event by tx hash or user — collateral/debt amounts, liquidator, premium-share / offset-ray / restored-premium deltas
• get_v4_treasury_flows — Merged stream of FeeMint / Sweep / Reclaim / DeficitEliminated events ordered by block desc, optionally filtered by hub (Core/Plus/Prime) and time
• get_v4_spoke_config_history — Spoke liquidation-config governance trail — current and historical targetHealthFactor, healthFactorForMaxBonus, liquidationBonusFactor per spoke
• Discovery — The Discovery tool exposed by this server
• Governance — The Governance tool exposed by this server
• Advanced — The Advanced tool exposed by this server

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

What it needs from you

Configuration is passed through the environment: GRAPH_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Graph's toolset — get_v4_hub_flows, get_v4_user_risk_trajectory, get_v4_liquidation_postmortem and 5 more — is a fair guide to whether it matches your workflow. It is maintained by PaulieB14; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Graph's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.