Everything
it actually does.

Or just a link

The third way in, for the party that doesn't need a queue: anyone with the link. One address you paste into the group chat; whoever opens it puts their name and number in, is seated, and RSVPs themselves — no money, no approval, and you can still add people by hand. A name you already have on the list is seated and then sent through the sign-in door instead, so a shared link can never hand a stranger somebody else's record.

Signups are leads, never seats

A public form can never write to your guest list or spend your plan's guest allowance. Nothing is a guest until you approve it, and approving is the only door in.

It sends nothing on your behalf

Approving seats them and stops. No invitation goes out, no automatic welcome fires — invitations stay your explicit action, still behind the guest-list lock.

The sell, in your words

An intro above the form, a full markdown pitch beside it — headings, bullets, the price line — and your payment instructions after they've signed up. All three are yours to write, and the pitch stays in view while they're filling the form in.

A public info page

A second, deliberately separate page for strangers — everything a passer-by should know, without the one your confirmed guests read behind a login. A quiet "more info" door on the promo page, and a "not sure yet?" link under the form.

Your front door follows

While signup mode is on, your party site's own landing page is the promo page. A visitor who already holds a seat gets "enter the party" instead of the sign-up offer, so one address works for both.

Decline keeps the record

Turning someone down keeps their row, so if they sign up again they see where they stand rather than filing a fresh one. If the payment email failed, there's a resend button that says so.

Pause without breaking links

Switch the mode off and the public page is gone — genuinely a 404, not a "closed" notice — and your landing page reverts. The link keeps its address, so turning it back on revives every post you ever made.

Guarded

A honeypot, a per-address rate limit, length caps on every field, and one signup per email per party settled in the database rather than by a check that can race.

Running a paid event and not sure how it would fit? Ask us — [email protected]. It's a model we know well and we'll tell you straight if it isn't a fit.

05 — The guest dashboard

The page they'll
keep coming back to.

A ticket with their name on it, a countdown, their karma, and a tile grid to everything the party has going on. It changes as the party gets closer, and changes again once it's over.

• Three phases — hype, party day, afterglow — chosen automatically from the date, with wording you can rewrite per event.
• Party day runs to 6am, because the small hours belong to the party that's still going, not the morning after.
• Party-night blocks surface your DJ line-up and running order inline on the night itself.
• Quick vote panel appears on the night for guests who are coming, deep-linking straight to the right ballot.
• The wall — a comment box on the page itself, the first place guests write to each other rather than to you. "Who's on the 22:47 back?" "Chilli's on at nine."

Markdown pages

Write as many info pages per event as you like — travel, house rules, the line-up, the schedule — in markdown, edited in the admin.

Drip slots

Any page or poll can be given an opening time. Before it, guests see a locked teaser. Anticipation, scheduled.

Photo carousel

Point the dashboard carousel at this event's photos, the whole album, or one category of it.

Every page is a tile

A markdown editor per page with a slug, a title and an optional opening time. Every page gets its own tile on the dashboard and its own door in every themed world — and a page that hasn't unlocked yet gets a tile that says so, with its title withheld, so the surprise stays a surprise.

The wall

One comment box on the party page, per party, in the open. Nothing is deleted — a host or the author can hide a line, and only the host can restore one the host hid. Nothing notifies anybody, on purpose: it's somewhere to look, not something that goes off in forty pockets. A slur is refused at the form; anything borderline posts, and lands in a queue we read.

Who's coming

A live face wall of confirmed guests, with a running count of who's in and who's still deciding.

Event switcher

Guests invited to more than one of your parties can move between them from the dashboard — minus anything still locked.

Statistics page

A public-to-guests breakdown of the party: RSVP split, nights, dietary needs, drinks, gender balance and answers.

12 — Feeding them

How many, what,
and who's next
to whom?

Any party longer than an evening has to feed people, and the three things you need are never in the same place: how many are eating, whether there's enough, and who sits with whom. Lay out the sittings and the head count comes off the guest list itself — then lay out the room and the seating plan does the same.

• The party's days aren't its nights. A Friday-and-Saturday stay is two nights and three meal days, because somebody has to do the Sunday departure breakfast.
• Nobody ticks anything for the count to work: a guest staying only Saturday night is in for Saturday dinner and Sunday breakfast and out of Friday's, from their RSVP.
• “Four guests need vegan and nothing on this menu is marked vegan” is the line the whole thing exists to show you, before the day rather than on it.
• And the two people who must not be sat together are a hard rule, not a strong preference — which is the bit a spreadsheet has never once got right.

The head count shows its working

A sitting reads 22 confirmed · 6 presumed · 3 said no · 28 to cook for. A caterer needs to know how much of that number is a guess, so it's never collapsed into one figure. Extra covers add people who aren't on the guest list at all; an override replaces the lot when you simply know better.

Is there enough?

Give a dish a serves and it joins the maths; leave it blank for the bread, the sauce and the olives, which are real dishes nobody sizes. The desk flags a main that's short of the head count, per course, rather than shouting about the crisps.

Diets, the right way round

A tag says what a dish is suitable for, never what it contains — read backwards it tells a nut-allergic guest to eat the satay. The desk counts the needs among the people actually eating and names any one nothing on the menu answers.

Caterers where the suppliers live

A sitting can have one caterer, or every dish its own — which is how a food-truck rally works: three trucks, three dishes, one head count. Fees and booking status stay in Backstage with every other supplier, so nothing is typed twice.

Tables belong to the party

Lay the room out once — nine rounds of eight, a top table, the long trestle by the window — and every sitting draws on it. A table serves Saturday dinner and Sunday lunch the way a tent sleeps Friday and Saturday night.

It knows who knows who

A seating plan is proposed from partner links, who's sharing a room at this party, who's on a crew together, who's been to parties with whom and who's in the photographs with whom — with the reason against every guest in words, not a score.

Keep apart means keep apart

Not a heavy negative weight something can outvote. Two people on that list are never put at the same table, and a guest who then fits nowhere is left unseated so you find out — rather than finding out on the night.

Balance, not packing

Filling one table before opening the next is right for beds and wrong for dinner. Tables fill evenly, and a table with one person on it is treated as the failure it is. Use every table you've laid, or open only as many as you need.

Nothing saved until you say

Suggest, move anyone you disagree with, check it again, then apply — the same two steps as the bed plan, and for the same reason. Lock the pairings you're happy with and they survive every re-plan afterwards.

Copy it to the next sitting

A weekender lays the room once and eats in it six times. Copying only adds: anyone already seated keeps their seat, and anyone not eating at that sitting isn't dragged to it.

Guests see their own

Their table, what you wrote about where it is, and the names of the others on it — names only, nothing about what anybody eats. The party AI answers “where am I sitting?” the same way, and stays quiet if you haven't published the plan.

Only if you need it

A party with no meals has no Food tile. Two switches decide whether guests see the food at all and whether they answer for themselves, and a third whether they're told where they're sitting.

By chat and by API

Twenty endpoints and twenty assistant tools across food and seating: ask what's for dinner, add a dish, propose a whole room, apply it. Suggesting writes nothing — that stays a separate, deliberate call.

Just say what you want

Same bubble, bottom right, on both sides of the party.

Yours makes the changes. Theirs answers the questions — and acts on the answer, for the guest asking and nobody else.

It cannot message your guests

Not by accident, not if you ask it to, not if something in your guest list is written to look like an instruction. Sending isn't one of its tools, so there is no sequence of words that produces one — with one deliberate, bounded exception: it can invite one named guest, using one of your own stored templates, so it never composes a word that reaches anybody. A whole-list send is still yours to press. Nor is deleting a tool.

Everything it does, you can undo

That's what earns it the right to just get on with it rather than asking permission each time. Every change is reported with a link straight to the screen that shows it.

It only ever touches your account

Every id it uses is checked against your own parties, so a wrong guess is a polite "can't find that" rather than a look at somebody else's guest list.

Guests are asking, not instructing

Nothing typed into the guest bubble can change its brief or its boundaries, however it's phrased — and it's told your guests' own words are text to report on, never orders to follow.

No second setup

The guest bubble is the same party AI as the full chat page, so it inherits the same guest-safe boundary, the same throttle and the same offline fallback. If you've pointed your party at a WhatsApp concierge instead, the bubble stands down — one front door, whichever you chose. The thirteen themed home pages carry their own AI panel instead of it, each being a hand-built world of its own; every other page inside a theme gets the bubble, renamed.

And six more

Places it saves you an evening.

What the party AI is told

Only what that guest could already read on their own pages — plus their own RSVP. Never login links, never anyone's phone number, never the anonymous confessions. An info page you've scheduled to unlock later is left out too, so it can't spoil what the guest can't yet read.

It never goes dark

Several models are tried in turn, so a rate-limited one costs a guest a second rather than their question. If every one of them is down it answers from the event itself — when, where, who's coming, their RSVP, their jobs — instead of showing an apology.

It wears the theme

The chat page is reskinned by whichever guest theme is engaged, and all thirteen name it in their own voice — The Barman in the speakeasy, Race Radio at the Tour, Q Branch in the spy thriller. The persona underneath stays your party's, so it answers as your host would, under that world's name.

Composition, not generation

The planner's model returns a structured brief and we render the artefacts, so the CSS on your guests' pages and the placeholders in your messages are ours, not a model's. One call per generation, and you can re-roll until it's right.

Every AI feature is optional and keyed. No key, no feature — the rest of the system is unaffected, and a feature that can't run is hidden rather than offered and then failing. Image generation runs off the request path in a background worker, so an upload never waits on a model.

The hundred and thirty-five

Thirty a read-only connection can reach. A hundred and five that need full access.

The party itself

list_eventsget_eventget_event_contextget_event_setupget_event_statsget_rsvp_summarycreate_eventupdate_event_detailsset_invite_lock

Guests and RSVPs

list_inviteesget_inviteelookup_inviteesearch_inviteescreate_invitee_for_eventadd_existing_invitee_to_eventupdate_inviteeupdate_rsvpset_guest_rsvpremove_invitee_from_eventgenerate_login_link

Open signups

list_signupsdecide_signup

The date poll

get_date_pollopen_date_pollset_my_availabilitypick_date

Your notes on a guest

list_guest_tagsget_guest_tagsupdate_guest_tags

Jobs, crews and contacts

list_taskscreate_taskupdate_taskdelete_taskcomplete_tasktick_checklist_itemlist_crewscreate_crewupdate_crewdelete_crewlist_contactscreate_contactupdate_contactdelete_contact

The programme

get_schedulecreate_schedule_trackupdate_schedule_trackdelete_schedule_trackcreate_schedule_itemupdate_schedule_itemdelete_schedule_item

Where they sleep

get_accommodationcreate_accommodation_unitupdate_accommodation_unitdelete_accommodation_unitallocate_accommodationupdate_accommodation_allocationunallocate_accommodationlist_accommodation_requestsdecide_accommodation_requestrequest_accommodationcancel_accommodation_requestsuggest_accommodationapply_accommodation_plan

Food

get_mealsget_meal_attendancecreate_mealupdate_mealdelete_mealadd_meal_dishupdate_meal_dishdelete_meal_dishset_meal_attendancesubmit_meal_answer

Seating

get_seatingget_my_seatcreate_seating_tableupdate_seating_tabledelete_seating_tableset_seating_rulessuggest_seatingapply_seatingclear_seatinglock_seat

Activities & extras

get_activitieslist_activity_bookingscreate_activityupdate_activitydelete_activitybook_activitycancel_activity_bookingrecord_activity_payment

Getting there

get_my_travelget_travelget_travel_groupslog_travelupdate_traveldelete_travel

Polls and voting

list_pollsget_pollget_poll_resultscreate_pollupdate_polldelete_pollset_poll_settingssubmit_poll_responselist_voting_categoriesget_voting_resultscreate_voting_categoryupdate_voting_categorydelete_voting_categoryset_voting_settingscast_vote

Badges and karma

list_badgesget_badgelist_invitee_badgesget_invitee_karmaget_leaderboardaward_badgerevoke_badge

Pages, photos and renders

list_pagesget_pagewrite_pagewrite_info_pagedelete_pagelist_photosrequest_ai_renders

The guest chat queue

list_guest_chatsdecide_guest_chat

Just asking

ask_question

Pink ones need a full-access connection; the rest are offered to read-only ones as well. ask_question is pink because it hands the model a question to answer rather than fetching a fixed thing — it still changes nothing.

One account, always

A connection acts as exactly one account — yours — or it is refused. There is no deployment-wide key behind it that could reach anybody else's party, and every id an assistant hands back is checked against your own parties before anything happens.

It's the same server your guests use

These are the tools behind the party's assistant on the web, WhatsApp and Telegram, so a guest asking it to change their RSVP and you asking Claude to do it go through one implementation, not two that drift.

Nothing to install

The server is part of your party site, at yoursite/mcp. No extra process, no separate address, no gateway in between — it's live the day your site is.

Disconnecting is one click

Every connector holds its own key. Revoke it and that program stops; the rest carry on. Nothing an assistant ever held keeps working afterwards.