Home · Organizer support · Organizer privacy policy

Build your Agenda with your AI app

Last updated: November 12, 2026

MultiTicketing lets your own AI app build and edit the Agenda of the Events you choose: Rooms, Sessions, Speakers and Tags, and nothing else. The app connects to MultiTicketing's MCP server at https://mcp.multiticketing.com/mcp. You sign in, say which Events it may work on, and from then on the app is a Connected Agent: it acts as you, on those Events only.

What a Connected Agent can and cannot do

• It reads an Event's Agenda: its days, time zone, Rooms, Tags, Tiers, Sessions and Speakers, with how many bookings and check-ins each Session has.
• At “Read and change the Agenda” it creates and changes Rooms, Sessions and Speakers, puts Tags and existing Tiers on Sessions, cancels and restores Sessions, and removes a Session nobody booked, a Room with no Sessions in it, or a Speaker.
• It writes a whole programme in one call, which lands completely or not at all. It reports every Room clash (two Sessions in one Room at once) and every refused row, row by row.
• At “Only read the Agenda” it reads and changes nothing.
• It cannot remove a Session that has bookings, check-ins, reviews or questions. That is refused, and it may cancel the Session instead.
• It never moves or un-schedules a Session that is Live, and never changes an Event that has ended (it can still read one).
• It never sets a Speaker's picture, and never touches people, invitations, messages, sponsors or reports.
• A second run of a corrected file changes only what changed. Nothing is removed because it was left out of the file.
• It reaches only the Events you named, and only while your role there still lets you connect an AI app and see the Agenda. It changes the Agenda only where your role lets you manage it. If your role there changes, the agent loses what your role lost at once.
• Every write is recorded as an Agent Change, which anyone who can manage the Event's Agenda can review and take back in the admin console.

Your AI app reads your file itself. MultiTicketing never sees the file, only what the app writes. What the app does with the Agenda it reads is your Organization's responsibility, as the Agent Declaration says.

Who can connect

You need a MultiTicketing account that is an Organization Admin or Owner, with at least one Event in that Organization. You can only name an Event where your role lets you connect an AI app and see its Agenda.

Which AI apps can connect

Claude and ChatGPT can connect. Other AI apps can't yet.

• Claude: a free Claude account is enough. On a Claude Team or Enterprise plan, an Owner of your Claude organization may need to add it first; then you choose Connect.
• ChatGPT: a Business, Enterprise or Edu workspace whose admin adds it, on the web only, not in the phone app.

Connecting

The admin console's Account page has a “Build an Agenda with your AI app” card with the address to paste, a Copy button and the steps for each app. The Agenda page of an Event links to it for anyone who may connect an agent there.

In Claude

1. Open Customize, then Connectors. Find MultiTicketing in the directory, or choose Add custom connector, name it MultiTicketing and paste https://mcp.multiticketing.com/mcp. The Add to Claude button on the Account page opens it already filled in.
2. Choose Connect. MultiTicketing opens: sign in, tick the Events Claude may work on, and connect.
3. In a chat, turn MultiTicketing on from the + menu, attach your file and ask Claude to build the Agenda.

In ChatGPT

1. On chatgpt.com, open Plugins, choose + and then Add custom MCP server.
2. Name it MultiTicketing, paste https://mcp.multiticketing.com/mcp, choose OAuth, accept the warning and choose Create as a plugin.
3. Install the plugin. MultiTicketing opens: sign in, tick the Events ChatGPT may work on, and connect.
4. In a chat, type @, pick MultiTicketing, attach your file and ask ChatGPT to build the Agenda. It asks you before each change.

The consent screen

The screen MultiTicketing opens shows which app is asking and where you will be sent back, who you are signed in as, and the Events you may name to it, grouped by Organization. Ended Events are folded at the bottom: the app can only read those.

You tick the Events, choose “Read and change the Agenda” or “Only read the Agenda”, and tick the Agent Declaration. The declaration states that you chose this app yourself, on behalf of the Organization of those Events, and that the Organization is responsible for what the app does with the Agenda's data. It is stored, word for word, with your Connected Agent.

Example prompts

Once it is connected, ask it for example:

• “Build the Agenda of my Event from this spreadsheet: its Rooms, Sessions and Speakers.”
• “I corrected the PDF timetable. Update the Agenda to match it and tell me every Room clash.”
• “Compare the Agenda in MultiTicketing with this document and list what differs, without changing anything.”

Managing your Connected Agents

The Account page lists every AI app you connected: its Events, whether it may change the Agenda or only read it, when it was connected and last used, and its status. A Connected Agent unused for 30 days ends by itself (“Unused for 30 days”). Each use pushes that day out.

Each one has its own page, where you can:

• switch it between “Read and change” and “Only read”, effective on its next call, with no new declaration;
• remove one Event from it, effective at once (removing the last one disconnects it);
• add Events, under a new Agent Declaration naming only those;
• read every Agent Declaration you made for it, in the language you made it in;
• disconnect it: its next call fails and the app asks you to connect again.

An Event you no longer may connect an agent to, or whose Agenda you no longer may see, reads “Out of reach: no longer allowed”. The agent cannot touch it until your role allows it again. What an agent wrote stays after it is disconnected, on each Event's Agent Changes page.

The Organization's view

Members who manage an Organization's members see every Connected Agent that touches the Organization's Events on its “Connected Agents” page, beside Members. For each one they see who connected it, the AI app, this Organization's Events only, its status, the date of its latest Agent Declaration and its last use.

They can cut off a Connected Agent: it loses every one of the Organization's Events at once, and goes on working on any other Organization's Events it names. Its person is not told; they see the Events gone on their Account page.

Reviewing and taking back an agent's work

Each Event's Agenda page links to its Agent Changes once there are any. The list shows every Agent Change, newest first: what it did (“Created 60 Sessions · Changed 9 Sessions”), when, the AI app, who connected it, and whether it was taken back. The edit page of a Session, Room or Speaker an agent wrote says which Agent Change last wrote it.

Opening an Agent Change shows every row it wrote, field by field: what the field held before, what the agent wrote, and what it holds now. Before you take it back, the page forecasts what “Would go back” and what “Would be left alone”, and why.

Taking back restores only what still stands exactly as the agent left it:

Anything else is left alone for a person to look at, for one of five reasons:

• the Session holds bookings, check-ins, reviews or questions;
• it was changed by hand since;
• a later Agent Change wrote it again (take that one back first);
• it was already removed by hand;
• a Room the agent created still has Sessions in it.

Nothing is canceled or moved on the system's own judgement. A take-back happens at once and completely. The Agent Change then reads “Taken back”, “Taken back in part” or “Nothing could be taken back”, with what went back and what was left alone. A taken-back Agent Change cannot be put back, other than by asking the agent again. Several ticked on the list are taken back newest first, so a later one never blocks an earlier one.

Anyone who can manage the Event's Agenda can take back any Agent Change; anyone who can see the Agenda can read them. The agent itself can take back only its own Agent Changes, and nothing on an Event that has ended.

Limits

So that one busy agent cannot slow down an Event for its Attendees:

• a Connected Agent makes at most 30 calls a minute and 300 an hour, 2 at a time;
• an Event takes at most 60 agent writes and 2,000 rows written an hour, across every agent, one write at a time;
• one call carries at most 1 MiB and runs at most 30 seconds; a document holds at most 200 rows.

A refused call writes nothing, and the agent is told which limit and when it clears. What people do in the admin console never counts.

Privacy

How MultiTicketing processes personal data is set out in the Privacy Policy.

Support

Write to info@redplanettribe.org.