Read Waitwhile visits, bookings, customers, services and analytics; add, update and cancel visits. Hosted by usefulapi — connect from Claude, 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": {
"waitwhile": {
"url": "https://waitwhile.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"waitwhile": {
"type": "http",
"url": "https://waitwhile.usefulapi.io/mcp"
}
}
}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 Waitwhile API key.
Create it in Waitwhile → Settings → Developers → API & Webhooks → Create API key (the API needs the Business plan or higher). Your key is used only to call the Waitwhile API on your behalf; it is 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 Waitwhile 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.
| Tool | Type | What it does |
|---|---|---|
waitwhile_list_locations | read | List locations List the account's locations (businesses/sites): id, name, short name, address, time zone, opening hours and waitlist/booking settings. Use the ids to filter visits, services and resources. GET /locations. |
waitwhile_get_location | read | Get location One location by id or short name (the part of its public Waitwhile URL). GET /locations/{shortNameOrId}. |
waitwhile_list_location_status | read | List location status (live waitlist) Live status of every location: open/closed, number of people waiting and being served, current estimated wait time, and booking counters. GET /location-status. |
waitwhile_get_location_status | read | Get location status (live waitlist) Live status of one location: open/closed, waiting and serving counts, estimated wait. GET /location-status/{locationId}. |
waitwhile_list_visits | read | List visits (waitlist entries and bookings) List visits: waitlist entries (people in line) and bookings (appointments), with customer, state (PENDING, DRAFT, BOOKED, WAITING, SERVING, COMPLETE), tags (e.g. NO-SHOW, CANCELLED, ARRIVED), services, resources, party size, position and timestamps. Filter by location, state, tag, customer, service, resource, booking date (local time) or created/updated date. Cursor-paged. Contains customer contact details. GET /visits. |
waitwhile_search_visits | read | Search visits Search visits by a prefix match on customer name, phone, e-mail or customer id, optionally filtered by location, state, tag and excluded tags. Page-numbered. Contains customer contact details. GET /visits/search. |
waitwhile_get_visit | read | Get visit One visit (waitlist entry or booking) by id: customer, state, tags, services, resources, party size, position, estimated wait and all timestamps. GET /visits/{visitId}. |
waitwhile_list_booking_slots | read | List booking slots Booking slots of a location for a date range with the free spots per resource and service, so you can see when an appointment can be booked. Dates are local to the location, YYYY-MM-DDThh:mm. GET /visits/availability. |
waitwhile_first_available_slots | read | First available booking slots The first available booking slots of a location (optionally for a party size, services and resources) from a date. Use it to propose appointment times. GET /visits/first-available-slots. |
waitwhile_list_customers | read | List customers List customers (name, phone, e-mail, tags, last visit per location, created/updated). Cursor-paged, 20 per page by default; filter by location, external id or created/updated date. Contains personal data. GET /customers. |
waitwhile_search_customers | read | Search customers Search customers by a prefix match on name, phone, e-mail or customer id; optionally narrowed by location, visit state or tag. Page-numbered. Contains personal data. GET /customers/search. |
waitwhile_get_customer | read | Get customer One customer by id: contact details, tags, per-location state and last visit. Contains personal data. GET /customers/{customerId}. |
waitwhile_list_customer_notes | read | List customer notes The staff notes recorded on a customer (content, author, visit and location, timestamps). GET /customers/{customerId}/notes. |
waitwhile_list_services | read | List services List services (what customers book or queue for): name, duration, price, locations, resources and category structure. GET /services. |
waitwhile_get_service | read | Get service One service by id. GET /services/{serviceId}. |
waitwhile_list_resources | read | List resources (staff, rooms, tables) List resources — the people, rooms, tables or equipment that serve customers: name, locations, services, availability flag and category structure. GET /resources. |
waitwhile_get_resource | read | Get resource One resource by id. GET /resources/{resourceId}. |
waitwhile_resources_availability | read | Resource availability Working hours/availability of a location's resources on a date (e.g. who is working today). GET /resources/availability. |
waitwhile_list_data_fields | read | List data fields (intake form fields) List the custom data fields (intake/booking form questions) with type, options and where they apply. Use the ids to read answers on visits. GET /data-fields. |
waitwhile_get_data_field | read | Get data field One data field by id. GET /data-fields/{dataFieldId}. |
waitwhile_list_users | read | List users (staff) List the staff users of the account: name, e-mail, roles, locations. Password data and tokens are never returned. GET /users. |
waitwhile_list_messages | read | List messages List the SMS/e-mail messages Waitwhile sent to and received from customers: channel, recipient, body, delivery state (PENDING, BLOCKED, FAILED, DELIVERED, UNCONFIRMED, RECEIVED) and error. Filter by location, visit, customer, state or date. Contains personal data. This only reads; it cannot send. GET /messages. |
waitwhile_get_message | read | Get message One message by id. Contains personal data. GET /messages/{messageId}. |
waitwhile_visit_analytics | read | Visit analytics Aggregated visit statistics for a period: visits, waitlisted, bookings, served, no-shows, cancellations, wait and serve duration quantiles, and breakdowns by location, resource, service, party size, user, day of week and hour of day. GET /analytics/visits (JSON). |
waitwhile_list_audit_entries | read | List audit entries The account's audit log: who changed what and when (visits, customers, locations, services, resources, users, messages). Filter by type, event, entity, location or date. GET /audit-entries. |
waitwhile_create_visit | write | Add a customer to the waitlist or create a booking WRITE: create ONE visit at a location. Without a date it adds the customer to the waitlist; with a local date-time (YYYY-MM-DDThh:mm) it creates a booking. Needs a location and at least a name, phone or e-mail. Not idempotent: calling it twice creates two visits. Visit notes are not supported here (the field is deprecated): use waitwhile_add_customer_note. By default the request asks Waitwhile to suppress the customer message; this may only stop the immediate confirmation, and scheduled reminders/follow-ups can still go out per the location's settings. With send_notifications=true Waitwhile may text/e-mail this ONE customer. POST /visits. |
waitwhile_update_visit | write | Update a visit (state, tags, time, party) WRITE: change ONE visit — its state (e.g. WAITING to SERVING to COMPLETE, or BOOKED), add/remove tags (e.g. ARRIVED, CONFIRMED, NO-SHOW), booking date/duration or party size. Only the fields you pass change. By default the request asks Waitwhile to suppress the customer message; this may only stop the immediate status message, and scheduled reminders/follow-ups can still go out per the location's settings. With send_notifications=true Waitwhile may text/e-mail this ONE customer. Use waitwhile_cancel_visit to cancel. POST /visits/{visitId}. |
waitwhile_cancel_visit | write | Cancel a visit WRITE: cancel ONE visit (a waitlist entry or booking). Waitwhile sets its state to COMPLETE and adds the CANCELLED tag; the visit is kept, not deleted. By default the request asks Waitwhile to suppress the customer message; this may only stop the immediate cancellation notice, and scheduled reminders/follow-ups can still go out per the location's settings. With send_notifications=true Waitwhile may text/e-mail this ONE customer. POST /visits/{visitId}/cancel. |
waitwhile_add_customer_note | write | Add a customer note WRITE: add one staff note to a customer's record (optionally tied to a visit and location). Adds only; nothing is edited or sent to the customer. POST /customers/{customerId}/notes. |
waitwhile_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
waitwhile_request_feature | Request a missing feature Tell usefulapi that the user needs something the Waitwhile 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. | |
waitwhile_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Waitwhile tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
waitwhile_cancel_subscription | Cancel the Pro subscription Cancel the caller's Waitwhile Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run waitwhile_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper account | $9/mo · $90/yr | Unlimited |
Pro covers this Waitwhile server only. Subscribe with waitwhile_upgrade (it returns a Stripe Checkout link). Cancel any time with waitwhile_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running waitwhile_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 Waitwhile. The server calls the Waitwhile API with your own Waitwhile access, so it sees only the data that your account can see.
The login page asks for your Waitwhile API key. See Before you connect for where to find it.
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 Waitwhile 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 Waitwhile 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 Waitwhile.
Yes, if you approve it. 4 of the 29 Waitwhile tools can create or change data. The other 25 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Waitwhile server only. Run waitwhile_usage_status to see how many calls you used.
Ask the AI to run waitwhile_upgrade: it returns a Stripe Checkout link. To cancel, run waitwhile_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 waitwhile_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, 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.