Check Bookeo availability and manage bookings, holds and customers; read payments. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"bookeo": {
"url": "https://bookeo.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"bookeo": {
"type": "http",
"url": "https://bookeo.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Bookeo API key and Application secret key.
The Bookeo API needs a paid Bookeo subscription. To get both keys: 1) create a free Bookeo developer account and register an application — its secret key is shown there; 2) have the business account owner open the app's Authorization URL and grant permissions (e.g. bookings_rwd_all,customers_rw_all,payments_r_all,availability_r) — Bookeo then issues the per-account API key. Your keys are used only to call the API on your behalf and to derive a private account id; they are never shown to anyone.
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 Bookeo API key and Application secret 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.
Turn on the Bookeo connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
bookeo_get_api_key_info | read | Get API key info Show which Bookeo account the credentials belong to and which permissions were granted (e.g. bookings_rw_all, customers_r_all, availability_r). A cheap way to confirm the setup works. Bookeo: GET /settings/apikeyinfo. |
bookeo_get_business | read | Get the business Get the business's name, contact details, address, website and description. Bookeo: GET /settings/business. |
bookeo_list_products | read | List products List the bookable products (tours, classes, courses, appointments) with their ids, type (fixed, fixedCourse, flexibleTime), duration, participant limits per people category, default rates and options. Bookeo: GET /settings/products. |
bookeo_list_people_categories | read | List people categories List the participant categories the account uses (default Adults/Children/Infants plus custom ones like Students), with their ids and seats taken. Needed for peopleNumbers. Bookeo: GET /settings/peoplecategories. |
bookeo_list_resources | read | List resources List resource types and their resources (guides, instructors, rooms, boats...) with ids. Bookeo: GET /settings/resources. |
bookeo_get_availability_slots | read | Get availability slots List available slots (eventId, start/end, seats available) for fixed and fixedCourse products in a time window of at most 31 days. Not for flexibleTime products — use bookeo_search_matching_slots for those. Bookeo: GET /availability/slots. |
bookeo_search_matching_slots | read | Search matching slots Find slots that can take a given party (participant counts per category, options, resources), with an estimated price. Works for all product types, including flexibleTime appointments. Window max 31 days. To page through results pass only pageNavigationToken (+ pageNumber). Read-only. Bookeo: POST /availability/matchingslots, GET /availability/matchingslots/{pageNavigationToken}. |
bookeo_list_bookings | read | List bookings List bookings by start time (startTime+endTime) and/or by last change (lastUpdatedStartTime+lastUpdatedEndTime) — at least one pair is required, each spanning at most 31 days. Optionally filter by product, include canceled bookings, and expand customer/participant details. Bookeo: GET /bookings. |
bookeo_get_booking | read | Get a booking Get one booking by its booking number: product, times, participants, options, price, paid amount, status (canceled/accepted/noShow). Bookeo: GET /bookings/{bookingNumber}. |
bookeo_list_booking_payments | read | List a booking's payments List the payments (and refunds, as negative amounts) received for one booking. Bookeo: GET /bookings/{bookingNumber}/payments. |
bookeo_list_customers | read | List customers List or search customers — by name, firstName, lastName or emailAddress — optionally only members/non-members or those created since a date. Bookeo: GET /customers. |
bookeo_get_customer | read | Get a customer Get one customer: contact details, next/previous booking, number of bookings, cancellations and no-shows, membership and store credit. Bookeo: GET /customers/{id}. |
bookeo_list_customer_bookings | read | List a customer's bookings List one customer's bookings, optionally between two dates. Bookeo: GET /customers/{id}/bookings. |
bookeo_list_payments | read | List payments List payments received in a time period, optionally by payment method. Refunds are included with a negative amount. Bookeo: GET /payments. |
bookeo_get_payment | read | Get a payment Get one payment: amount, method, reason, received time, customer and gateway transaction id. Bookeo: GET /payments/{id}. |
bookeo_create_hold | write | Hold seats (price check) Temporarily reserve the seats/resources for a draft booking (default 300 s, max 600 s) and get the FINAL price, taxes and amount payable. The recommended step before bookeo_create_booking: pass the returned hold id as previousHoldId there. Holds expire automatically. Bookeo: POST /holds. |
bookeo_create_booking | write | Create a booking Create a confirmed booking for an existing customer (customerId) or a new one (customer). fixed/fixedCourse products need an eventId from the availability tools; flexibleTime products take eventId or startTime. Pass previousHoldId to convert a hold. Does NOT record any payment. Reversible with bookeo_cancel_booking. Bookeo: POST /bookings. |
bookeo_update_booking | write | Update a booking Change an existing booking — reschedule (eventId or startTime/endTime), change participant counts, options, resources or external reference. Fetches the current booking and sends it back with only your changes applied (Bookeo's PUT takes the full booking). Bookeo: GET then PUT /bookings/{bookingNumber}. |
bookeo_cancel_booking | write | Cancel a booking Cancel a booking. It stays in the system (visible with includeCanceled) but frees its seats. The account's cancellation policy is NOT applied, so no cancellation fee is charged. Bookeo: DELETE /bookings/{bookingNumber}. |
bookeo_create_customer | write | Create a customer Create a customer record. Not needed before booking — bookeo_create_booking can create the customer inline. Bookeo: POST /customers. |
bookeo_update_customer | write | Update a customer Update a customer's contact details. Fetches the current record and sends it back with only your changes applied (Bookeo's PUT takes the full customer). Bookeo: GET then PUT /customers/{id}. |
bookeo_usage_status | Usage status (free-tier meter) 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. | |
bookeo_request_feature | Request a missing feature Tell usefulapi that the user needs something the Bookeo 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. | |
bookeo_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Bookeo (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $19/month or $190/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
bookeo_cancel_subscription | Cancel the Pro subscription Cancel the caller's Bookeo 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 bookeo_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Bookeo server only. Subscribe with bookeo_upgrade (it returns a Stripe Checkout link). Cancel any time with bookeo_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running bookeo_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Bookeo. The server calls the Bookeo API with your own Bookeo 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 Bookeo API key and Application secret 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 Bookeo API key and Application secret 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 Bookeo 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 Bookeo.
Yes, if you approve it. 6 of the 21 Bookeo tools can create or change data. The other 15 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 unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Bookeo server only. Cancel any time: Pro then runs to the end of the paid period. Run bookeo_usage_status to see how many calls you used.
Ask the AI to run bookeo_upgrade: it returns a Stripe Checkout link. To cancel, run bookeo_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with bookeo_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.