Act on Avalanche from your agent: scaffold a dapp, deploy a contract, mint, and read chain state.
A server that acts on Avalanche from your agent to scaffold a dapp, deploy a contract, mint, and read chain state. It exposes tooling and workflows to interact with Avalanche-related development tasks via the MCP protocol.
🛠️ Key Features
Interacts with Avalanche network from an agent workflow
Scaffold a decentralized application (dapp) structure
Deploy smart contracts and perform minting
Read and query chain state through MCP-driven actions
Topics include ai, avalanche, devtools, infra, javascript, mcp, web3
🚀 Use Cases
Initialize dapp projects on Avalanche
Deploy and mint tokens or NFTs
Read and verify contract state within agent pipelines
⚡ Developer Benefits
Streamlined MCP protocol integration for Avalanche tasks
Clear, focused actions: scaffold, deploy, mint, read state
JavaScript-friendly interfaces aligned with web3 workflows
⚠️ Limitations
Details depend on MCP specifications and current network configuration
Specific endpoints or command options are not described in the provided data
▶ Watch the 90-second demo — one command to a live, social-login Avalanche dapp: sign in with Google, deploy an NFT from the browser, and mint it on Fuji.
bash
npm create avalanche-app@latest
That's it. Connect with a social login, read your balance, and send your first transaction on Avalanche in minutes.
Scaffolding an Avalanche dapp with create-avalanche-app
Then deploy an NFT contract and mint it, straight from the browser, on Fuji:
Connecting a wallet, deploying an NFT contract, and minting on Avalanche Fuji
Proven live on Fuji. The mint in that clip is a real on-chain transaction; view it on Snowtrace (contract 0x7612…7786). No Foundry, no backend: the bytecode is bundled and deployed from the user's wallet.
Why AvaKit
Avalanche's C-Chain is EVM-compatible and end-user onboarding is already solved (Core wallet's seedless social login). The remaining friction is on the developer side: spinning up a modern dapp with onboarding wired up still takes hours. AvaKit removes that.
Zero-setup onboarding: a temporary in-browser wallet appears so a newcomer can try a real Fuji transaction with nothing installed, and social login (Google, no seed phrase) or Core/MetaMask is the upgrade — for those, keys stay in the provider's HSM and AvaKit never touches them. (The burner is the exception, and holds its key in localStorage — see SECURITY.md.)
AI-native by default: every generated app ships CLAUDE.md, llms.txt, and .cursor/rules, and @avakit/mcp lets Claude Code / Cursor scaffold, deploy, and read chain state for you.
shadcn/ui, themed: a clean design system with dark/light from day one. Copy-in components, no vendor lock-in.
Deploy-ready: contracts compile to bundled bytecode, so you can deploy straight from the browser. Fuji testnet by default.
Safe defaults: testnet-first, mainnet is explicit opt-in, secrets stay in env.
Wrap, don't rewrite: built on viem, Web3Auth, and Foundry, packaged for a great DX.
Requirements: Node ≥ 20.11, pnpm ≥ 10. See CONTRIBUTING.md and the design docs in docs/. Conventions: English everywhere, shadcn/ui only, Framer Motion / GSAP for animation, latest stable versions.