@dedanzi/avalanche-mcp-server

MCP server that gives AI agents live access to Avalanche network data - L1 stats, ICM messages, ICTT transfers, validator info, and L1 deployment scaffolding.

Part of the Avalanche Developer AI Toolkit.

Quick Start

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "avalanche": {
      "command": "npx",
      "args": ["-y", "@dedanzi/avalanche-mcp-server"],
      "env": {
        "AVACLOUD_API_KEY": "your-key-here"
      }
    }
  }
}

Restart Claude Desktop. You can now ask:

• "What are the most active Avalanche L1s right now?"
• "Check the status of ICM message 0x1234..."
• "Generate a genesis.json for my new L1 with chain ID 12345"
• "Is validator NodeID-XXX active on my subnet?"

Run Directly

npx @dedanzi/avalanche-mcp-server

Install Globally

npm install -g @dedanzi/avalanche-mcp-server
avalanche-mcp-server

Getting an AvaCloud API Key

All 13 tools work without an API key using public endpoints. An AvaCloud API key unlocks higher rate limits and additional data fields on network, ICM, and ICTT tools.

1. Go to avacloud.io and sign up for a free account
2. In the AvaCloud console, navigate to Settings > API Keys
3. Click Create API Key, give it a name, and copy the key
4. Set it as AVACLOUD_API_KEY in your MCP config env (see Quick Start above) or in a .env file

The free tier includes rate limits sufficient for development and testing.

Tools (13 total)

Network

| Tool | Description | |------|-------------| | get_network_overview | Avalanche network health snapshot | | get_avalanche_l1s | List live Avalanche L1s | | get_l1_stats | Stats for a specific L1 (TPS, addresses, validators) | | get_validator_info | Validator status and uptime |

ICM (Interchain Messaging)

| Tool | Description | |------|-------------| | get_icm_messages | Recent ICM messages with filtering | | check_icm_message | Delivery status of a specific message | | get_icm_stats | ICM volume and delivery stats |

ICTT (Interchain Token Transfer)

| Tool | Description | |------|-------------| | get_ictt_transfers | Recent token bridge transfers | | get_ictt_tokens | ICTT-deployed tokens and their remotes |

Developer Utilities

| Tool | Description | |------|-------------| | scaffold_l1_deployment | Generate genesis.json + Hardhat config for a new L1 | | get_contract_addresses | Official Avalanche contract addresses | | decode_warp_message | Decode a raw Warp message payload | | check_avacloud_status | AvaCloud service health |

Configuration

# Optional - higher rate limits and additional data (get key at avacloud.io)
AVACLOUD_API_KEY=

# Optional - override default RPC endpoints
AVAX_MAINNET_RPC=https://api.avax.network/ext/bc/C/rpc
AVAX_FUJI_RPC=https://api.avax-test.network/ext/bc/C/rpc

# Optional
DEFAULT_NETWORK=mainnet
REQUEST_TIMEOUT_MS=10000

Example Interactions

Check ICM message delivery:

"Check if ICM message 0xabc123... was delivered"

Scaffold a new L1:

"Generate deployment files for my L1 called 'GameChain' with chain ID 99999, native token GAME, ICM enabled"

Monitor validators:

"Is NodeID-5mb46qkSBj81k9g9e1af1uAGbFjGcr1LL active on subnet 2D9GkvLMBuH4..."

Development

git clone https://github.com/mzf11125/avalanche-mcp-server
cd avalanche-mcp-server
npm install
npm run dev    # run with tsx (no build needed)
npm run build  # compile to dist/
npm test       # run tests

License

MIT