Billetweb MCP server

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.

Connect Billetweb50 free tool calls a month

What can I ask?

Turn on the Billetweb connector, then ask in plain words. The AI picks the tools.

What you can do with Billetweb in Claude and ChatGPT

For event organisers who sell tickets with Billetweb.

Check how many seats are left for an event

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.

Find who has not checked in for a session

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.

Check attendees in or out at the entrance

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 data

Review sales, refunds and payouts for a period

Read the sales and refunds of a period, then list the payouts. Open one payout to see each sale, refund and fee line.

Send payment requests for unpaid reservations

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 data

Create offline orders for guests

List 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 data

How do I connect Billetweb?

Before you connect

The 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.

Claude claude.ai · Desktop

Add to Claude
or add it manually

Open Customize → Connectors → + Add → Add custom connector, then enter the name Billetweb and this URL:

https://billetweb.usefulapi.io/mcp

The Claude Free plan allows one custom connector.

  1. In the dialog, click Continue, keep the detected options and confirm.
  2. Claude opens the login page: enter your Billetweb API user and Billetweb API key.
  3. In a chat, click + → Connectors and turn on Billetweb.

Team and Enterprise: an Owner adds it for the organization first.

ChatGPT chatgpt.com

  1. Open Plugins, click +, then Add custom MCP server.
  2. Enter the name Billetweb and this URL, choose OAuth as the authentication, confirm the warning and create it:
    https://billetweb.usefulapi.io/mcp
  3. ChatGPT opens the login page: enter your Billetweb API user and Billetweb API key.
  4. In Plugins, install Billetweb, then choose it in a chat.

No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.

Claude Code

Run this command, then run /mcp in Claude Code to log in:

claude mcp add --transport http billetweb https://billetweb.usefulapi.io/mcp

Cursor

Add to Cursor or add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "billetweb": {
      "url": "https://billetweb.usefulapi.io/mcp"
    }
  }
}

VS Code

Add to VS Code or add this to .vscode/mcp.json:

{
  "servers": {
    "billetweb": {
      "type": "http",
      "url": "https://billetweb.usefulapi.io/mcp"
    }
  }
}

Codex

Run these commands. The second one opens the login page:

codex mcp add billetweb --url https://billetweb.usefulapi.io/mcp
codex mcp login billetweb

Other clients

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.

https://billetweb.usefulapi.io/mcp

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.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Proper user$9/mo · $90/yr10,000 tool calls / month
Pro+per user$39/mo · $390/yr100,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].

Tools 22

Show all 22 tools (the AI picks them for you)

Read only · 14

  • List eventsbilletweb_list_events
    List the organiser's events with id, name, start/end, place, shop URL, online state, tax rate, tags and contact. Past events are left out unless include_past is set.
  • Get availabilitybilletweb_get_availability
    Remaining places of an event: per session, per category and per ticket type, with avail (-1 = unlimited), quota and sales. Use it to answer 'how many seats are left'.
  • List ticket typesbilletweb_list_tickets
    The ticket types (tarifs) of an event in display order: id, name, price, category, quota, visibility (0 visible, 1 web, 2 box office, 3 secret link, 4 hidden), sales window, tax and commission.
  • List sessionsbilletweb_list_sessions
    The sessions (séances, dates) of a multi-session event: id, start/end, name, place, quota, total_sales, state (0 open, 1 hidden, 2 box office only, 3 web only, 4 link only, 5 cancelled) and the ticket ids sold in it.
  • List attendees of an eventbilletweb_list_attendees
    The attendees (one row per ticket) of one event: name, email, ticket type, price, check-in state (used), session, order id and payment, custom form answers. Filter by session, ticket, buyer, check-in state or when the order changed; use updated_since to fetch only what is new. Billetweb allows 10 attendees calls per minute (shared with billetweb_list_all_attendees), so prefer one filtered call.
  • List attendees across all eventsbilletweb_list_all_attendees
    The attendees of ALL events, newest changes included, with the same fields as billetweb_list_attendees. Filter by event tag, only unfinished events, buyer, ticket, check-in state or order change time. Billetweb allows 10 attendees calls per minute; use updated_since for incremental reads.
  • List waiting listbilletweb_list_waiting_list
    People on the waiting list of an event: name, email, phone, ticket/session wanted, places asked for and whether they were notified.
  • List sales and refunds (accounting)billetweb_list_accounting
    The accounting history: one row per ticket and per money movement, type product_pay (sale) or product_refund (negative price), with price incl. tax, Billetweb fees, tax, payment type, transaction id and payout id (0 = not paid out yet). Period at most 1 year, starting at most 1 year ago.
  • List payoutsbilletweb_list_payouts
    The bank transfers Billetweb made to the organiser (type out) or took back (type in, negative amount): id, date, net amount, account holder. The IBAN is masked to its last 4 characters.
  • Get payout detailbilletweb_get_payout
    The line-by-line detail of one payout: each sale, refund or transfer with ticket reference, order, event, price, fees and tax. Net transferred = sum of price minus sum of fees. Pass a payout id, or a date (yyyy-mm-dd) for all payouts of that day.
  • List CRM contactsbilletweb_list_crm_contacts
    The organiser's buyer contacts: name, email, first/last purchase, number of orders and tickets, total spent and average ticket price. Filter by email, CRM segment or last change.
  • List CRM segmentsbilletweb_list_crm_segments
    The saved CRM segments (id, name, created, last sync). Use an id as the segment filter of billetweb_list_crm_contacts.
  • List custom listsbilletweb_list_lists
    The organiser's custom lists (id, name, key type), such as member or invitation lists used for access control and discounts.
  • Get custom list contentbilletweb_get_list_data
    The rows of one custom list (each row is an array of values, the first being the key).

Changes data · 4

  • Check tickets in or outbilletweb_check_tickets
    WRITE: set the check-in state of tickets (composter): 1 = checked in, 2 = checked out, 0 = back to not checked in. Tickets are identified by the ticket id from billetweb_list_attendees (the `id` field, not the order id). Setting the same state again is harmless. Needs a read+write key.
  • Mark reservations as paidbilletweb_mark_orders_paid
    WRITE: confirm the payment of reservation orders (unpaid orders taken as a reservation) with the payment type you were given (card, cash, check, reservation, other). With send_confirmation the BUYER GETS AN EMAIL with the tickets; default is no email. The order id is `order_id` in billetweb_list_attendees. Needs a read+write key.
  • Send payment request emailsbilletweb_send_payment_requests
    WRITE: SENDS AN EMAIL to each buyer asking them to pay their unpaid reservation. Customers receive it immediately; it cannot be recalled. The order id is `order_id` in billetweb_list_attendees. Needs a read+write key.
  • Create offline ordersbilletweb_create_offline_orders
    WRITE: CREATE new orders (tickets) in an event as if sold off-line: each order takes places from the quota and is recorded as paid with the given payment type (card, cash, check, invitation, reservation, other). Only basic tickets (no choice passes, packs or seat placement). With send_tickets the BUYER GETS THE TICKETS BY EMAIL (default: no email). NOT idempotent: calling twice creates two orders, so pass request_id and check billetweb_list_attendees before retrying. Needs a read+write key.

Your usefulapi plan · 4

  • Usage status (free-tier meter)billetweb_usage_status
    Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter.
  • Request a missing featurebilletweb_request_feature
    Tell usefulapi that the user needs something the Billetweb tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter.
  • Upgrade to Pro or Pro+billetweb_upgrade
    Get a paid plan for Billetweb (the free tier caps monthly usage). Pro: 10,000 tool calls a month, for normal use — plan "monthly" ($9/month) or "yearly" ($90/year, 2 months free). Pro+: 100,000 tool calls a month, for automations and heavy use — plan "plus" ($39/month) or "plus_yearly" ($390/year). Without a plan it returns both Pro and Pro+, each with a payment link, for the user to choose; with a plan, one link. An existing Pro subscription changes to Pro+ in place: call without confirm first, as the reply states the exact charge for this account (the price difference for the rest of the period, or in a free Pro trial the full Pro+ price, as the trial ends); then call with confirm: true. Cancel any time: the plan then runs to the end of the paid period, so it also suits a one-time job. A link opens Stripe Checkout in the browser; after payment the account upgrades automatically. Does not count against the meter.
  • Cancel the Pro subscriptionbilletweb_cancel_subscription
    Cancel the caller's Billetweb Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run billetweb_upgrade later to undo the cancel before the period ends. Does not count against the meter.

FAQ

What can I do with Billetweb in Claude or ChatGPT?

Check 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.

Is this an official Billetweb product?

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.

Can I connect Billetweb to Claude or ChatGPT?

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.

What do I need to connect?

The login page asks for your Billetweb API user and Billetweb API key. See Before you connect for where to find them.

Do I put my Billetweb key or an Authorization header in the client config?

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.

How do you keep my Billetweb credentials?

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.

Can the AI change my Billetweb data?

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.

What does it cost?

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.

How do I subscribe or cancel?

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.

What if a Billetweb tool that I need is missing?

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.

Which AI clients can I use?

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.

More Commerce & Memberships MCP servers

Abacus POSApiloAwtomicBeacon CRMBettermodeBetterNowBloomerangbol.comBooqableBrandboomBreeze ChMSBrightpearlBrother POSBsaleBSS B2B SolutionBuy Me a CoffeeCatalog MachineCCV ShopChannableChannel Pilot ProChannelEngineCharityFundraiserCharityStackCin7 CoreConsignCloudCratejoyCustomCatDarasDecimal POSDecoNetworkDokunDotyposEasyStoreEcwidEffectConnectElementary POSElvantoEveniumEventbriteFeed APIFinale InventoryFinerWorksFitsseyFoxy.ioFunraiseGelatoGift Up!GiftbitGivecloudGivingFuelGoDataFeedGood GrantsGootenGumroadHeartland RetailHello ClubHiboutikHumanitixIdoSellImker SalesCRMInventory PlannerJubelioKASSA.ATKiotVietKoursesLearnWorldsLengowLibibLightspeed Retail (R-Series)Lightspeed Retail (X-Series)LinnworksLittle Green LightLooxLoyverseMarketTimeMegaventoryMemberfulMemberRunMembers.devMemberSuiteMemberVaultMyCashflowmyClubMyOnlineStoreNembolNeon CRMOpenWaterOrder DeskOwnerRezPatreonPHP Point of SalePlentyONEPowerHubpretixPrice2SpyPrintfulPrintifyPrintPossPrisyncProdigiPutiikkipalveluQgivRackbeatRaiselyRechargeRecurpayRetailCloudReturnGOReturnLogicREVIEWS.ioRock Gym ProSalesBinderSalesPlay POSSalsa EngageSamitaSapoSearchaniseSellasistSelloShift4ShopShoprocketShopWiredSmaregiSmile.ioSOS InventorySpektrixSpreadconnectStampedSteadyStoreRocketSugarWODSwellTeamUpTicimaxTicketsauceTicketSpiceTillhubTiltifyTitoTourCMSTshirtgangUniverseUnleashed SoftwareUPOS Cloud POSVeeqoVendtyVirtuousWhite Label LoyaltyWild ApricotZettleZylvie

All Commerce & Memberships servers →