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.

Install it What to say first

Add custom connector

Name: Presso Events
Connector URL: https://events.pressonetwork.com/mcp
Sign-in: OAuth, passwordless, the first time it connects

Add Presso Events to Claude (opens in a new tab)

01Install

Pick your AI.

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

In Claude

Open the add-connector dialog
This opens Claude's add-connector dialog with the name and address already filled in. Works in Claude Desktop and claude.ai.
Add Presso Events to Claude (opens in a new tab)
Or paste the address yourself
In Settings, then Connectors, choose Add custom connector, name it Presso Events and paste this.
https://events.pressonetwork.com/mcp
Press Add, then sign in
Passwordless, with the email you want the tickets and payouts under. The first sign-in creates your organisation.
Connect Stripe
Payouts are Stripe's, so ticket money lands in your own account.
Ask for your first event
Set up my first event on Presso Events

In ChatGPT

Open Plugins and add a custom MCP server
Custom MCP servers are available on ChatGPT Business, Enterprise and Edu, on the web. Open Plugins, select the plus button, then Add custom MCP server. You do not need developer mode first.
Paste the address and choose OAuth
Tick I understand and want to continue, then Create as a plugin. If your ChatGPT still shows Apps rather than Plugins, the older route is Settings, then Apps, then Create.
https://events.pressonetwork.com/mcp
Ask an admin if you need to
On Business, only workspace admins and owners can create and publish one. On Enterprise and Edu, an admin can let selected members create one, and only an admin or owner can publish it for the workspace.
Sign in and connect Stripe
It asks you to sign in the first time you use it. Card checkout happens on Presso Events, not inside the chat.
Ask for your first event
Set up my first event on Presso Events

In Claude Code

Run this once in your terminal
It adds Presso Events to Claude Code over HTTP. Run it in any project: the connection follows your account, not the folder.
claude mcp add --transport http presso-events https://events.pressonetwork.com/mcp
Sign in when it asks, then connect Stripe
Your assistant opens a Presso Events sign-in window the first time it connects. Nothing to paste and no token to find.

In Cursor

1
Drop it in your MCP config
Add the server to your Cursor MCP settings and reload. It works the same in Windsurf and other editors.
```
{
  "mcpServers": {
    "presso-events": {
      "url": "https://events.pressonetwork.com/mcp"
    }
  }
}
```
Sign in, then connect Stripe
Same server, same tools: the sign-in window opens the first time it connects.

In Other MCP clients

Point it at the address
Streamable HTTP transport with OAuth. Codex, Gemini, Windsurf and anything else that supports remote MCP servers takes the same URL.
https://events.pressonetwork.com/mcp
Restart, sign in, connect Stripe
The server answers an unauthenticated call with a sign-in pointer and your client takes it from there. An existing Bearer pev_ token also works.

02Signing in

The connector is deliberately almost useless until it knows who you are. Signing in is what fixes that, and your assistant handles the rest of it without you.

Add the connector
Your assistant opens a Presso Events sign-in window the first time it connects. Nothing to paste and no token to find: the two ends arrange it between themselves.
Sign in, or create your account there and then
Passwordless, with the email you want the tickets and payouts under. First time through, Presso creates your organisation from that address, so there is no separate sign-up to do first.
Describe your event
The full toolset is available immediately: create events and ticket tiers, invite your team, publish, check people in at the door. You will not need to reconnect.

03Then 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 the platform fee comes off in transit.

Cards, wallets and 3D Secure handled by Stripe
Presso never holds your funds
Disconnect whenever you like: the account stays yours

Presso · Stripe
Account	connected
Payouts to	your bank
Held by Presso	£0.00
Platform fee	1%

04Your 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.

Build a prompt for any job

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.

05Once connectedSnapshot 01/11/2026

All 44 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_session: Add ONE session to an event's agenda.
add_speaker: Add ONE speaker to an event.
add_stage: Add ONE stage to an event.
archive_event: Archive an event: hides its page and stops sales.
assign_session_stage: Put one session on a stage, by their refs.
buy_links: Permanent links you put on YOUR OWN website's buy button.
cancel_event: Cancel an event that is not going ahead: stops all sales, refunds every paid ticket in full to the card used, cancels free tickets and emails every ticket holder once.
check_in_ticket: Check 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).
check_in_without_code: Admit an attendee who cannot produce their check-in code, using a ticketId that find_attendee returned.
connect_status: Whether the organiser can take money yet, and what is outstanding if not.
create_event: Start a new event for this organiser, as a private draft that is NOT sellable yet.
delete_event: Delete a DRAFT event that never had a ticket issued - a duplicate or a false start.
download_guest_list: Called by the door screen itself when the operator presses Download list: a 15-minute private link to one event's guest list as Excel, CSV or an A4 tick sheet, delivered to the screen only.
find_attendee: Find one person at the door by name when their ticket will not scan - a flat battery, a lost email, a phone that will not load.
generate_checkout: Create a hosted Stripe Checkout link for a PAID ticket type on one of your published events, for ONE buyer's purchase.
get_agenda: Read 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_analytics: Ticket 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_attendees: Who holds a ticket, and moving one to somebody else.
get_door_board: Opens the door screen for one event: the guest list to tick people off, a box to type a ticket's check-in code, and the live count.
get_revenue: What you have sold, one entry per currency: gross, platform fee, net, orders, refunds and disputes.
issue_free_ticket: Issue a FREE ticket to an attendee by email (for a pricePence-0 ticket type).
list_events: Your events.
list_stages: List the stages on one of your events, in timetable column order.
publish_event: Publish an event, moving it from 'draft' to 'published' so its ticket links and attendee app go live.
record_event_setup: Record what the organiser has TOLD you about an event: venue, refund policy, expected attendance, on-sale dates.
refund_order: Refund an order, in full or in part.
remove_session: Remove ONE session by its 'ref'.
remove_speaker: Remove ONE speaker by their 'ref'.
remove_stage: Remove ONE stage by its 'ref'.
request_image_upload: Get a private link the organiser opens to upload ONE image - a speaker photo, the event's own photograph, an event logo, a sponsor's logo, or the organiser logo.
send_feedback: Send the Presso Events team feedback from this organiser: a bug, an idea, something confusing, or something that worked well.
set_agenda: Write an event's WHOLE agenda in one call.
set_door_policy: The two door decisions only an owner can make, per event.
set_event_capacity: Set how many people an event's venue holds, as a hard limit across ALL ticket types together.
sponsors: The sponsors of one event: name, tier, website, logo and display order.
team: Your team: who can sign in to this organiser and what they can do.
tick_off_ticket: Called by the door screen itself when the operator ticks a guest on its list of valid tickets for an event: checks that guest in and records it as ticked off the list.
ticket_types: What one of your events sells, and how to change it.
update_event_config: Update 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_event_details: Change an event's name, dates, times, timezone or venue, on a draft or a live event.
update_organiser: Set the organisation's PUBLIC identity: display name, description, location, website, logo and brand colours, plus whether the public profile page is visible.
update_session: Update ONE session by its 'ref'.
update_speaker: Update ONE speaker by their 'ref'.
update_stage: Update ONE stage by its 'ref'.

Five minutes

Connect it, then talk to your event.

Install it See how it works

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

Pick your AI.

In Claude

Open the add-connector dialog

Or paste the address yourself

Press Add, then sign in

Connect Stripe

Ask for your first event

In ChatGPT

Open Plugins and add a custom MCP server

Paste the address and choose OAuth

Ask an admin if you need to

Sign in and connect Stripe

Ask for your first event

In Claude Code

Run this once in your terminal

Sign in when it asks, then connect Stripe

In Cursor

Drop it in your MCP config

Sign in, then connect Stripe

In Other MCP clients

Point it at the address

Restart, sign in, connect Stripe

Sign in once. That is the whole setup.

Add the connector

Sign in, or create your account there and then

Describe your event

Your account, not ours.

Say what you are running.

All 44 tools, generated from the live server.

Connect it, then talk to your event.