How the AI works

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 it once, then describe what you want in the same words you would use to a colleague, and it happens in your account.

See how to connect →

Tools your AI can call

Standard

MCP, not a bespoke plugin

Token

Scoped to you, revocable

Fee

Flat 1%, straight to your Stripe

Why

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 is where the hours go.

Every one of those jobs is a sentence before it is 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.

The shape of it

Four steps, then it is just conversation.

01 · two minutes, onceConnect your AIIn Claude, add Presso as a custom connector and paste the endpoint we give you. That is the whole setup - no SDK, no developer, no integration project. Step by step here.

02 · your wordsSay 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.

03 · it asks firstIt interviews you, then actsSetting 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.

04 · before it goes liveNothing sells until you confirmPublishing 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.

Enforced on our servers

It has keys to your account. So here is what it cannot do.

These are enforced on our servers, not requested in a prompt. A language model is not a security boundary, so we do not treat it as one.

It cannot 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 cannot 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 does not match what is on sale, nothing publishes.

It cannot 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 cannot 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.

The standard

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 is nothing to install and no plugin to maintain, and if you would rather use a different MCP client, it works there too.

The full connection guide →

Getting started

Stop filling in forms about your own event.

Free until your first ticket sells. Connect your AI in about two minutes.

Connect your AI →Use the portal instead