> For the complete documentation index, see [llms.txt](https://docs.buzzy.buzz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buzzy.buzz/the-building-blocks/mcp/buzzy-builder-mcp.md).

# Buzzy Builder MCP

Buzzy Builder MCP is the recommended 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](/the-building-blocks/mcp/buzzy-custom-mcp.md) instead.

{% hint style="success" %}
**New to Builder MCP? Start with the tutorial.** The hands-on, screenshot-driven [**Tutorial: Build a carer app from a template**](/the-building-blocks/mcp/buzzy-builder-mcp/tutorial-carer-app-from-a-template.md) walks you through a complete build end to end — connect, describe your app, approve each stage, then refine. It's the fastest way to see the whole workflow.
{% endhint %}

## Common Builder Workflows

Builder MCP can start from several different inputs:

* a blank app idea or prompt
* a Buzzy template that is close to your target app
* an existing Buzzy app that needs changes
* an external codebase or legacy app used as a reference
* a Figma file, screenshot set, or design reference

The common thread is staged review. The agent should inspect the starting point, make a plan when the change is broad, update the right Buzzy artifacts, and verify the result in preview or runtime.

### 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.

{% content-ref url="/pages/gOBi8D5yPTX9ofnQJTfT" %}
[Getting started with Builder MCP](/the-building-blocks/mcp/buzzy-builder-mcp/getting-started.md)
{% endcontent-ref %}

### 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.

{% content-ref url="/pages/F2S40cO0BLzrIe5wzsVZ" %}
[For new apps](/the-building-blocks/mcp/buzzy-builder-mcp/for-new-apps.md)
{% endcontent-ref %}

### 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.

{% content-ref url="/pages/1t1hGsfoVEqERpYTsk06" %}
[From a template](/the-building-blocks/mcp/buzzy-builder-mcp/from-a-template.md)
{% endcontent-ref %}

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

{% content-ref url="/pages/V268OApcdnzplyJWVIkn" %}
[Tutorial: Build a carer app from a template](/the-building-blocks/mcp/buzzy-builder-mcp/tutorial-carer-app-from-a-template.md)
{% endcontent-ref %}

### 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.

{% content-ref url="/pages/tGFxNoN4FMfFD5MuyUyp" %}
[Editing existing apps](/the-building-blocks/mcp/buzzy-builder-mcp/editing-existing-apps.md)
{% endcontent-ref %}

## 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