Wallet passes.

Wallet passes

Design an Apple Wallet pass from an MCP client, hand it out by link or QR code, and keep talking to everyone who added it. Each person who opens the link gets their own pass, so you can message all holders at once or update one holder's values, such as a points balance or a seat.

Operations

• create_wallet_pass: design a pass (generic, store card, event ticket or coupon) and get a code, install link and optional QR code.
• issue_holder_pass: pre-issue a personal pass for one known person, with their own field values.
• list_wallet_passes: list your passes with holder and device counts.
• get_wallet_pass_activity: inspect holders, installs, device registrations, pushes and updates.
• send_wallet_push: put a message on the lock screen of every holder, or one holder.
• update_wallet_pass: change the design or a holder's values, silently or with a notification.
• revoke_wallet_pass: void every pass, or one holder's pass.

Messages arrive on the lock screen in about one to two seconds for online devices. Apple Wallet on iPhone only; holders need Wallet notifications and Automatic Updates on.

Access and data

Jetski Auth with email verification and password signup. Every caller can only see and change the passes they created. Allowances: 20 new passes per UTC day, 1,000 holders per pass, and 60 pushes or updates per pass per hour. Pass data is stored in Cloudflare D1; artwork you supply is copied into Cloudflare KV.

Create an Apple Wallet loyalty card for "Bean & Co": store card style, dark green, a POINTS header field starting at 0 and a MEMBER primary field. Give it a QR barcode with BEAN-{ref}, and return the install link with a QR code.