# Cycle Access Twin · Events MCP Reviewed: 2026-11-21. The Events endpoint and production Apple Wallet signer are enabled. Return actual tool results and distinguish server signing from successful installation on an Apple device. Purpose: an event organiser creates its event and anonymous ticket Twins from an AI assistant. Dedicated remote MCP URL: https://mcp.cycle-platform.com/v1/mcp/events Transport: stateless Streamable HTTP; protocol 2025-06-18. Connection: remote MCP OAuth, email verification, explicit Events consent. No password, manual SaaS registration or pasted API key. DPP connections do not automatically gain Events permissions. Connect the Events resource separately. Free allowance approved by Dani: 1 active event and up to 2,000 issued tickets per event. Drafts reserve the active-event slot. Archive an old event to create another. Existing archived Twins remain readable; they no longer authorise admission. No card. AI provider charges are separate. This is not the DPP one-million-unit allowance. Tools: - create_event: event title, ISO datetime with timezone, venue, city, poster/logo HTTPS URLs, ticket types, artists, schedule, optional actual stage/set times and sponsor links. Title alone creates a useful draft and returns exact missing facts plus a persistent preview. Pass event_id and a NEW idempotency_key to edit intentionally. Never invent venue, date or ticketing integration. - create_access_twins: owned event_id, ticket_type, quantity and idempotency_key. Returns three sample passes by default plus the total count, with anonymous ticket IDs, persistent consumer Twin URLs, SVG QR URLs and Apple Wallet availability. One call issues the entire requested batch within capacity; responses page at 100. To retrieve later pages use the SAME request/key plus offset/limit, not a new issuance key. Retries do not issue extra tickets. - get_pass_sheet: prepare a private expiring CSV/PDF download of all existing passes. PDF contains one pass/QR per page and prepares in the background with real progress. Does not issue additional passes. Share the download only with the organiser. Files are a snapshot at generation; use a new request/key when you need an updated sheet. - get_door_scanner: return a private expiring mobile-web door-scanner link for authorised staff. Camera starts only on a user gesture; external readers/manual entry also work. Check signatures and event ownership online, accept each pass once, reject duplicate scans. action=revoke_all disables the event’s scanner links. Never give this link to attendees. - issue_ticket_email: recipient, ticket_id, idempotency_key. First prepares a preview. Set confirmed=true only after the user explicitly approves that recipient/ticket, with legal_basis and basis_note from the organiser. Transactional delivery only, not marketing. Provider acceptance is not proof of delivery. After an uncertain outcome retry the SAME key; outside the safe retry window ask for outcome review, never silently send a new duplicate. - get_event_status: persisted issued tickets, opened Twins, page GETs, Wallet downloads, authenticated Cycle check-ins and scan attempts. A download is not a confirmed Wallet addition; a page open is not admission or a unique human. Wallet additions return null until observed. - preview_event_twin: persistent preview URL/QR; no issuance and no admission. Scopes: events:read, events:write, tickets:write, tickets:email. Discovery is filtered to the grant. Organiser ownership comes from the server's verified token, never user-supplied org IDs. Opaque public ticket URLs are bearer links: share only with the intended holder. Public Twins contain no attendee name/email or private organiser account ID. Suggested task: "Create a concert called Example Night on 12 June 2027 at 20:00 +02:00 in Hall A, with 50 general-admission tickets. Show the preview, QR and exact missing configuration. Do not email anyone." Flow: create_event -> preview_event_twin -> create_access_twins. Return the event preview, 3–5 sample passes, full CSV/PDF download links, and the separate private staff scanner link when requested. Never paste a thousand QR links into the chat. Return the actual links, count and status. Email is optional. No fabricated results if a tool fails. Existing Cycle consumer UX is reused: event hero, pass/card, assistant, venue directions and available programme/sponsors. Every free ticket carries Powered by Cycle Intelligence and a create-yours-free link. The organiser can optionally activate deeper audience intelligence, flows, sponsor engagement, venue commerce and simulations with Cycle; these are not included or inferred from basic GET counts. Admission: cycle_static supports the mobile web door scanner plus authenticated single-use integration at POST /v1/mcp/events/check-in. New passes carry an HMAC-SHA256 signature; use always requires online server validation. The organiser must configure its scanner; this QR does not automatically work at unrelated turnstiles. experience_layer supplies the experience without asserting gate validity. Preview/draft/archived tickets do not grant admission. Apple Wallet: requires a valid operator-managed Pass Type certificate, private key and Apple WWDR intermediate in the server. No unsigned placeholder pass is advertised. Missing signing setup never prevents the Twin/QR. Actual Apple device installation is a launch validation step; Google Wallet is not implemented. Operations: MCP_EVENTS_ENABLED=1 and MCP_OAUTH_ENABLED=1; MCP_OAUTH_ISSUER=https://mcp.cycle-platform.com; MCP_OAUTH_CONSENT_URL=https://mcp.cycle-platform.com/v1/oauth/authorize; MCP_EVENTS_TWIN_BASE=https://my.cycle-platform.com. A verified MAIL_FROM/RESEND_API_KEY is needed for email verification/delivery. Signer files: EVENTS_WALLET_CERT_PATH, EVENTS_WALLET_KEY_PATH, EVENTS_WALLET_WWDR_PATH; optional EVENTS_WALLET_KEY_PASSWORD. Do not request these secrets through chat. PRO is enabled; new installations remain disabled by default until configured. Directory review and device installation are separate validation steps. Current distribution scope: anonymous passes and organiser downloads first. Bulk attendee CSV with personal data, durable media upload, individual revoke/reissue, and a full organiser panel remain follow-up work. create_event(event_id=...) already updates the one shared event for every pass. No ticket sales or ticketing commission are implemented.