Connect your AI assistant

You don’t have to build your site yourself. You can connect an AI assistant (Claude, ChatGPT, or any tool that speaks MCP) to your Bailey account, then just ask it in plain words:

“Make me a one-page site for my bakery at sunrise-bakery, with a sign-up form for the newsletter.”

The assistant builds the page, publishes it, and gives you back the live address. You can come back later and say “add the opening hours” or “how many people signed up?” and it does that too.

What it can do for you

Once connected, the assistant can, on your sites only:

• Create a new site at an address you choose, and put a page online.
• Update a page: change the text, the design, add a section.
• Check an address is free before using it.
• Read your sign-ups: the entries a form collected, newest first (only you can read these).
• See your numbers: votes, views, clicks, how many submissions came in.
• Take a site offline and bring it back, rename it, or change its address.
• Connect your own domain (like www.myshop.com) and tell you the exact DNS record to add.

It works with the same account you use for the dashboard, so everything it does shows up there too: versions, data, settings.

Connect it (about 20 seconds)

The address to connect to is:

https://app.trybailey.app/mcp

1. Open your assistant’s connector settings.

   • In Claude: Settings → Connectors → Add a connector (sometimes called Custom connectors).
   • In ChatGPT: the custom connectors / MCP section.
   • Any other MCP client: wherever you add an MCP server.

2. Paste the Bailey address above and confirm.

3. Log in once. A Bailey login window opens. If you’re already signed in to Bailey, it’s a single Authorize click. If not, sign in with your email and password (or Google) once, then Authorize.

That’s it: no token to copy, no key to generate, no client_id to create. The assistant now has access to your account and is ready.

Already building a site in chat?

You can hand the assistant a finished page in the same breath: “here’s the HTML, publish it at my-launch.” Bailey publishes a single self-contained HTML page directly. For a multi-file site (a built React/Astro folder, images, downloads), use the dashboard or the bailey CLI instead; those handle whole folders.

You stay in control

• It only ever touches your sites. The assistant can’t see, read or change anyone else’s sites or data; that boundary is enforced by Bailey, not by the assistant being polite.
• Sign-ups stay private. Forms are write-only from the page: visitors add entries but can’t read them back. Only you (and an assistant acting as you) can read submissions.
• Data collection is declared. If a page stores data or collects a form, the assistant has to declare what it’s for. A page that quietly collects personal data without a stated purpose won’t publish; see Data & privacy.
• You can pull the plug anytime. Take a site offline from the dashboard in one click, or remove the connector in your assistant’s settings to cut its access entirely.

”It says I need to log in again”

If the login window asks you to sign in even though you’re already using Bailey, just sign in once more in that window and click Authorize; it’s harmless and only happens the first time, or when your session has expired.

What’s next?

You’re connected. There’s one more short step that makes a real difference: add the Bailey skill, so your assistant reaches for Bailey on its own instead of waiting to be told.

Then ask for something: Your first page, in one ask.

---

For developers

Under the hood this is a standard MCP server with OAuth 2.1 discovery: Bailey is the authorization server and delegates the actual login to your Bailey identity. The full tool list, the protocol, and the data-declaration rules are in AI assistants (MCP).