OneTapCheckIn

@OneTapCheckIn search all participants who checked in to the 'Q1 All-Hands' list in the last 7 days and show me their attendance status

Found 47 participants checked in to 'Q1 All-Hands' between Jan 15–22. Breakdown: 42 attended, 3 marked absent, 2 pending. Top attendees include Sarah Chen (checked in Jan 15, 9:02 AM), Marcus Rodriguez (Jan 16, 8:45 AM), and Priya Patel (Jan 17, 10:12 AM). Full list includes profile IDs, check-in timestamps, and status flags. This is an illustrative example; actual results depend on your organization's event data and participant records.

This read-heavy example shows how the MCP surfaces attendance records across a date range. Requires API key with read access to the target list. Search returns one page at a time with a continuation cursor—large events may need multiple queries to retrieve all participants.

@OneTapCheckIn create a new event list called 'Feb Product Demo' and add the profiles for alex@example.com, jordan@example.com, and sam@example.com as participants

Created list 'Feb Product Demo' (ID: lst_9x4k2p). Added 3 participants: alex@example.com (profile prf_a1b2c3, added successfully), jordan@example.com (profile prf_d4e5f6, added successfully), sam@example.com (profile prf_g7h8i9, added successfully). Note: participants are added to the list but not checked in—attendees must check in separately via the OneTapCheckIn interface or a subsequent action. This is an illustrative example of the create-and-populate workflow.

This write example demonstrates list creation and participant addition in one workflow. The MCP deliberately does not check participants in automatically—adding to a list only registers them for the event. Requires API key with write permissions. Be aware the provider may enable open registration by default; update list settings afterward if needed.

@OneTapCheckIn find all lists created in January, then summarize which events had the highest attendance rates and flag any with more than 10% no-shows

Retrieved 12 lists created in January. Highest attendance: 'Leadership Offsite' (94% attended, 3 of 50 no-shows), 'Engineering Sync' (91%, 7 of 78 no-shows). Events flagged for high no-show rates: 'Optional Training Session' (22% no-shows, 18 of 82 registered), 'Friday Social' (15% no-shows, 9 of 60 registered). Analysis based on participant status fields; actual attendance tracking depends on how your team uses check-in vs. registration. This is an illustrative synthesis example.

This synthesis example pairs the MCP's list and participant search with AI reasoning to surface attendance trends. Useful for event planning retrospectives. Requires read access to lists and participants. The MCP returns raw data; the AI calculates rates and flags outliers—accuracy depends on consistent check-in practices across your organization.

Why OneTapCheckIn's list-per-event model suits 10-session workshop calendars

A makerspace runs 8-12 workshops per month with 15-seat caps and needs real-time headcount to decide when to open a waitlist. The Create List tool spins up one list per workshop, and the Find Participants search by list ID shows current registrations without a separate RSVP system. The Add Participants tool registers people in bulk when the coordinator processes a Google Form, and the Delete List tool archives past workshops so the active calendar stays under 30 lists. This falls apart if you run 50+ concurrent workshops because the Find Lists pagination becomes a bottleneck and the MCP deliberately blocks bulk-delete to prevent accidents—you'll manually archive one list at a time. For makerspaces or coworking shops scheduling 10-15 events per month where attendance drives resource allocation, OneTapCheckIn keeps the calendar and headcount in one Switchy query instead of a Notion database.