Developers
Event Publisher capabilities
Supported publishing operations, copy behavior, and tasks that need the portal.
Audit date: 2026-10-25. Introduced in v3.13.0. Refresh the client's MCP tool list after deployment to discover the new tools. The public read-only event API is unchanged. All additions use the existing authenticated management API and Event Publisher authorization, not a second write API.
| Capability | API/MCP coverage |
|---|---|
| Event creation, editing, publishing | Existing tools retained; Stripe publication gates remain enforced. |
| Ticket-sale notification switch | create_event/update_event accept sale_notifications_enabled; event responses return it. No direct send operation. |
| Add-on management | List, create, update content/price/active state and eligible ticket types. Event responses include add-ons. |
| Replicate add-ons | copy_add_ons copies selected/all items and independent image files; preserves restrictions through explicit ticket mappings; refuses existing targets unless append is requested. |
| Multiple showtimes | create_showtime, update_showtime, and replicate_showtime through the portal's scheduling service. Replication copies the selected performance's ticket types with zero sales. No bypass of the initial orders/reservations gate. |
| Full-event duplication | duplicate_event uses the portal duplication service: copies every showtime, remaps ticket assignments, shifts dates, copies assets independently, and always creates a draft without orders/attendees/sales. |
| Ticket ordering | Set sort_order on create/update and read it back. |
| Unlock codes | Create event codes, read existing codes, assign/remove ticket code IDs. Foreign-event IDs and deleted codes are rejected. |
| Publication fields | Visibility, performers, featured flag, terms, and descriptive metadata can be edited and read back. |
| Existing image assets | Read primary/variant URLs and copy images with the existing tool; add-on copy includes its own artwork. |
| Event pagination | list_events exposes page so agents can traverse all results. |
| Partial schedule edits | Compare against stored dates when only one boundary is supplied; reject reversed sale windows and quantity ranges. Reject master schedule edits on multi-showtime events rather than silently ignoring them. |
Security and Copy Semantics
- Integration keys retain the Event Publisher scope. Scoped legacy user tokens also retain their account and assigned-event restrictions.
- Every source event, target event, add-on, showtime, ticket, and code is resolved inside the authorized event/account boundary.
- Copying is additive. It never replaces target add-ons, copies orders/sales, or reuses a source artwork filename. Missing ticket mappings fail closed.
- Database failures roll back copied records and clean up newly copied files.
- Existing read-only public API fields/routes are not changed.
Intentionally Still Portal-Only
This pass covers the publishing gaps above, not every management screen:
- Uploading/cropping new image binaries, including arbitrary remote-image fetch.
- Buyer-details/question-builder configuration, service-fee settings, and sharing control configuration.
- Creating/editing organizer profiles and venue records (the MCP can list and select them), and changing account-wide SMTP, Stripe, or other settings.
- Deleting events, tickets, add-ons, showtimes, or used access codes. Availability toggles and code assignment removal cover reversible publishing operations.
- Customer/attendee data, order administration, check-in, refunds, and payments. These remain outside the intended Event Publisher integration scope.
Agents should report these limits rather than claiming those operations succeeded.