Run Sweescape from Claude or ChatGPT

The Sweescape connector links your AI assistant, Claude or ChatGPT, to your account. You describe what you want in plain language, and the assistant reads your events and statistics or prepares the work for you: event, tickets, codes, ticketing page, campaign. It relies on the MCP protocol (Model Context Protocol), supported by both assistants.

The principle: the assistant prepares, you open the doors. Nothing it creates reaches a buyer until you publish the ticketing page yourself in Sweescape.

Connect your assistant

1. In the Claude or ChatGPT settings, open the connectors section and add a custom connector.

2. Paste the address of the Sweescape MCP server: https://mcp.sweescape.com/mcp.

3. The assistant opens a Sweescape page titled Authorize a third-party application. Enter the Email and Password of your Sweescape account.

4. Click Authorize. You return to your assistant, connected.

If the email or password is wrong, the page shows “Invalid email or password.”. Deny cancels the connection.

Where exactly the connector settings are depends on your assistant and its plan. The connector does not use the AI credits of your Sweescape plan: your assistant does the work.

What the assistant can do

The assistant acts with your account, on your data only.

Look up

• Your events: the list (upcoming, past, search by name or date) and an event’s details (dates, venue, number of attendees, VAT rate).
• Your account: your plan, your SMS credits, your usable Stripe accounts and your verified sending domains.
• Your tickets: tax-inclusive price, quota, tickets sold and left, per-order limits, visibility.
• Your discount and access codes, with their quota and usage.
• Your ticketing page: published or not, and its content.
• Your custom domain and the DNS record to create.
• Your automations and the content of your campaigns, your audiences (name and size, never the contacts) and your senders.
• An event’s statistics: the conversion funnel, visits and their sources, the check-in summary.
• Your extensions, those of the marketplace and those installed on an event.

Prepare

• Create an event with ticketing: name, full postal address, dates, VAT rate and an active Stripe account of yours.
• Duplicate an event for the next edition: tickets, columns, badge, invitation and ticketing page are copied, and the page arrives unpublished. The copy keeps the original venue and gets placeholder dates (the day after and two days after the duplication): correct them in Sweescape.
• Add a ticket: tax-inclusive price, quota, minimum and maximum per order, ticket hidden behind a code. A ticket cannot be edited or deleted afterwards from the assistant: check the price and quota before confirming.
• Create a discount code or an access code, on one event or shared across several, and change the events of a multi-event code.
• Build the ticketing page as long as it is not published: the assistant knows every page editor block.
• Connect a custom domain and check its DNS.
• Prepare an automation or a campaign as a draft, email or SMS, with its content.
• Create an extension, upload its files and write its manifest.

Your plan’s limits apply: if an action requires a higher plan, the assistant tells you which one.

What the assistant will never do

• Publish a ticketing page. It even refuses to edit a page that is already published: a live ticketing page only changes through you.
• Activate or deactivate an automation.
• Send a campaign.
• Install, activate or publish an extension.
• Delete anything.
• Sell, refund, or change a payment.
• Read the personal data of your attendees and buyers: statistics are aggregated.
• Edit an existing event or ticket, or your account configuration (Stripe, billing, collaborators).
• Edit your audiences.

Sample requests

• “List my upcoming SUBSOL events and tell me how many tickets are left for SUBSOL #15.”
• “Duplicate SUBSOL #15 under the name SUBSOL #16.”
• “Create the event SUBSOL #16 on Saturday November 14, 2026 from 11 PM to 6 AM, at 12 rue de l’Exemple, 75011 Paris, 20% VAT, with an Early bird ticket at €12 (100 spots) and a Normal ticket at €18 (300 spots).”
• “Create a SUBSOLVIP code for 20% off SUBSOL #16, usable 50 times.”
• “Prepare the SUBSOL #16 ticketing page in black and acid green, with the line-up, practical info and a clearly visible buy button.”
• “Analyze the SUBSOL #15 statistics: where do my visitors come from and at which step do they drop off?”
• “Write a draft email campaign for the SUBSOL audience announcing that tickets for #16 are on sale.”

After a preparation, open Sweescape to review the result, then publish or send yourself.

Always review

An AI assistant can make mistakes: price, date, ticket name. Check in Sweescape what it created before publishing the page or sending a campaign.

Security

• OAuth sign-in. You enter your password on the Sweescape page, not in the assistant, and the connector does not store it.
• Access limited to your account. Every action runs with your identity: the assistant can neither see nor change another account’s data.
• Short sessions. Access renews automatically every hour. If you do not use it for 30 days, you need to sign in again.
• Revocable access. Remove the connector in your assistant’s settings to cut access at any time.
• Data shared with the assistant. The connector’s answers are processed by your assistant’s provider (Anthropic for Claude, OpenAI for ChatGPT), under its own privacy rules.