Presso Events
First £50 of fees on usSign inConnect your AI →

Presso Eventsconnect your AI

The connector

Add Presso Events to your AI. Then describe your event.

Presso Events runs an MCP server. Connect it once to the assistant you already pay for and everything after that is a sentence. About five minutes, no card, nothing to download.

Prefer clicking? Create your account and use the portal - both doors reach the same place

One click

Install for Claude.

This opens Claude's add-connector dialog with the Presso Events URL already filled in. Press Add, then follow the three steps below to get your token.

Add Presso Events to Claude →

works in Claude Desktop and claude.ai

Add custom connector
Name
Presso Events
Connector URL
https://mcp.presso.events/mcp
AddCancel
Other clients

Anything that speaks MCP.

Same server, same tools. You bring the assistant; we bring the ticketing.

One command in your terminal.

Adds Presso Events to Claude Code over HTTP. Run it in any project - the connection follows your account, not the folder.

CLI clients in full →
claude mcp add --transport http presso-events https://mcp.presso.events/mcp
Getting your token

Sign in once, then reconnect with the token.

The connector is deliberately almost useless until it knows who you are. This is the exchange that fixes that.

1Ask your AI to create your organisationWith no token yet, the connector offers exactly one tool - create_organisation. Give it your name, your email and your organisation name.
2Approve the one-time passwordless sign-inYour AI receives a scoped connector token (it starts pev_). Already registered? For security no token is issued - sign in at Presso Events to recover access.
3Re-add the connector with the tokenThis time as a Bearer token (Authorization: Bearer pev_...). That unlocks the full toolset - create events, ticket types, invite your team, publish. Reconnect whenever your AI needs the full toolset.

The long version, per client, is in the setup guide

Then point it at Stripe

Your account, not ours.

Connect the Stripe account you have, or create one during onboarding. You are the merchant of record on your own account: payouts, tax settings and the money itself live there, and our 1% comes off in transit.

  • Cards, wallets and 3D Secure handled by Stripe
  • We take the platform fee on the way past and never hold funds
  • Disconnect whenever you like - the account stays yours
Presso · Stripe
Accountconnected
Payouts toyour bank
Held by Presso£0.00
Platform fee1%
Your first message

Say what you are running.

Paste this and answer the questions it asks. It sets the event up as a draft, then stops and waits for you before anything can be sold.

You are connected to Presso Events.
1. Confirm the connection and tell me what you can do.
2. Ask me about my next event - one question at a time.
3. Create it as a draft with the ticket tiers, read the full price list back to me, and wait for my go-ahead before publishing.
Browse the prompt library →
Once connected

All 24 tools, generated from the live server.

You never call these by name - you describe what you want. They are listed because a page that claims a capability should be checkable against the thing that provides it.

add_sessionAdd ONE session to an event's agenda.
add_speakerAdd ONE speaker to an event.
buy_linksPermanent links you put on YOUR OWN website's buy button.
check_in_ticketCheck in an attendee at the door using the check-in code on their ticket (six characters, shown as 7HK-2M9 - hyphen, spaces and case are ignored, and I/L are read as 1 and O as 0).
create_eventStart a new event for this organiser.
generate_checkoutCreate a hosted Stripe Checkout link for a PAID ticket type on one of your published events, for ONE buyer's purchase.
get_agendaRead an event's whole agenda: sessions grouped by day (in the event's OWN timezone, not UTC), each with its speakers and their roles, plus the full speaker list.
get_analyticsTicket volume across every event you own: valid tickets issued per day for the last N days (default 30), broken down by ticket type and by event.
get_attendeesWho holds a ticket, and moving one to somebody else.
get_revenueWhat you have sold, one entry per currency: gross, Presso's 1% fee, net of that fee, orders, refunds and disputes.
issue_free_ticketIssue a FREE ticket to an attendee by email (for a pricePence-0 ticket type).
list_eventsYour events.
publish_eventPublish an event, moving it from 'draft' to 'published' so its ticket links and attendee app go live.
record_event_setupRecord what the organiser has TOLD you about an event: venue, refund policy, expected attendance, on-sale dates.
remove_sessionRemove ONE session by its 'ref'.
remove_speakerRemove ONE speaker by their 'ref'.
set_agendaWrite an event's WHOLE agenda in one call.
set_event_capacitySet how many people an event's venue holds, as a hard limit across ALL ticket types together.
teamYour team: who can sign in to this organiser and what they can do.
ticket_typesWhat one of your events sells, and how to change it.
update_event_configUpdate an event's presentation: tagline, description, branding (colours, logo), which optional sections the attendee app shows (agenda, speakers, venue, sponsors, faq), and their content.
update_organiserSet the organisation's PUBLIC identity: display name, description, location, website, logo and brand colours, plus whether the public profile page is visible.
update_sessionUpdate ONE session by its 'ref'.
update_speakerUpdate ONE speaker by their 'ref'.

Generated from docs/tool-catalogue.json ·the full reference, with arguments

Five minutes

Connect it, then talk to your event.

Add to Claude →Use the portal instead

https://mcp.presso.events/mcp