Qflow runs a hosted Model Context Protocol (MCP) server, so AI agents like Claude and ChatGPT can work with your events directly — creating events, managing guest lists, assigning team members and reading live figures, all in natural language and with your permission.

It's the same Qflow account and data as the dashboard and the REST API — just reached conversationally.

What you can do

• Read your events, guests, team and tallies — including fast counts, breakdowns and facets over the attendee search index.
• Write — create and update events and guests (single or up to 200 in bulk), add tags and tallies, and assign or unassign team members.
• Everything runs against your account, scoped by OAuth — the agent only ever sees what you've authorised.

The Qflow MCP server is hosted and OAuth-secured. Point your MCP client at the endpoint and sign in with your Qflow account — there are no API keys to copy or store.

Endpoint

https://api.qflowhub.io/qflow-mcp/mcp

Transport is Streamable HTTP, implementing the MCP 2025-06-18 specification.

Authentication

Access is protected by OAuth 2.1 (Authorization Code + PKCE) via Qflow's identity server. On first connect your client is redirected to sign in and authorise access, then the token is refreshed automatically.

• Protected-resource metadata: https://api.qflowhub.io/qflow-mcp/.well-known/oauth-protected-resource
• Authorization server: https://identity.qflowhub.io/core

Discovery is automatic — your client reads the protected-resource metadata, finds the authorization server, and runs the OAuth flow for you.

Add it to a client

Claude and ChatGPT — add a custom connector / MCP server pointing at the endpoint above; you'll be prompted to sign in with your Qflow account.

Claude Code and other MCP clients — register the server with Streamable HTTP transport, then complete the OAuth sign-in when prompted:

claude mcp add --transport http qflow https://api.qflowhub.io/qflow-mcp/mcp

The server exposes 22 tools. Reads are safe to run freely; writes change your data, and agents confirm before anything destructive.

Reading

• getRecentEvents — the 10 most recent events, newest first.
• searchEventsByName — events whose title contains a substring.
• getEventsByDateRange — events fully within a date window.
• getGuest — a single guest by id.
• getGuests — page an event's guest list.
• getGuestsByName — find guests by (prefix-matched) name within an event.
• getGuestsByEmail — exact email match within an event.
• getGuestsByBarcode — barcode lookup within an event.
• getTeamMembers — team members across your events.
• getTalliesByEvent — an event's tallies and current totals.
• getSearchSchema — the attendee search index field schema.
• searchAttendeeIndex — the analytics tool: counts, breakdowns, facets and time-based queries over the attendee index.

Writing

• createEvent / updateEvent — create or update an event.
• createGuest — add a single guest.
• upsertGuests — bulk create-or-update up to 200 guests in one call.
• updateGuest — update a guest's details.
• createTags — create tags for an event.
• createTallies — create door-staff counters (walk-up sales, drink tokens, and so on).
• createTeamMember — create a team-member account.
• assignATeamMember / unassignATeamMember — put a team member on an event, or remove them.

Every call runs against your own account and respects your plan; bulk guest creation counts only new guests against it.