MCP Server

Search Avalanche docs, code, RPCs, CLI commands, ACPs, and public network data via Model Context Protocol

The Avalanche MCP server gives AI clients a read-only interface to Builders Hub knowledge and public Avalanche tooling context.

Endpoint: https://build.avax.network/api/mcp

Scope

Surface	Tools
Documentation	`docs_search`, `docs_fetch`, `docs_list_sections`
Task lookup	`cli_lookup_command`, `rpc_lookup_method`, `acp_lookup`, `acp_list`
GitHub	`github_search_code`, `github_get_file`, `github_list_repositories`
Public blockchain lookup	`blockchain_get_native_balance`, `blockchain_get_contract_info`, `blockchain_lookup_*`
P-Chain RPC	`platform_get_*`
Info API	`info_get_*`, `info_is_bootstrapped`, `info_peers`, `info_acps`

docs_search searches body-level chunks across documentation, academy courses, integrations, and blog posts. Results include source URLs, chunk numbers, and matching excerpts.

The older avalanche_docs_search, avalanche_docs_fetch, and avalanche_docs_list_sections names remain available as compatibility aliases. Prefer the shorter canonical names for new clients.

GitHub Coverage

The GitHub tools cover these repositories:

ava-labs/avalanchego
ava-labs/subnet-evm
ava-labs/coreth
ava-labs/avalanche-cli
ava-labs/platform-cli
ava-labs/icm-services
ava-labs/avalanche-network-runner
ava-labs/icm-contracts
ava-labs/hypersdk
ava-labs/libevm
ava-labs/builders-hub

Resources

Resource	Purpose
`docs://index`	All documentation pages
`academy://index`	Academy pages
`integrations://index`	Integration pages
`blog://index`	Blog posts
`rpcs://index`	RPC method and API docs
`cli://index`	Avalanche CLI, Platform CLI, and tmpnet docs
`acps://index`	ACP docs

Claude Code Setup

claude mcp add avalanche-mcp --transport http https://build.avax.network/api/mcp

Or add it to .claude/settings.json:

{
  "mcpServers": {
    "avalanche-mcp": {
      "transport": {
        "type": "http",
        "url": "https://build.avax.network/api/mcp"
      }
    }
  }
}

Claude Desktop Setup

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "avalanche-mcp": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://build.avax.network/api/mcp"]
    }
  }
}

Claude Desktop uses stdio transport and does not support HTTP MCP servers natively. mcp-remote acts as a bridge from stdio to the HTTP endpoint. Node.js must be installed for npx to work.

JSON-RPC Examples

Search docs:

curl -X POST https://build.avax.network/api/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "docs_search",
      "arguments": {
        "query": "create an L1 with a custom precompile",
        "limit": 5
      }
    }
  }'

Look up a CLI task:

curl -X POST https://build.avax.network/api/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
      "name": "cli_lookup_command",
      "arguments": {
        "query": "add validator",
        "cli": "avalanche-cli"
      }
    }
  }'

Look up an RPC method:

curl -X POST https://build.avax.network/api/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 3,
    "method": "tools/call",
    "params": {
      "name": "rpc_lookup_method",
      "arguments": {
        "query": "platform_getCurrentValidators",
        "chain": "p-chain"
      }
    }
  }'

Look up a specific ACP and list activated standards-track ACPs:

# Structured lookup of ACP-77 with full table fields
curl -X POST https://build.avax.network/api/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 4,
    "method": "tools/call",
    "params": {
      "name": "acp_lookup",
      "arguments": { "number": 77 }
    }
  }'

# All Activated ACPs on the Standards track
curl -X POST https://build.avax.network/api/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 5,
    "method": "tools/call",
    "params": {
      "name": "acp_list",
      "arguments": { "status": "Activated", "track": "Standards" }
    }
  }'

Search code:

curl -X POST https://build.avax.network/api/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 6,
    "method": "tools/call",
    "params": {
      "name": "github_search_code",
      "arguments": {
        "query": "TransformSubnetTx",
        "repo": "avalanchego",
        "language": "go"
      }
    }
  }'

List server tools:

curl -X POST https://build.avax.network/api/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":7,"method":"tools/list"}'

The hosted MCP server is read-only. It does not execute local shell commands, run Avalanche CLI commands, modify node state, or access private files. Local/operator execution is tracked separately in the public roadmap issue: ava-labs/builders-hub#4070.

For AvaCloud and Chainkit API surfaces, use companion MCP servers alongside this hosted server:

claude mcp add avalanche-mcp --transport http https://build.avax.network/api/mcp
claude mcp add avalanche-chainkit --command "npx -y @avalanche-sdk/chainkit mcp-server"
claude mcp add avalanche-avacloud --command "npx -y @avalabs/avacloud-sdk mcp-server --apikey $AVACLOUD_API_KEY"