Connect an AI assistant with MCP

What the connection does

The remote Q2Tix MCP server lets an authorized assistant manage event publishing. It is separate from the public, read-only event feed. It cannot issue refunds, access payments or attendee data, or change account credentials.

Use the Event Publisher capabilities guide to check supported actions and portal-only tasks before automating a workflow.

Create an Event Publisher key

1. In the organizer workspace, open Account Settings → Integrations.
2. Create a named integration key with the Event Publisher capability and the event access you intend to grant.
3. Copy the secret when it is displayed. It is shown only once. You can rotate or revoke it from the same settings page.

Use your MCP client's protected credential or header configuration. Never place the key in Git, a public website, an application .env file, or a support message.

Connect your client

Set the remote server URL to:

https://q2tix.com/mcp

Configure this header using your own integration key:

Authorization: Bearer qst_your_integration_key

No local Node process or application checkout is required. The remote server accepts Integration Keys; legacy user API tokens are not accepted. A Ticket Check-in key is a different capability and cannot be used for event publishing through MCP.

Verify the connection

Run get_connection and confirm that the returned account and Event Publisher capability match what you intended. Refresh your client's tool list if newly released operations are missing.

If authentication fails, check the key's capability, expiration, and whether it has been rotated or revoked. Contact support@q2tix.com with the visible error, never the key itself.

Publishing and duplication change real event records. Inspect the result after an uncertain response before retrying a create or copy operation: another call may create another record.

For the underlying authenticated endpoints, see the Event API reference.