Avalanche AVAX MCP
Let your coding agent search official Avalanche docs while you implement subnets, C-Chain apps, or AVAX integrations without leaving the editor.
Overview
Avalanche AVAX MCP is an MCP server for the Build phase that searches and retrieves Avalanche blockchain documentation for building on AVAX.
What is this MCP server?
- Streamable HTTP remote MCP at build.avax.network/api/mcp (no local npm install required for remote use)
- Search and retrieve Avalanche blockchain documentation tailored to building on AVAX
- Publisher keywords cover avalanche, avax, subnet, L1, web3, and blockchain
- GitHub source: Airpote/avalanche-mcp-vscode with registry version 1.0.1
- Hosted docs portal tie-in via build.avax.network
- Remote transport: streamable-http at build.avax.network/api/mcp
- Publisher categories: Blockchain, Documentation, Developer Tools
What problem does it solve?
Jumping between your editor and scattered AVAX docs slows implementation and invites wrong chain or subnet details in generated code.
Who is it for?
Indie builders adding AVAX, subnet, or Web3 features in Claude Code, Cursor, or Codex who want in-editor doc search via MCP.
Skip if: Teams that only need generic JavaScript help with no blockchain surface, or builders who want automated on-chain transactions rather than docs.
What do I get? / Deliverables
Your agent can pull grounded Avalanche documentation into the chat so AVAX-related code and explanations align with official references.
- In-chat excerpts and answers grounded in Avalanche documentation
- Faster reference lookup while coding AVAX-related features
Recommended MCP Servers
Journey fit
Documentation retrieval sits in Build because solo builders wire AVAX features during implementation, not during initial market research. Canonical shelf is docs: the server’s job is to fetch and cite Avalanche reference material, not to run infra or ship tests.
How it compares
Documentation remote MCP, not an Avalanche node runner or wallet integration skill.
Common Questions / FAQ
Who is Avalanche AVAX MCP for?
Solo developers and small teams building on Avalanche who want their AI editor to query official AVAX documentation through MCP.
When should I use Avalanche AVAX MCP?
Use it during Build when implementing AVAX apps, subnets, or integrations and you need searchable, retrievable docs inside the agent session.
How do I add Avalanche AVAX MCP to my agent?
Register the streamable-http remote URL https://build.avax.network/api/mcp in your MCP client (e.g. Claude Desktop, Cursor, or VS Code MCP extension) per your editor’s MCP setup docs.