Does Aave have an MCP server?
Aave maintains an official MCP server.
Prepares transactions for the user's wallet to sign; it does not hold keys.
- Access
- Remote server
- Endpoint
- https://mcp.aave.com
- Category
- Finance & Fintech
A remote server run by Aave itself — nothing to install. Documented at aave.com.
Hosted by the vendor — no install, connect over HTTP with OAuth or a token.
Add it from the terminal, then restart your session:
claude mcp add --transport http aave https://mcp.aave.comAdd --scope user to make it available in every project.
- Open Settings → Connectors
- Click Add custom connector
- Paste
https://mcp.aave.com - Finish the sign-in prompt, then enable it in the chat's tools menu
Add to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for
every project:
{
"mcpServers": {
"aave": {
"url": "https://mcp.aave.com"
}
}
}A green dot in Settings → MCP means it connected.
Add to .vscode/mcp.json:
{
"servers": {
"aave": {
"type": "http",
"url": "https://mcp.aave.com"
}
}
}Then pick the server from the tools menu in Copilot's agent mode.
- Enable Developer mode under Settings → Apps & Connectors → Advanced
- Choose Create and paste
https://mcp.aave.com - Complete sign-in, then enable the connector in a new chat
Does Aave have an official MCP server?
Yes. Aave maintains an official MCP server, hosted at https://mcp.aave.com.
How do I connect Aave to Claude?
Add https://mcp.aave.com as a custom connector under Settings → Connectors in Claude Desktop or claude.ai, or run "claude mcp add --transport http aave https://mcp.aave.com" in Claude Code.
Do I need to install anything to use the Aave MCP server?
No. It is a remote server hosted by Aave, so your MCP client connects to it over HTTP. You authenticate with the vendor rather than installing a package.
How is this verdict verified?
Published to the MCP Registry under Aave's verified namespace com.aave and documented at aave.com/docs/mcp (server endpoint mcp.aave.com), which answers MCP initialize with 200; the source is also published on npm as @aave/mcp by Aave maintainers. GitHub metadata is refreshed every six hours.
Published to the MCP Registry under Aave's verified namespace com.aave and documented at aave.com/docs/mcp (server endpoint mcp.aave.com), which answers MCP initialize with 200; the source is also published on npm as @aave/mcp by Aave maintainers.
- github data refreshed 2026-09-29, then every 6 hours
- vendor docs verified on 2026-09-29
Spotted something out of date? Tell us — corrections ship same-day.