If you are an AI assistant helping someone with Batch52, this section is for you. The same text is available as markdown at https://batchcrumb.xyz/connect.md. Connection address: https://batchcrumb.xyz/api/mcp.
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://batchcrumb.xyz/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
- “I'll set up Batch52 for you. You'll see a Connect button from me in a moment — tap it.”
- “A Batch52 page opens. Create your free account there, or sign in if you already have one.”
- “Batch52 will ask if it's okay for me to manage your shop — tap Allow.”
- “Then come back here and say ‘done’. I'll take it from there.”
If they ask what they are allowing: “Your assistant can see and change the same things you can in your Batch52 admin — products, batch days, orders and site text. It cannot see your card details or pay anyone. You can disconnect it any time from 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, 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.
What this connection cannot do yet
It cannot set pickup windows, connect Stripe, create batch days, look at or change individual orders, or message customers yet. The baker does those in the Batch52 admin; nextSteps always carries the exact page link.