Avalanche Builder Hub MCP

Overview

Avalanche Builder Hub MCP is an official, read-only MCP server run by Ava Labs at build.avax.network. It gives AI clients access to Builders Hub documentation, CLI/RPC/ACP task lookup, GitHub code search across ava-labs repositories, and public blockchain queries such as balances, contract info, and P-Chain RPC/Info API calls. An agent builder plugs it in for grounded Avalanche documentation and on-chain lookups without running local infrastructure.

Tool inventory — 48 tools, probed live 2026-10-15

• docs_search — Search body-level chunks across Avalanche documentation, academy courses, integrations, and blog posts. Returns source citations and matching excerpts.
• docs_fetch — Fetch a specific documentation page as markdown
• docs_list_sections — List available documentation sections and their page counts
• cli_lookup_command — Look up Avalanche CLI, Platform CLI, and tmpnet command guidance in the docs. Returns cited command references and task docs.
• rpc_lookup_method — Look up Avalanche RPC methods and API guides across C-Chain, P-Chain, X-Chain, Subnet-EVM, and node RPC docs.
• acp_lookup — Look up Avalanche Community Proposals (ACPs) by number, title, or topic. When a number is provided the structured ACP record is returned (title, status, track, authors, cross-references).
• acp_list — List Avalanche Community Proposals with structured fields, optionally filtered by status (Activated, Implementable, Proposed, Stale, Withdrawn) or track (Standards, Best Practices, Meta, Subnet).
• avalanche_docs_search — Compatibility alias for docs_search. Prefer docs_search for new clients.
• avalanche_docs_fetch — Compatibility alias for docs_fetch. Prefer docs_fetch for new clients.
• avalanche_docs_list_sections — Compatibility alias for docs_list_sections. Prefer docs_list_sections for new clients.
• blockchain_lookup_transaction — Look up a transaction by hash on Avalanche (C-Chain, P-Chain, or X-Chain). Supports 0x format (C-Chain) and CB58 format (P/X-Chain).
• blockchain_lookup_subnet — Look up a Subnet / L1 by its ID — validators, chains, and configuration.
• blockchain_lookup_chain — Look up a blockchain by its ID — name, VM type, and Subnet/L1.
• blockchain_lookup_validator — Look up a validator by node ID — stake, uptime, delegation info.
• platform_get_height — Get the current P-Chain block height
• platform_get_block — Get a P-Chain block by its block ID
• platform_get_block_by_height — Get a P-Chain block by its height
• platform_get_blockchains — Get all blockchains that exist on the P-Chain (paginated; use limit/offset)
• platform_get_subnets — Get information about Subnets/L1s on the P-Chain
• platform_get_current_validators — Get the current validators of a Subnet/L1 (paginated; use limit/offset)
• platform_get_pending_validators — Get the pending validators of a Subnet/L1 (paginated; use limit/offset)
• platform_get_staking_asset_id — Get the asset ID of the token used for staking on a Subnet/L1
• platform_get_min_stake — Get the minimum staking amounts for validators and delegators on a Subnet/L1
• platform_get_total_stake — Get the total amount staked on a Subnet/L1
• platform_get_balance — Get the AVAX balance of one or more P-Chain addresses
• platform_get_utxos — Get UTXOs that reference a given set of P-Chain addresses
• platform_get_tx — Get a P-Chain transaction by its transaction ID
• platform_get_tx_status — Get the status of a P-Chain transaction
• platform_get_current_supply — Get the current total supply of AVAX on a Subnet/L1
• platform_get_validators_at — Get the validators and their weights of a Subnet/L1 at a given P-Chain height
• info_get_node_version — Get the version of the node, including the database version, git commit, and API compatibility info.
• info_get_network_id — Get the numeric ID of the Avalanche network this node is participating in.
• info_get_network_name — Get the human-readable name of the Avalanche network this node is participating in.
• info_get_blockchain_id — Get the CB58-encoded blockchain ID for a given blockchain alias (e.g., "X", "P", "C").
• info_is_bootstrapped — Check whether a given chain has finished bootstrapping on the node.
• info_get_tx_fee — Get the current transaction fees for the network, returned in both nAVAX and AVAX.
• info_peers — Get a list of peers this node is connected to. Optionally filter by specific NodeIDs.
• info_acps — Get information about Avalanche Community Proposals (ACPs), including their status and vote counts.
• blockchain_get_native_balance — Compatibility alias for onchain_lookup address balances. Prefer onchain_lookup for new clients.
• blockchain_get_contract_info — Compatibility alias for onchain_lookup contract metadata. Prefer onchain_lookup for new clients.
• blockchain_lookup_address — Compatibility alias for onchain_lookup address details. Prefer onchain_lookup for new clients.
• onchain_lookup — PRIMARY lookup tool — use this (not raw RPC) to resolve/describe any on-chain identifier in one call: an EVM address (native + token balances, recent txs, contract metadata + isContract), a contract/t
• onchain_activity — Time-windowed on-chain activity. scope=chain/address returns the transaction COUNT over the last `hours` (max 720h = 30 days; for longer windows use chain_stats series or onchain_query day-based ops)
• chain_stats — On-chain statistics via the query gateway, which picks the most accurate live source PER FIELD and stamps it (sources/warnings in the response). target=chain: tx count/gas/fees/active senders/avg gas
• onchain_query — PRIMARY tool for indexed on-chain stats/activity/totals — prefer this over raw RPC for chain data. Each `op` is a backend-agnostic intent: the query gateway selects the most accurate live source per f
• build_plan — Generate a step-by-step, copy-pasteable runbook for an Avalanche operation — Builder Console (no-code) path plus the equivalent platform-cli / SDK / interchain-kit commands. Read-only: never signs. op
• console_link — Return a deep-link into a specific Builder Console flow (create-l1, convert-to-l1, validator-manager, ictt, faucet, multisig, staking, transfers, interchain-kit-local). For faucet on mainnet, returns
• console_flow — Builder Console flow knowledge. Call with NO `flow` to list every flow (summaries + deep-links); call with a `flow` key to explain it (ordered steps, equivalent CLI, whether it signs transactions, dee

Answers a handshake

yes · 2026-10-15

Answers a call

not asked — no tool is named as a read (list_/get_/search_)

Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.

Where Avalanche Builder Hub MCP fits

Related concepts: What Are MCPs? The Standard Way to Give Agents Tools, What Are Onchain Agents?