Avalanche MCPGitHub

Model Context Protocol · open source · read-only

Avalanche,
explained to
your AI agent.

One MCP server with the whole Avalanche stack: docs and Academy, every ACP and network upgrade, live C/P/X-Chain data, and step-by-step L1, precompile and ICM workflows. Hosted or local. No API key.

$claude mcp add avalanche --transport http https://avalanche-mcp.dev/mcp
Install guide
avalanche-mcp — zsh
$ claude mcp add avalanche --transport http https://avalanche-mcp.dev/mcp
✓ Added HTTP MCP server avalanche to local config
$ claude
/mcp  →  avalanche · connected · 41 read-only tools
$ › Which ACPs does Helicon activate, and is it live on mainnet?
⏺ avax_upgrade_lookup(query: "Helicon")
Helicon (v1.15.0-fuji) activates ACP-194, 236, 267, 273, 283, 285. Fuji since 2026-07-28; mainnet not scheduled.
Source: build.avax.network/docs/primary-network/helicon-upgrade
$
Mainnet C-Chain block
—
Gas price
—
Tools
41 · read-only
Indexed chunks
9,905
ACPs
36 · structured
Endpoint
/mcp · hosted

What it looks like

Ask in plain language. Get cited answers.

The agent picks tools itself: a structured lookup for the upgrade, the ACP that defines it, then the official page — and returns the build.avax.network URLs it read.

› What changes in the Helicon upgrade for my C-Chain indexer? ⏺ avax_upgrade_lookup(query: "Helicon") ⏺ avax_acp_lookup(query: "ACP-194") ⏺ avax_get_doc(content/docs/primary-network/helicon-upgrade.mdx) Helicon (AvalancheGo v1.15.0-fuji) is live on Fuji since 2026-07-28; mainnet is not scheduled yet. For an indexer the relevant change is ACP-194 Continuous Execution: consensus and execution are decoupled, so a block's state root settles after a τ delay (~5 s). Don't treat "latest" as executed state — index the settled block, and note several C-Chain RPC namespaces are deprecated alongside it. ACP-283 also makes the minimum gas price dynamic, so never hardcode a fee floor. Sources build.avax.network/docs/primary-network/helicon-upgrade build.avax.network/docs/acps/194-continuous-execution ›

What your
agent gets

01

Knows the docs. All of them.

A bundled index of build.avax.network — docs, Academy, 234 integrations, blog — plus Subnet-EVM precompile docs, ICM contracts, the Avalanche CLI reference and every ACP. 9.9k chunks searched locally in milliseconds, each hit with its source URL.

  • avax_search_docs
  • avax_get_doc
  • avax_get_guide
  • avax_search_integrations
  • avax_fetch_live_doc
02

Reads the chain, live.

C-Chain, Fuji, known L1s or any RPC URL through viem; P-Chain validators, subnets, staking economics and tx status over JSON-RPC; indexed balances and history from the Avalanche Data API. Read-only by construction.

  • avax_get_chain_status
  • avax_call_contract
  • avax_pchain_get_validators
  • avax_pchain_get_subnet
  • avax_data_list_chains
03

Turns questions into runbooks.

Plan an L1 for a use case, generate a valid genesis.json with the right precompiles, get a Teleporter sender/receiver recipe with real addresses, or paste an error and get the fix. Builder Console links and platform-cli commands included.

  • avax_plan_l1_launch
  • avax_generate_genesis
  • avax_explain_precompile
  • avax_icm_recipe
  • avax_troubleshoot
04

Stays current.

A structured upgrade timeline from Banff to Helicon, live ACP signaling from nodes, the always-fresh .md endpoint for any page, and a proxy to Ava Labs' hosted MCP. Facts models get wrong — like the 1-wei C-Chain base fee — are pinned and verified.

  • avax_upgrade_lookup
  • avax_acp_list
  • avax_acp_votes
  • avax_hosted_call

One line.
Any client.

  1. 01

    Add the server

    Same shape as Ava Labs' hosted MCP: a public Streamable HTTP endpoint, no key, no install. Pick your client:

    Hosted — nothing to install:

    claude mcp add avalanche --transport http https://avalanche-mcp.dev/mcp

    Or commit it for the whole team in .mcp.json: { "mcpServers": { "avalanche": { "type": "http", "url": "https://avalanche-mcp.dev/mcp" } } } Run /mcp to verify — you should see avalanche with 41 tools.

  2. 02

    Ask

    The agent picks the right tools and cites build.avax.network for every claim.

    • TransportStreamable HTTP (stateless JSON) · stdio for local
    • KeysNone. Optional GLACIER_API_KEY in local mode
    • SafetyEvery tool is read-only. No private keys, no transactions
    • CompanionsWorks alongside build.avax.network/api/mcp, chainkit and AvaCloud MCPs

41 tools.
Every one read-only.

Knowledge

7
  • avax_search_docs
  • avax_get_doc
  • avax_list_docs
  • avax_list_topics
  • avax_get_guide
  • avax_search_integrations
  • avax_fetch_live_doc

Protocol & upgrades

4
  • avax_acp_list
  • avax_acp_lookup
  • avax_acp_votes
  • avax_upgrade_lookup

Workflows

6
  • avax_plan_l1_launch
  • avax_generate_genesis
  • avax_explain_precompile
  • avax_icm_recipe
  • avax_troubleshoot
  • avax_console_flows

Live EVM

8
  • avax_list_networks
  • avax_get_chain_status
  • avax_get_balance
  • avax_get_block
  • avax_get_transaction
  • avax_get_code
  • avax_call_contract
  • avax_estimate_gas

P-Chain · X-Chain · node

8
  • avax_pchain_get_validators
  • avax_pchain_get_subnet
  • avax_pchain_list_blockchains
  • avax_pchain_get_stake_info
  • avax_pchain_get_tx_status
  • avax_pchain_get_balance
  • avax_xchain_get_balance
  • avax_node_info

Data API

5
  • avax_data_list_chains
  • avax_data_list_erc20_balances
  • avax_data_list_transactions
  • avax_data_get_token_metadata
  • avax_data_list_l1_validators

Hosted federation

3
  • avax_hosted_list_tools
  • avax_hosted_call
  • avax_hosted_read_index

Things to ask
on day one

Open source.
MIT.

Add your L1 to the network registry, write a guide, or point the indexer at a new source — each is a single TypeScript file.

View on GitHub