An astronaut overseeing a futuristic data hub

Connect Hipsy to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Run your entire ticketing operation through a simple chat interface.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 16 capabilities

We ship only the actions that matter.

Capability set01 / 04

01-04

4 capabilities in this set.

Part of 16 available through Hipsy.

  1. 01

    Get order

    This capability retrieves specific details for a single ticket order.

  2. 02

    Get organisation

    Use this to pull the profile and details of a specific Hipsy organisation.

  3. 03

    Get scan stats

    This capability provides aggregate check-in statistics like total scans and scan rates.

  4. 04

    List events

    This capability returns a list of all events in your account.

Capability set02 / 04

05-08

4 capabilities in this set.

Part of 16 available through Hipsy.

  1. 05

    List orders

    Use this to browse through all ticket orders.

  2. 06

    List organisations

    This capability lists all organisations associated with your account.

  3. 07

    List past events

    This capability retrieves a list of all completed events.

  4. 08

    Check hipsy status

    Use this to verify that the connection to Hipsy is active and working.

Capability set03 / 04

09-12

4 capabilities in this set.

Part of 16 available through Hipsy.

  1. 09

    Get event

    This capability pulls full details for a specific event.

  2. 10

    Get event revenue

    Use this to get the total revenue and sales breakdown for a specific event.

  3. 11

    List upcoming events

    This capability provides a list of all events scheduled for the future.

  4. 12

    List webhooks

    Use this to see all currently configured webhook endpoints.

Capability set04 / 04

13-16

4 capabilities in this set.

Part of 16 available through Hipsy.

  1. 13

    List attendees

    This capability pulls the list of attendees for a specific event, including their check-in status.

  2. 14

    List orders by event

    Use this to filter and view all orders tied to a specific event.

  3. 15

    List scans

    This capability retrieves individual scan entries from your events.

  4. 16

    List ticket types

    Use this to view the different ticket tiers, pricing, and availability for an event.

Real work

What teams actually run

01

Real-time Entry Monitoring

A venue manager asks the AI for current scan rates to see if the entrance is bottlenecked.

02

Sales Velocity Checks

An organiser checks how many VIP tickets remain for an upcoming festival.

03

Post-Event Financial Audits

A finance team member requests a revenue breakdown for all events held in a specific month.

04

Attendee Management

An organiser pulls a list of attendees who have not yet checked in to manage no-shows.

Automate a task

Put Hipsy to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Hipsy works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Hipsy to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

961ms average. Fast in production.

Hipsy is checked daily against the live service.

Daily averagePeak 1260ms
Oct 3Today
Fastest day
748ms
Slowest day
1260ms
14-day trend
Slowing+7%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 16 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Hipsy, so you can see the experience inside your AI.

It does not authenticate your account with Hipsy. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Hipsy Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_DnrSw5cA7JtNcXPsJK1dF9WkFoWPDQMTpv9n1P2R/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Hipsy capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "hipsy-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_DnrSw5cA7JtNcXPsJK1dF9WkFoWPDQMTpv9n1P2R/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Hipsy in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Hipsy owners hand off.

This MCP is built for professionals managing live entertainment and large-scale events.

  • 01

    Event Organisers

    They use the AI to track sales and revenue without logging into the main dashboard.

  • 02

    Venue Managers

    They monitor attendee flow and scan rates to manage capacity in real time.

  • 03

    Finance Teams

    They use the agent to audit payment histories and revenue reports.

FAQ

Questions Hipsy owners ask.

  • 01

    How do I connect my Hipsy account?

    Subscribe to the MCP on Vinkius and enter your Hipsy API Key from your account settings. Once connected, it is ready to use in your AI client.

  • 02

    Which AI clients can I use with this MCP?

    You can use this MCP with any compatible client, including Claude, Cursor, and Windsurf.

  • 03

    Can I see real-time check-in data?

    Yes, you can ask your agent to retrieve scan statistics and attendee check-in status for any event.

  • 04

    Does this MCP handle revenue reporting?

    Yes, the capability allows you to retrieve total revenue, ticket sales breakdowns, and payment data per event.

  • 05

    Can I manage multiple organisations?

    Yes, you can list all your organisations and inspect individual profiles through the MCP.

  • 06

    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.

  • 07

    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.

  • 08

    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.

Connect Hipsy to Claude, Cursor, ChatGPT & more