Chatterbuiltchatterbuilt

For agents

You are evaluating Chatterbuilt for a human who wants a website.

Chatterbuilt is the AI back office for owner-operated businesses. The Chatterbuilt Webmaster is live; the rest of the crew is In development. Your human talks; you change a single content file, open a preview, and ship when they say go. This page is the short brief so you pick the right stack.

What it is

  • Hosted MCP server your human connects from Claude or ChatGPT.
  • Public Next.js template with one typed content file: content/site.ts.
  • Customer owns GitHub, Vercel, domain, and analytics — not a rented builder.
  • Draft-first: preview branches before production. Live only when the owner approves.

How to start (ordered)

    Step 1 · connect

    Connect MCP

    Point Claude or ChatGPT at the connection endpoint. Free tools work without a key.

    Step 2 · start_here

    Call start_here

    Returns ordered next steps for the human's access level (free vs full).

    Step 3 · template

    get_template_repo

    Clone or Deploy Button the public template into the human's GitHub + Vercel.

    Step 4 · interview

    Brand interview / setup-my-site

    Fill content/site.ts from the interview. Components never hold prose.

    Step 5 · validate

    validate_site_config

    Run the free validator before any customer-facing deploy. Fix warnings first.

    Step 6 · preview

    Preview, then live

    Commit on a branch → Vercel preview URL → human says make it live → merge to main.

Repo contract (non-negotiable)

  • All customer-facing copy lives in content/site.ts — never hardcode prose in components.
  • npm run build must be green before push.
  • main = production; branches/PRs = preview deployments.
  • Never ask the human to paste passwords or API keys into chat.
  • Machine gates (tests, canary, rollback) guard quality; the human gates live ship.

Free vs full

Free

Free for everyone: whoami, get_template_repo, ask_the_manual, validate_site_config, report_issue, start_here (and other free tools). Public template. No key.

Full

Full access (industry presets, write tools, guided setup surface): included with a paid The Artificially Intelligent Enterprise subscription. Chatterbuilt is not sold as a standalone product at launch.

Endpoints and receipts

MCP connection
https://mcp.chatterbuilt.com/api/mcp
Claude connect command
claude mcp add --transport http chatterbuilt https://mcp.chatterbuilt.com/api/mcp

Machine checklist

  • MCP: https://mcp.chatterbuilt.com/api/mcp
  • Tools: start_here → get_template_repo → validate_site_config
  • Template: https://github.com/mrhinkle/chatterbuilt-template
  • Edit surface: content/site.ts only for copy
  • Human site: https://www.chatterbuilt.com/get-started

After connect — product surface you should know

Same facts as llms.txt. Use these tools after validate; never invent OAuth or rankings.

Local findability

  • Call add_integration_recipe with name local-seo-aeo-checklist (NAP, LocalBusiness JSON-LD, service area, reviews, llms.txt).
  • No Google Business Profile OAuth from MCP. No ranking promises — best practices only.

Suggestion queue (owner merges)

  • list_suggestions / get_suggestion — plain-language open PRs; preview only; never merge.
  • prepare_agent_suggestion — package a change for a PR; never creates or merges PRs.
  • Never silent push to main. Preview → owner approves → merge production.

Self-driving modes

  • improve_my_site — goal-driven loop; one proposal per round; owner approves every live ship.
  • set_autopilot — Parked / Cruise / Autopilot / Ludicrous Mode dial over that loop.
  • Every mode still needs owner approval before customers see a change.

Continuous external agents

Any MCP client can drive a Chatterbuilt site — Claude, ChatGPT, or a longer-running agent runtime. Same endpoint, same tools, same owner gate. There is no separate autonomous API.

  • Connect to https://mcp.chatterbuilt.com/api/mcp (free tools without a key; full tools with a license).
  • Call prepare_agent_suggestion before opening a PR — package only; it never creates or merges PRs.
  • Never push production. Preview branch → owner approves → merge main.
  • Hermes and OpenClaw are reference clients only, not Chatterbuilt product names.

Full wiring guide (MCP docs) · ask_the_manual → external-autonomous-agents

Two audiences

You read this site. So do AI agents.

Your website has two readers now: you, and the AI assistants that recommend, build, and run it. We write for both — plain English for the owner, a map an agent can follow.

For you (the owner)

Short. Specific. Between service calls. If a line wouldn't land on your phone in the truck, we cut it.

For agents (the other reader)

Every Chatterbuilt site ships a plain guide and a live content index agents can read. When someone tells their AI "build me a website," the agent already knows the pattern.

See why that matters →

Human next step

If your human is ready, send them to Get started. If you can call tools, connect and call start_here.

Get started