Using your own Claude to build

Connect BurrowHub to your own Claude: Claude writes the app on your Claude plan, and BurrowHub checks, builds, previews, publishes and keeps every version.

On this page

What it is

You add BurrowHub to your own Claude as a connector and ask it for an app. Claude writes the code; BurrowHub checks it, builds it in its sandboxed builder, runs it on its own, shows you a preview, publishes it when you say so and keeps every version.

  • The writing counts against your Claude plan, not your business's AI credits. BurrowHub never sees your Claude sign-in.
  • Each preview is one of your business's builds for the day. Checks have their own daily allowance (60 a day unless your BurrowHub sets another number).
  • Owners and admins can connect, and so can a partner (consultant) working for the business. You choose the business when you connect.

Add the connector

The connector's address is https://burrowhub.com/api/mcp/build (on a self-hosted BurrowHub, your hub's own address followed by /api/mcp/build).

  1. In claude.ai or Claude Desktop, open Customize → Connectors and choose + Add → Add custom connector.
  2. Name it BurrowHub, paste the address, and leave sign-in on (OAuth).
  3. Choose Connect. BurrowHub's sign-in opens: sign in, pick the business, and allow what Claude may do — read apps; write drafts, check and preview; publish and roll back.
In Claude Code
claude mcp add --transport http burrowhub https://burrowhub.com/api/mcp/build

The first time a BurrowHub tool is used, Claude Code opens BurrowHub's sign-in in your browser.

How a build goes

  1. Get the contract. Claude reads BurrowHub's build guide (get_build_guide) — the fixed stack, the files it may write and every rule — and your business (get_workspace_context): brand kit, data sources with their columns, apps.
  2. Write. It starts a draft (start_draft) and writes files (write_files). Anything it may not write — configuration, new packages, BurrowHub's own files — is refused with the reason.
  3. Check. check_draft runs every check in the sandboxed builder. Each problem comes back as rule, file, line and fix; Claude corrects it and checks again. This usually takes a few rounds of a minute or two.
  4. Preview. When the check passes, preview_draft builds a version. A new app's first version goes live; a change waits as the preview. Claude gives you the link.
  5. Publish. Look at it. Say "publish it" and Claude calls publish_preview; "put version 2 back" and it calls restore_version.

Everything Claude did is in BurrowHub too: the app's page shows each version as written by your assistant, who published it and when.

Prompting tips for Claude

Everything in How to describe your app applies. A few things help with the connector in particular:

  • Say "using BurrowHub", so Claude reaches for the connector instead of writing code in the chat.
  • Name your data sources exactly as they appear under Your data, and the columns that matter.
  • Ask for the preview link, and say "don't publish until I say so".
  • Change one thing per draft, and say which app: "change the Stock app".
  • The guide for the people who use the app is part of every version; ask Claude to keep it up to date with each change.
A first request through the connector
Using BurrowHub, build a stock list for our shop. Read BurrowHub's build guide first. Build it on our "Products" data source (Qty is stock on hand, Min is when to reorder). Staff record what came in and went out from their phones, and AI reads a photo of a delivery note into the form. Give me the preview link and don't publish until I say so.

These docs, inside Claude

The connector carries these pages, so Claude can follow them while it works. In Claude's connector menu you'll find:

  • Resources — every page as burrowhub://docs/<page>, in your language.
  • Prompts — describe-business-app asks for your business, users, data and goal and turns them into a request that follows this guide; ask-for-a-change writes one small change; review-app-request checks a request against the checklist.
  • Tools — search_docs and get_doc, which only read these pages.

If something goes wrong

  • Claude can't reach BurrowHub — check the address ends in /api/mcp/build. A self-hosted hub must be on the internet over HTTPS for claude.ai and Claude Desktop.
  • "This connection wasn't allowed …" — you didn't allow that when you connected. Disconnect BurrowHub in Claude and connect again, allowing it.
  • "The draft changed since its last check" — ask Claude to run the check again; preview after it passes.
  • The preview link shows the live app — open it signed in to BurrowHub as someone who builds the app; only they see a preview.
  • Drafts disappeared — a draft nobody changes for 7 days is removed. Built versions are never removed this way.
All docs

Ready to describe yours?

Write what your business needs, or start from one of six starting points.