Compatible with every major AI agent and IDE
What is the Hipsy MCP Server?
Connect your Hipsy account to any AI agent and manage your event ticketing operations through natural conversation.
What you can do
- Organisation Management — List all event organisations and inspect individual profiles
- Event Browsing — List all events, filter upcoming or past events, and inspect full event details with ticket types and sales data
- Order Tracking — Browse all ticket orders, filter by event, and inspect individual order details with buyer info and payment status
- Ticket Configuration — View all ticket types for an event with pricing and availability
- Attendee Management — List all attendees for an event with check-in status
- Scan Analytics — Review ticket scan entries and aggregate check-in statistics (total scanned, scan rate)
- Revenue Reporting — Retrieve total revenue, ticket sales breakdown, and payment data per event
- Webhooks — List all configured webhook endpoints
How it works
- Subscribe to this server
- Enter your Hipsy API Key from your account settings
- Start managing events from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Event Organisers — track ticket sales, monitor check-ins in real time, and review post-event revenue without opening the dashboard
- Venue Managers — monitor attendee flow, scan rates, and capacity utilization
- Finance Teams — audit revenue reports, payment breakdowns, and order histories through AI
Built-in capabilities (16)
Verify connectivity
Get event details
Get event revenue
Get order details
Get organisation details
Get scan statistics
List attendees
List all events
List all orders
List orders by event
List organisations
List past events
List scan entries
List ticket types
List upcoming events
List webhooks
Why VS Code Copilot?
GitHub Copilot Agent mode brings Hipsy data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 16 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Hipsy in VS Code Copilot
Hipsy and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Hipsy to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Hipsy in VS Code Copilot
The Hipsy MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 16 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Hipsy for VS Code Copilot
Every tool call from VS Code Copilot to the Hipsy MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Splitwise
10 toolsConnect your Splitwise account to AI agents to track expenses, check balances, and manage shared groups.

Hunter
10 toolsEquip your AI agent with direct access to Hunter.io — find professional email addresses, verify deliverability, and enrich lead data without leaving your workflow.

DHL
6 toolsAI logistics: track global shipments, audit delayed packages, and quote DHL worldwide rates.

WordPress
10 toolsManage posts, pages, and media on WordPress — the world's most popular open-source content management system.
