Build live experiences with Banto DSL
A small declarative language for real-time audience sessions. Describe what the host and audience see, wire up the actions, and publish. No socket plumbing required.
$ npm install -g @bantohq/cli
$ banto init my-game
$ banto publish Getting started
Install the CLI and the editor extension, scaffold a project, and publish a game to banto.tv.
Read more →The Banto language
A friendly tour of the DSL — blocks, types, actions, and components.
Read more →CLI reference
Every command, every flag, every config file.
Read more →Recipes
Copy-paste patterns for the things you'll actually build.
Read more →Registry reference
The components and functions Banto ships with.
Read more →Gotchas
Common compile errors and the fixes that clear them.
Read more →Build with Claude Code, Cursor, or Codex
Your agent writes .banto files locally, runs banto build, tests in the sandbox, and publishes to banto.tv. No Banto LLM on this path.
{
"mcpServers": {
"banto": {
"command": "npx",
"args": ["-y", "@bantohq/mcp@latest"]
},
"playwright": {
"command": "npx",
"args": ["-y", "@playwright/mcp@latest", "--headless", "--isolated"]
}
}
} Banto MCP loads the agent skill and docs on demand ( get_banto_skill, get_banto_docs, run_banto_cli). Playwright MCP is optional for automated sandbox playthroughs.
Download the agent skill
If you skip MCP, drop SKILL.md in your project (e.g. .claude/skills/banto-game/SKILL.md).