AvaKit logoAvaKit

@avakit/studio

A local control center for Avalanche development. You run it from your own terminal; it opens a browser dashboard, à la Prisma Studio.

Run it

No install needed. Start the dashboard with:

$ npx @avakit/studio

Studio starts a server bound to 127.0.0.1 and opens the dashboard in your browser. The devnet, Interchain, and Fuji features shell out to avalanche-cli and Foundry (forge / cast), so install those to use them; the Data view works without them.

Views

  • Overview: a snapshot of your local Avalanche environment and running devnets.
  • Devnet: spin up local L1s with Interchain Messaging, or launch your own L1 with a custom name, chain id, and token.
  • Interchain: deploy messenger contracts on each L1 and send a cross-chain message, watching it arrive.
  • Launch on Fuji: a guided wizard that funds a key, moves funds C to P, and deploys a sovereign L1 to the Fuji testnet with your machine as its validator.
  • Data: look up balances, NFTs, and transaction history for any Fuji or C-Chain address (via the AvaCloud Data API).
  • Environment: detect your toolchain (avalanche-cli, Foundry, Node) and copy an MCP config to connect an AI agent.

MCP mode

Studio exposes the same actions to AI agents over stdio. Point Claude Code or Cursor at:

{
  "mcpServers": {
    "avakit-studio": {
      "command": "npx",
      "args": ["-y", "@avakit/studio", "mcp"]
    }
  }
}

The agent can then inspect the environment, spin up devnets, launch L1s, send Interchain messages, and read address data. One tool, two faces: a dashboard for humans and an MCP server for agents.

Studio is a tool you launch yourself, so it may run local processes. It binds 127.0.0.1 only, checks the Host header, gates every API call behind a per-session token, and runs external tools with fixed argument arrays (never a shell). See SECURITY.md.