ticket-generator-mcp

Generates a ticket for a given event and returns the ticket ID (as text) along with its QR Code as a rendered image (PNG). Optionally pass a ticket category and image width.

Returns a URL to the rendered QR Code ticket for the specified event (and optional category). You can optionally override up to 5 variable fields on the ticket design.

Sends a generated ticket to a recipient via Email, SMS, or WhatsApp. You can include subject, body, and sender details, along with up to 5 custom variable fields.

Return the details (name, description, start date, end date, location, ticket categories, etc.) of all active events associated with your account.

V2: List your events with cursor pagination. Optionally filter by status and event start date range. Returns a page of events plus a next_cursor to fetch the following page.

V2: Create a new event. Requires a name and an ISO 8601 start date (must be at least ~15 minutes in the future, UTC). Returns the created event details, including the event's eventType (may be null when not set).

V2: Get the full details of a single event you own (works even for cancelled/expired events).

V2: Partially update an event (any of name, date, end_date, venue, description, eventType, timezone). Unchanged payloads are a safe no-op.

V2: Cancel an event (soft cancel; ticket records are preserved). Fails if any ticket for the event has already been scanned/checked in.

V2: Get lightweight stats for an event: capacity, tickets issued/sent/cancelled, checked-in count and attendance rate.

V2: List an event's attendees (tickets) with cursor pagination. Optionally search by name/email/phone and filter by delivery status. Returns a page plus next_cursor.

V2: Get a single attendee/ticket detail including the live ticket URL, QR data and check-in state.

V2: Correct an attendee's details (any of name, email, phone). Data-only update; it does NOT resend the ticket. At least one field must be provided.

V2: Re-send an existing ticket to the attendee over a channel (email, sms or whatsapp). Does not create a new ticket or consume credits. The attendee must have a destination on file for the chosen channel.

V2: Cancel/invalidate a single attendee ticket for check-in. The ticket record is preserved. Fails if the ticket was already scanned/checked in.

V2: List an event's check-ins (validated tickets) with cursor pagination, newest first. Optionally filter by check-in time range. Returns a page of {ticket_id, name, check_in_time, check_in_count, entry_point} plus next_cursor.

V2: Get the current validation status of a single ticket (valid, used, cancelled or expired) with its check-in count and last check-in time.

V2: Get structured analytics for an event: attendance_rate and delivery_rate (decimals), delivery_by_channel (email/sms/whatsapp), hourly check_in_timeline and failed_deliveries_count.

V2: Get a full per-attendee report for an event with delivery + check-in data. Returns JSON by default, or a CSV document when format is "csv".

V2: Get cross-event analytics for your account: total_events, total_tickets, avg_attendance_rate, tickets_by_channel and a per-event attendance_rate list. Optionally filter by event start date range and group_by week/month.

V2: Register a webhook endpoint to receive signed event notifications. Provide a https URL and one or more event types. A signing secret is returned ONCE in the response (store it to verify the X-TG-Signature HMAC-SHA256 header).

V2: List your account's active webhook registrations (signing secrets are never returned).

V2: Delete (deactivate) a webhook registration so it stops receiving deliveries.