Read your box office, then create discounts and tickets as approved steps
Connect Ticket Tailor and Luumen can read your events, occurrences, discounts, checkout forms, and check-ins on request. Ask what sold, which codes are live, or who scanned in at the door. When something needs to change — a new discount code, a held seat, a comped ticket — Luumen shows the plan first and waits for your approval. Auth is DCR OAuth.
77 tools: 34 read, 43 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Ticket Tailor MCP run looks like inside Luumen.
Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — bundle create, bundle delete, bundle update, check in create, and more — is shown as a plan and requires approval by default, including the 31 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Ticket Tailor MCP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.