Build booking and CRM apps.
Without rebuilding operations.

A · Merchant setup

One-time merchant setup. Fully MCP-native — same tool surface as the customer flow.

1. 01 create_service_category({ name }) — Optional grouping ("Treatments", "Classes").
2. 02 create_service({ name, durationMinutes, price, capacity, categoryId? }) — Define a bookable service. Add cancellationPolicy / requiresStaff / requiresResource as needed.
3. 03 set_staff_availability({ memberId, dayOfWeek, startTime, endTime }) — Weekly working hours per staff member. Use date instead of dayOfWeek for one-off changes.
4. 04 create_resource({ name, type }) + set_resource_availability(...) — (Optional) For room/equipment-bound bookings.

B · Customer flow

Customer-facing storefront. Works via MCP tools, SDK, or raw REST.

1. 01 list_services — Render service cards with name, price, duration, capacity.
2. 02 get_service_detail(serviceId) — (Optional) Show prep notes + cancellation policy on the detail page.
3. 03 get_available_slots(serviceId, { startDate, endDate }) — Render date picker + open times. Returns [] if fully booked.
4. 04 create_booking({ serviceId, slotTime, participants, customer }) — Confirm booking. Returns booking ID + status.
5. 05 cancel_booking({ bookingId, reason? }) — Cancel flow. Server checks policy + computes refund eligibility.

A · Merchant setup

Optional content-model setup. Skip if the default post type fits.

1. 01 create_category({ name, slug? }) — Organize posts ("News", "Tutorials"). Skip if you only need a flat blog.
2. 02 create_post_type({ key, label }) — Define a custom content type beyond the default `post` (e.g. `case_study`).
3. 03 create_post_type_field({ postTypeId, key, label, fieldType }) — Add typed custom fields (text, number, image, etc.) to a post type.

B · Customer flow

Author + render flow. Fully MCP-native — no REST fallback needed.

1. 01 create_post({ type, title, slug?, blocks }) — Create a post with starting blocks. Slug auto-generated from title if omitted.
2. 02 append_post_block({ postId, type, props }) — Append heading / paragraph / image / button / divider / video / gallery / form blocks.
3. 03 update_post({ postId, status: "published" }) — Flip from draft to published when ready.
4. 04 list_posts({ status: "published", categoryId?, limit, offset }) — Storefront index page.
5. 05 get_post({ slug }) — Storefront single-page view. Returns post + ordered blocks array.

A · Merchant setup

Provision the catalog + audience once. Fully MCP-native.

1. 01 create_product_category({ name }) + create_product({ name, price, ... }) — Build the shop catalog. Use list_product_categories first if you want to attach to existing groups.
2. 02 list_customer_segments + create_customer_segment(...) — Define audience segments (VIP, recent buyers, lapsed) for campaign targeting.
3. 03 create_promotion({ name, code, type, value, ...channelFlags }) — Create promo / coupon codes. Toggle bookingEnabled / onlineEnabled / posEnabled to scope.
4. 04 create_service + set_staff_availability — See Wedge 01 for booking-side setup.

B · Customer flow

Daily ops + marketing automation. All MCP-native today (campaign send still REST — see edge cases).

1. 01 list_bookings({ status: "confirmed", date }) + list_orders({ status: "pending" }) — Daily dashboard / fulfilment queue.
2. 02 create_shop_order({ accountId, items, promotionCode? }) — Create orders programmatically (e.g. from a chat agent or quote-to-order flow).
3. 03 validate_promotion({ promotionCode, channel, amount }) — Pre-check coupon at checkout — returns isValid + discountAmount.
4. 04 create_campaign({ name, channel, recipientSource: "segment", segmentId, channelConfig }) — Stage an email/SMS/WhatsApp campaign in DRAFT.
5. 05 POST /v6/merchant/campaigns/{id}/send — Trigger send (REST only — MCP send tool needs queue binding, coming next).