Aave Mcp
Wire your agent to live Aave lending, supply, and borrow data when researching or building DeFi-related products.
Overview
io.github.junct-bot/aave-mcp is a MCP server for the Idea phase that exposes six tools for Aave lending rates, supply, and borrow data over streamable HTTP.
What is this MCP server?
- Six MCP tools focused on Aave lending rates, supply, and borrow data
- Hosted streamable-http remote at aave.mcp.junct.dev—no local chain node required
- Version 1.1.0 with GitHub source at junct-bot/aave-mcp
- Fits agent workflows that compare pools and rates during spec and copy drafting
- Pairs with other junct finance MCP servers for multi-protocol research
- 6 Aave-focused MCP tools
- Server version 1.1.0
- Streamable-http remote endpoint
What problem does it solve?
Solo builders waste cycles tab-switching to Aave analytics sites whenever an agent needs fresh lending and borrow figures in a spec or script.
Who is it for?
Indie builders exploring DeFi product ideas, yield comparisons, or agent-assisted research memos grounded in live Aave stats.
Skip if: Teams that need trade execution, wallet signing, or full portfolio management without a separate execution layer.
What do I get? / Deliverables
After you add the remote MCP URL, your agent can call structured Aave market data inside the same thread where you research and plan the product.
- Agent-callable Aave rate and market snapshots in chat
- Structured protocol data for specs, comparisons, and copy drafts
- Repeatable research workflow without manual site scraping
Recommended MCP Servers
Journey fit
Canonical shelf is Idea because the first solo-builder win is researching yields and protocol economics before committing to a build. Research subphase fits rate and market lookups that inform whether a DeFi or treasury angle is worth pursuing.
How it compares
Remote finance data MCP server, not an on-chain transaction skill or generic web scraper.
Common Questions / FAQ
Who is io.github.junct-bot/aave-mcp for?
It is for solo builders and small teams using MCP-capable coding agents who need Aave lending and borrow metrics while researching or writing DeFi-related software.
When should I use io.github.junct-bot/aave-mcp?
Use it when you are in the research or validation phase and want six focused tools for rates and supply or borrow data without building your own Aave indexer.
How do I add io.github.junct-bot/aave-mcp to my agent?
Register the streamable-http remote URL https://aave.mcp.junct.dev/mcp in your MCP client (Claude Code, Cursor, Codex, or compatible hosts) per your editor’s MCP settings.