Connect an AI client
Connect your AI assistant to TixFin over MCP, so it reads your events and sales and proposes changes you confirm, as you and only in the projects you choose
The Model Context Protocol (MCP) is an open standard that lets an AI client, such as a desktop chat app or a coding assistant in your editor, call tools on another service. TixFin runs an MCP server: once you connect your AI client to it, you can ask the client about your events, ticket sales, orders and check-ins, and it reads the answers from TixFin live. If you allow it, the client can also plan and change things: it then shows you a proposal, and nothing changes until you confirm it. The client always acts as you. It can do no more than you can in the dashboard, only in the projects you allow, and only what you allowed it.
Who can do this: every project member. The client gets your own permissions in each project, no more.
The server address
https://mcp.tixfin.com/mcpThe address is the same for every organiser; your sign-in decides what the client sees.
Which clients can connect
TixFin does not let AI clients register themselves. A client can connect only if TixFin has registered it for your region, with the addresses it may send you back to after you sign in. Which clients are registered in your region, and the client ID to enter if your client asks for one, you get from support.
A client needs three things:
- it adds a remote MCP server by address, over Streamable HTTP;
- it signs in with OAuth, in your browser (TixFin asks for no API key);
- TixFin has registered it, as above. A client that only registers itself on the fly cannot connect yet.
A client that only runs local MCP servers on your computer cannot connect yet either.
ChatGPT, Claude and Claude Code
Most clients need nothing but the address: they register themselves with TixFin when you connect, and the consent page
then names them by the address they send you back to (for example chatgpt.com, or localhost for an app on your
computer). If a client still asks for a client ID, enter one of these in its advanced OAuth settings and leave the
client secret empty.
| Client | Client ID | Where you add TixFin |
|---|---|---|
| ChatGPT | chatgpt | Settings → Apps & Connectors, with developer mode on under Advanced settings; Create |
| Claude (web, desktop and mobile) | claude | Settings → Connectors → Add custom connector; the client ID is under Advanced settings |
| Claude Code | claude-code | In your terminal, below |
claude mcp add --transport http tixfin https://mcp.tixfin.com/mcpIf it asks for a client ID, add --client-id claude-code.
Then run /mcp in Claude Code and choose tixfin to sign in in your browser.
In the client, TixFin shows as TixFin with its logo and a short description, and it tells the client how its tools fit together: which projects it may use, that every change is a proposal you confirm, and when a second factor is needed. For another coding assistant, ask support.
Add TixFin to your AI client
Clients come in two kinds, and each names its settings differently.
Chat apps
Desktop and web chat apps add a remote server under a name such as connector, integration or custom server.
Coding assistants and editor agents
Agents in your editor or terminal usually read their MCP servers from a settings file. Add TixFin as a server with
the address as its url and HTTP as its type; the exact keys are in your client's own documentation. For example:
{
"mcpServers": {
"tixfin": {
"type": "http",
"url": "https://mcp.tixfin.com/mcp"
}
}
}When the agent first uses the server, it opens TixFin in your browser, and you sign in and approve it as in steps 3 to
5 above. Agents on your computer receive the answer on a local address (127.0.0.1), which TixFin accepts on any port
for the clients it registered that way.
The consent page
Allow an AI client names the client that asks ("client name asks for access to your TixFin account") and asks two things.
What it may do. Each choice is a scope. The page offers the scopes your client asked for; a client that asks for none is offered reading alone. Only reading is ticked to start with; the other three carry a warning. If a choice you need is missing, your client did not ask for it: check its settings.
| Choice | Scope | What it means |
|---|---|---|
| Read your events, ticket sales, orders and reports | tixfin.read | The client can read your events, ticket tiers, venues, sales figures, shop pages and reports. Orders, check-ins and guest lists also need personal data, below. |
| Make changes you confirm | tixfin.write | The client can propose changes such as a draft event, ticket types, a venue or a shop page. Each one is a proposal you see before anything changes. |
| Take actions that move money or reach buyers | tixfin.money | The client can propose refunds, cancellations, deletions, discounts, campaigns to buyers and other actions buyers notice. Each one is a proposal, and applying it needs a second factor from the last ten minutes (money and the step-up). |
| See buyers' personal data | tixfin.personal_data | Lets the client read orders, attendance and other answers that contain buyers' names and contact details. It also needs the project's AI access setting on. Without both, those tools are refused and personal fields are masked (what is masked). |
The choices do not include one another: to propose changes and see the current values in the preview, allow reading too.
Allow only what you need. You can connect again later with more.
In which projects. Tick every project the client may work in. A project you do not tick is closed to it, even if you are an owner there. Allow stays disabled until you have picked at least one choice and one project.
Click Deny to send the client away without access. If the page says "This request is invalid or has expired", start the connection again from your client: a request is valid for 10 minutes.
Disconnect a client
Open Account → Security → Sessions. Under Devices, every AI client you allowed is listed by its name, beside your browsers and phones. Click Revoke next to it.
Access ends at once: the client's next request is refused and it has to ask you again to reconnect. Removing the server in your AI client alone does not end TixFin's grant, so revoke it here as well.
Common problems
- The client says it is not authorized, or asks you to sign in again. The connection was revoked, or TixFin ended it because a token was used twice (see Privacy and security). Connect again.
- The client says a project is not one this connection may act in. You did not tick that project on the consent page. Connect again and tick it.
- A tool answers that it needs personal data. You did not allow See buyers' personal data, or the project's AI access setting is off. Connect again and tick it, or ask a project admin to switch the setting on, if you want the client to read orders and attendance.
- A tool is refused although you allowed the project. Your role in that project lacks the permission. Ask the project owner (see Team and roles).
- A change is refused with a note about a second factor. Money proposals need a fresh second factor on the connection: see money and the step-up.
- The browser shows an error instead of the sign-in or consent page. TixFin may not have registered this client, or the address it returns to, in your region. Ask support.
- "You are not a member of any project". Accept an invitation or create a project first.