For the complete documentation index, see llms.txt. This page is also available as Markdown.

Buzzy Builder MCP

Buzzy Builder MCP is the workflow for using an AI agent to build or change a Buzzy app. The agent connects to Buzzy's MCP server, follows Buzzy's bootstrap instructions, and works with you through staged app-building and review.

Use this section when you want an agent to create, inspect, or edit the app itself. If you already have an app and want that app to expose tools to ChatGPT or Claude, use Buzzy Custom MCP instead.

Common Builder Workflows

Getting started

Start here once per project. This covers MCP credentials, connecting your agent, bootstrapping the local repo, and the review habits that apply to every Builder MCP workflow.

Getting started with Builder MCP

For new apps

Start with an empty repo and a focused app prompt. After setup, the agent creates the app and moves through the brief, flows, data model, theme, blueprint, screens, sample data, and refinement stages.

For new apps

From a template

Start from an existing Buzzy template when the app shape is close to something Buzzy already provides. The agent should still inspect the template, identify the changes you need, and work through staged edits rather than treating the template as finished.

From a template

Prefer a guided, screenshot-by-screenshot build? Follow the full walkthrough:

Getting started with Buzzy Builder MCP

Editing existing apps

Use MCP to help an agent inspect the current app, plan the smallest useful change, apply edits in stages, and verify the result in preview or runtime.

Editing existing apps

Working Style

Good Builder MCP work is collaborative and staged:

  • connect the agent to Buzzy MCP and bootstrap the repo first

  • review generated artifacts before moving downstream

  • use sample data and screenshots when screens exist

  • ask for a plan before broad screen or data-model changes

  • verify important runtime paths before treating the change as complete

Last updated