You already know your event. Now just say it.
Most ticketing platforms give you forms to fill in. Presso gives your AI a set of keys. Connect Claude once, then describe what you want in the same words you'd use to a colleague — and it happens in your account.
Software should do the admin, not hand it to you.
Running an event is a hundred small jobs. Set the tiers. Watch the sales. Notice the early-bird tier is nearly gone. Decide whether to open the next one. Check the payout. Reconcile it at month end. None of that is the reason you put on events, but it's where the hours go.
Every one of those jobs is a sentence before it's a screen. So we built Presso so the sentence is enough. Your AI reads your live sales and takes the action — the tier gets created, the report lands, the link comes back. You stay the one deciding.
Four steps, then it's just conversation.
Connect your AI
In Claude, add Presso as a custom connector and paste the endpoint we give you. That's the whole setup — no SDK, no developer, no integration project. Step by step here.
Say what you want
"How is the conference selling?" "Add a late release at £45." "Who has bought but not checked in?" No syntax to learn. Prompts that work well.
It interviews you, then acts
Setting up an event, it asks for the venue, the tickets, the prices and the refund policy one question at a time — because it is not allowed to guess any of them.
Nothing sells until you confirm
Publishing is the moment a stranger can be charged. Before it happens, your AI has to read every ticket name, price and quantity back to you and get a yes.
One sentence, then a conversation.
This is a real setup, shortened. Note what it does not do: fill in the gaps.
"A one-day conference called Staging Proof on 12 September, 9am to 5pm in London."
It asked four questions to get there, and refused to price a ticket you hadn't priced. The last step returned the link you share to sell.
It has keys to your account. So here's exactly what it can't do.
These are enforced on our servers, not requested in a prompt. A language model is not a security boundary, so we don't treat it as one.
It can't invent a price.
Every ticket needs a price you gave or an explicit "this one is free" — there is no default. Send neither and the server refuses the call. A guessed price is a price a stranger could be charged.
It can't publish quietly.
An event will not go live until it has a venue, a refund policy and real tickets — and then only when your AI submits the full price list back for checking. If what it submits doesn't match what's on sale, nothing publishes.
It can't see anyone else's events.
Your token is scoped to your account and nothing else. There is no shared context between organisers, so it cannot read another organiser's sales, buyers or payouts.
It can't touch your money.
Buyers pay your own Stripe account directly. Presso takes a flat 1% as the payment goes through and never holds your funds, so there is no balance for anything to move.
An open standard, not a chatbot bolted on.
Presso runs a Model Context Protocol server — the same open standard Claude uses to talk to any tool. Your account gets its own endpoint and its own token. There's nothing to install and no plugin to maintain, and if you'd rather use a different MCP client, it works there too.
Stop filling in forms about your own event.
Free until your first ticket sells. Connect your AI in about two minutes.