Introduction

AvaKit is the open-source, AI-native developer toolkit for Avalanche: one framework-agnostic core plus four surfaces (React, a CLI, an MCP server, and Studio).

AvaKit gets you from idea to first transaction in minutes. You get social-login onboarding (no seed phrases), a shadcn/ui design system with dark and light from day one, deploy-ready contracts, and AI context so Claude Code and Cursor understand your project. It wraps mature pieces like viem, Web3Auth, and Foundry instead of reinventing them.

Quickstart

Scaffold a full dapp with one command:

$ npm create avalanche-app@latest my-app

Then follow the steps the CLI prints (they vary by template and wallet):

$ cd my-app
pnpm install
cp .env.example .env.local   # social login only; injected scaffolds skip this
pnpm dev

Open localhost:3000, connect a wallet, and send your first transaction on Avalanche Fuji.

The icm-messenger, l1-launch, and token-bridge templates start a local Avalanche devnet first — run pnpm run devnet / l1 / bridge (needs avalanche-cli and a Unix-like shell) before pnpm dev. See the CLI docs.

The packages

Everything is built on one framework-agnostic kernel, consumed through the surface you need:

@avakit/core: viem clients, wallet adapters, deploy helpers, and chain data.
@avakit/react: <ConnectAvalanche /> and hooks, built on shadcn/ui.
create-avalanche-app: the scaffolder that generates deploy-ready apps from eight templates.
@avakit/mcp: an MCP server so AI agents can scaffold, deploy, and read chain state.
@avakit/studio: a local dashboard for L1s, Interchain Messaging, and on-chain data (also an MCP server).

Design principles

Onboarding friction lives on the dev side. AvaKit removes it, not the wallet's.
Safe defaults: Fuji testnet first, mainnet is explicit opt-in, secrets stay in env.
No lock-in: adapter-based wallets and copy-in shadcn components.
AI-native: agent context ships with every app.

AvaKit is pre-1.0. The core, React layer, scaffolder, MCP, and Studio are built, published, and verified live on Fuji; APIs may still change before 1.0.

Go deeper

Curious how AvaKit is actually put together? The full story lives in the repo: the vision, the PRD, the architecture, the decision records, and per-package specs (00–12) — plus a security review.

Feel like a builder? Star the repo on GitHub, read the deep-dive docs, or grab all five packages on npm.

@avakit/core →The kernel: chains, adapters, deploy, data.@avakit/react →Provider, ConnectAvalanche, and hooks.create-avalanche-app →Scaffold a dapp from a template.@avakit/mcp →Drive Avalanche from Claude and Cursor.@avakit/studio →A local dashboard for L1s and ICM.