Read events, seats, attendees, sales and payouts; check in tickets and create orders in Billetweb. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the Billetweb connector, then ask in plain words. The AI picks the tools.
For event organisers who sell tickets with Billetweb.
List the events of the organiser, then read the remaining places per session and per ticket type. Use the numbers to answer how many seats are left.
List the sessions of an event, then list its attendees filtered by session and by check-in state. Use the list to see who has not arrived yet.
Find the ticket id of an attendee in the attendee list. Then set the ticket to checked in, checked out or not checked in.
Changes dataRead the sales and refunds of a period, then list the payouts. Open one payout to see each sale, refund and fee line.
Find the unpaid reservation orders in the attendee list. Then send each buyer a payment request email. Billetweb cannot recall the email once it is sent.
Changes dataList the ticket types of an event, then create offline orders paid by cash, card or invitation. Pass a request id, because a retry creates a second order.
Changes dataThe login page asks for your Billetweb API user and Billetweb API key.
Create a key in the Billetweb back office on the API page: choose A third party and name it (for example the AI assistant you use), pick read only to browse or read and write to also check in tickets or create orders, and optionally restrict it to some events. The page then shows the user and the key. They are used only to call the Billetweb API on your behalf; they are never shown to anyone.
Open Customize → Connectors → + Add → Add custom connector, then enter the name Billetweb and this URL:
The Claude Free plan allows one custom connector.
Team and Enterprise: an Owner adds it for the organization first.
No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"billetweb": {
"url": "https://billetweb.usefulapi.io/mcp"
}
}
} Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"billetweb": {
"type": "http",
"url": "https://billetweb.usefulapi.io/mcp"
}
}
} Run these commands. The second one opens the login page:
Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Billetweb API user and Billetweb API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | 10,000 tool calls / month |
| Pro+per user | $39/mo · $390/yr | 100,000 tool calls / month |
Each paid plan covers this Billetweb server only. Ask your AI to run billetweb_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with billetweb_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with billetweb_upgrade before then undoes the cancel. Or write to [email protected].
billetweb_list_eventsbilletweb_get_availabilitybilletweb_list_ticketsbilletweb_list_sessionsbilletweb_list_attendeesbilletweb_list_all_attendeesbilletweb_list_waiting_listbilletweb_list_accountingbilletweb_list_payoutsbilletweb_get_payoutbilletweb_list_crm_contactsbilletweb_list_crm_segmentsbilletweb_list_listsbilletweb_get_list_databilletweb_check_ticketsbilletweb_mark_orders_paidbilletweb_send_payment_requestsbilletweb_create_offline_ordersbilletweb_usage_statusbilletweb_request_featurebilletweb_upgradebilletweb_cancel_subscriptionCheck how many seats are left for an event. Find who has not checked in for a session. Check attendees in or out at the entrance. Review sales, refunds and payouts for a period. Send payment requests for unpaid reservations. Create offline orders for guests. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Billetweb. The server calls the Billetweb API with your own Billetweb access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Billetweb API user and Billetweb API key. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Billetweb API user and Billetweb API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Billetweb API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Billetweb.
Yes, if you approve it. 4 of the 18 Billetweb tools can create or change data. The other 14 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Billetweb server only. Cancel any time: your paid plan then runs to the end of the paid period. Run billetweb_usage_status to see how many calls you used.
Ask the AI to run billetweb_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run billetweb_cancel_subscription. Your paid plan continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with billetweb_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.