# Hipsy MCP MCP > Hipsy lets you manage event ticketing, registrations, and revenue streams entirely through your AI agent. Instead of jumping between dashboards to check sales data or attendee lists, you ask your client for a full picture—from listing upcoming festivals to auditing total revenue for the quarter. ## Overview - **Category:** ecommerce - **Price:** Free - **Tags:** ticketing, event-registration, attendee-check-in, revenue-reporting, event-analytics, sales-tracking ## Description Managing an event's lifecycle used to mean opening multiple tabs: one for ticket sales, another for attendance logs, and yet a third just for financial reports. Now, connect Hipsy via Vinkius and let your agent handle it all through natural conversation. You can ask the system to check overall organization details or list all events happening next month. Need to know how much money came in? The agent retrieves total revenue broken down by event. If you're worried about last night’s crowd, you can review scan entries and get real-time attendance statistics. It's like having a dedicated ops analyst sitting on your shoulder, ready to answer any operational question instantly. ## Tools ### check_hipsy_status Verifies the connection status between your agent and Hipsy's platform. ### get_event_revenue Calculates and reports the total revenue generated for one particular event. ### get_event Retrieves specific, detailed information about a single event by its ID. ### get_order Provides full details on a single ticket purchase, including buyer information and payment status. ### get_organisation Pulls general profile data for the event organizing entity. ### get_scan_stats Generates aggregate statistics on ticket scanning, such as total scans and scan rates. ### list_attendees Lists all registered attendees for an event so you can check their current status. ### list_events Provides a comprehensive list of every event recorded in the system. ### list_orders_by_event Filters and lists only the orders that are tied to a specific event ID. ### list_orders Retrieves a master list of all ticket orders across the entire platform. ### list_organisations Lists all existing organizations that run events through Hipsy. ### list_past_events Retrieves a list of all event records that have already occurred. ### list_scans Provides a raw, chronological list of every ticket scan entry recorded at an event. ### list_ticket_types Lists all available ticket categories for an event, including their specific price points and availability counts. ### list_upcoming_events Shows a list of events scheduled to happen in the future. ### list_webhooks Displays all webhook endpoints that have been configured for automated data pushes. ## Prompt Examples **Prompt:** ``` Show all upcoming events and the ticket sales for the next one. ``` **Response:** ``` 4 upcoming events: 1) 'Summer Music Festival' — Jul 15, 2025 (event_301, Venue: Park Stage). 2) 'Tech Meetup Amsterdam' — Jul 22 (event_302). 3) 'Outdoor Cinema Night' — Aug 5 (event_303). 4) 'Food & Wine Fest' — Aug 18 (event_304). Ticket sales for 'Summer Music Festival': 3 ticket types: Early Bird (€25, 200/200 sold — SOLD OUT), Regular (€40, 142/300 sold), VIP (€85, 28/50 sold). Total orders: 370. Revenue: €18,430. Would you like to see attendee check-in stats or order details? ``` **Prompt:** ``` Show the check-in stats for last Saturday's event and any attendees who haven't checked in. ``` **Response:** ``` Check-in stats for 'Jazz Night' (event_298, Apr 19): Total tickets sold: 185. Checked in: 162 (87.6% scan rate). Unique scans: 162. Not checked in: 23 attendees. No-show highlights: 5 VIP tickets (€85 each = €425 unredeemed), 18 Regular tickets. Peak check-in window: 7:00-7:30 PM (68 scans). Last scan: 9:15 PM. Would you like to see the revenue report or export the attendee list? ``` **Prompt:** ``` Show the revenue report for all past events this month. ``` **Response:** ``` 3 past events this month. Total revenue: €32,780. Breakdown: 1) 'Jazz Night' (Apr 19) — €12,450 (185 tickets). Payment: 82% card, 18% iDEAL. 2) 'Art Exhibition Opening' (Apr 12) — €8,330 (92 tickets). Payment: 75% card, 25% iDEAL. 3) 'Comedy Show' (Apr 5) — €12,000 (240 tickets). Payment: 90% card, 10% iDEAL. Average ticket price: €63.40. Average attendance rate: 89.2%. Would you like to compare with last month or check webhook configurations? ``` ## Capabilities ### Review Event Lineups List all upcoming or past events, and inspect the full details for any specific event you need information on. ### Track Sales & Orders Get a complete list of ticket orders, filter them by a specific festival, and see who bought what and if payment went through. ### Audit Financials Pull detailed revenue reports showing total sales, payment breakdowns, and order histories for any given event. ### Monitor Attendance List every registered attendee for an event or review real-time ticket scan entries to see who checked in. ### Manage Setup Data View all configured webhook endpoints, check the overall connection status, and list available ticket types with their current pricing. ## Use Cases ### The Day After-Party Audit A venue manager needs to know if they met their sales quota. They ask the agent: 'What was the revenue and total orders for last night's event?' The agent uses 'get_event_revenue' combined with 'list_orders_by_event' to give an immediate, accurate financial snapshot. ### Pre-Event Capacity Check An organizer asks the agent: 'Show me all upcoming events and list their ticket types.' This allows them to confirm if they have enough capacity or need to raise pricing on specific event IDs using 'list_upcoming_events' and 'list_ticket_types'. ### Investigating Missing Attendees A finance team member notices a discrepancy. They ask the agent: 'List all attendees for Event X, and tell me who hasn't checked in.' This uses 'list_attendees' to identify potential no-shows that impact revenue. ### Quarterly Performance Review A senior manager needs a high-level view. They ask the agent for total performance across all past events, triggering calls like 'list_past_events' and aggregating data from multiple 'get_event_revenue' calls. ## Benefits - You don't have to jump through hoops to see the money. By using 'get_event_revenue', your agent gives you a clear breakdown of total revenue, including payment splits, without opening any financial dashboard. - Need to know who showed up? Instead of sorting massive CSV files, calling 'list_attendees' lets you see every person registered for an event and their check-in status instantly. - Stop guessing about what’s available. The 'list_ticket_types' tool tells you exactly how many Early Bird or VIP tickets are left to sell before the next promotion runs out. - Never lose track of a sale again. You can use 'list_orders_by_event' to pull all transaction records for a single festival, giving you immediate visibility into every ticket purchased. - When things go wrong, you need data fast. By calling 'get_scan_stats', your agent summarizes raw scan logs to give you the total scanned count and the actual scan rate percentage. - You can always verify the system's health first by running 'check_hipsy_status' before asking for any complex reports. ## How It Works The bottom line is: your agent translates complex business questions into specific data calls across the entire ticketing system. 1. Subscribe to this MCP on Vinkius. 2. Enter your Hipsy API Key into the connector settings. 3. Tell your AI agent what you need—for example, 'Show me total revenue for all events last month and list any attendees who haven't checked in.' ## Frequently Asked Questions **How does list_orders_by_event work?** It filters the entire order database to show only purchases related to a specific event ID. This is critical when you need to audit sales for one festival without seeing data from every other event. **Can I see all ticket types using list_ticket_types?** Yes, this tool shows every available ticket category for an event, giving you the pricing details and how many tickets of each kind are still available to sell right now. **What is the difference between list_orders and list_orders_by_event?** Using 'list_orders' gives you every single order ever placed. But if you only care about one specific event, use 'list_orders_by_event'; it cuts out all the noise. **How do I check revenue for multiple events?** You first need to list the relevant events using 'list_events,' then you can run 'get_event_revenue' on each ID and aggregate the results in your prompt. **What is the purpose of running the `check_hipsy_status` tool after setup?** It verifies your connection and API credentials. This check confirms that your AI agent can successfully communicate with Hipsy, letting you know immediately if there are any authentication issues or rate limit concerns. **If I need to review active integrations, what does the `list_webhooks` tool show me?** The `list_webhooks` tool provides a manifest of all configured webhook endpoints for your account. You can use this list to audit which systems are receiving event data or if any critical connections have been deactivated. **Does `get_scan_stats` help me track no-shows or attendance rates?** Yes, it gives you detailed check-in analytics. This includes the total number of tickets sold versus how many were scanned, allowing your agent to calculate the precise scan rate and identify potential missed attendees. **When using the `list_events` tool, can I limit the results to a specific time frame?** You can filter event listings by date range or status. If you specify parameters for 'upcoming' versus 'past,' your agent returns only the events that match those criteria, keeping your data set focused. **Can I track ticket sales and revenue for a specific event?** Yes. Use `get_event_revenue` with an Event ID to retrieve total revenue, ticket sales breakdown by type, and payment method distribution. Use `list_orders_by_event` to see individual orders with buyer details and amounts. Use `list_ticket_types` to see pricing and availability per ticket tier. **Can I monitor attendee check-ins in real time?** Yes. Use `list_attendees` to see all attendees with their check-in status. Use `list_scans` for individual scan entries with timestamps. Use `get_scan_stats` for aggregate metrics: total tickets scanned, unique scans, and overall scan rate percentage. **Can I view only upcoming or past events separately?** Yes. Use `list_upcoming_events` for future events sorted by date, or `list_past_events` for completed events useful for post-event reporting. Use `list_events` for all events regardless of date, and `get_event` for complete details of any specific event.