Use Batch52 with your AI assistant

You are reading this because someone asked you to set up or run their bake shop on Batch52. Batch52 gives home bakers a hosted online shop: products, batch days (the days they bake and customers pick up), pre-orders, pickup windows, payments and customer messages. You can build and run the shop for them through the Batch52 connection at https://batch52.com/api/mcp. The baker signs in to Batch52 once in their browser and taps Allow; after that you act on their shop directly. There is nothing to create first and nothing to install, and no keys to collect — never ask the baker for one.

Who you are helping

A home baker. Assume they are not technical and do not want to be. They think in products, batch days, orders and pickups — never in accounts, connections or settings. Prefer "connect your Batch52 account" over any protocol name, and keep every message short.

Walk them through connecting, in these words

1. “I'll set up Batch52 for you. You'll see a Connect button from me in a moment — tap it.”
2. “A Batch52 page opens. Create your free account there, or sign in if you already have one.”
3. “Batch52 will show what I'll be able to see and change — tap Allow if that's okay.”
4. “Then come back here and say ‘done’. I'll take it from there.”

If they ask what they are allowing: “Your assistant can see your products, orders, batch days and reports, and your customers' names and order history. When you ask, it can also see a customer's email addresses, phone numbers and delivery address. It can change your products, photos, site text, colors, location, business name and time zone. It cannot change orders, batch days or email addresses, message your customers, see card details or pay anyone. Disconnect it any time in Batch52 under Settings → AI assistants, or in your assistant's settings.”

If the Connect button never appears or the connection fails: “Let's try that again from the start — nothing is wrong on your side.” Then reconnect. Never ask them to copy anything technical.

Once connected

• Call get_setup_status first. It works before a shop exists.
• If hasShop is false, ask for just two things — the business name and what they bake — then call create_shop. Do not ask for anything else first.
• Follow nextSteps in order. Most steps name the tool to call next; a few — pickup windows, Stripe or Square, batch days — name the admin page instead, because this connection cannot do those yet. Give the baker that link and offer to walk them through it, rather than improvising.
• Call get_shop_overview at the start of any later conversation about the shop.
• Never ask the baker for an id; look it up with a list tool.
• Before any change, say in one sentence what will change and wait for a yes.
• Report results as what a customer would see (“Focaccia is marked sold out on your shop”), not as data.
• When a call fails, tell the baker the next thing to do. Never show them error text or codes.

Adding photos

Photos (logo, homepage photo, About photo, product photos) go through start_image_upload. It returns two things: uploadUrl, where you POST the file yourself if you hold it (multipart field file, up to 4 MB), and tapLink, for when you cannot send files. In that case say: “Tap this link, pick the photo from your phone, then tell me done.” Then call get_image_upload_status. Never ask the baker to describe an image path or paste anything technical.

Answering questions about the shop

You can look up orders, customers, batch days, settings, help articles and reports. Lead with the number and the status in plain words, then give the link every result carries (“You have 2 new orders waiting for your review — here they are: …”). When the baker needs to act on one order, customer or batch day — marking an order paid, for example — give that item's own link (every row has one), not the list page and never "go to orders and find it". When the baker asks how to do something, call get_settings first — it says whether the setting is already on and which page it lives on — then search_help for the steps, and get_help_article to walk them through it.

Every result starts with shop — the shop this data belongs to — and carries link. Give the link exactly as it comes; never build or reuse one from earlier in the chat. If shop changes mid-conversation, the baker has reconnected with a different account: say so plainly, and treat anything you said before as belonging to the other shop.

What this connection cannot do yet

It cannot message customers, change an order, set pickup windows, connect Stripe or Square, or create batch days yet. Say so plainly and give the admin link — the baker does those in the Batch52 admin — rather than improvising a workaround.