Premium feature · MCP integration

Run your waitlist
with Claude.

Name: Waitlist App
Author: Waitlist App

Connect Waitlist App Premium to Claude. Add walk-ins, send SMS, mark tables seated — in plain English, from any conversation.

Set up in 3 steps Contact us

Enterprise · $749/mo · purchased through our team

How it works

From a sentence to a sent SMS — in seconds.

You

"Add Sarah for 6pm, party of 2"

Claude

Picks the right tool, fills in the args

Waitlist MCP

Authenticates & runs the action

Customer

Gets an SMS with their place in line

Setup

Three steps. About 5 minutes.

Get an API token.

Tokens authenticate Claude to your queue without exposing your account password. Each token is shown once — copy it straight into a password manager.

a. Open your dashboard and scroll to the API Tokens section.
b. Name the token (e.g. Claude Desktop) and click Create Token.
c. Copy the token from the amber banner — you won't see it again.

The API Tokens section unlocks on the Enterprise plan ($749/mo, purchased through our team). On the Pro plan you'll see an upgrade card in the same spot. Contact us →

Connect your Claude client.

Pick how you use Claude. Each tab below has the exact config to paste — replace YOUR_TOKEN_HERE with the token from step 1.

Edit your claude_desktop_config.json:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "waitlistapp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://car.0rder.app/mcp",
        "--header",
        "Authorization: Bearer YOUR_TOKEN_HERE"
      ]
    }
  }
}

Then restart Claude Desktop. The waitlist tools appear in the tools menu.

Available on Claude.ai Pro, Team, and Enterprise plans.

1 Open Claude.ai → Settings → Integrations.
2 Click Add custom integration.
3

Server URL — copy:

https://car.0rder.app/mcp
4 Authentication — choose Bearer token, paste your token from step 1.
5 Save. Toggle the integration on in any new chat.

Run this in your terminal — Claude Code stores it in your project's MCP config:

terminal

claude mcp add waitlistapp https://car.0rder.app/mcp \
  --header "Authorization: Bearer YOUR_TOKEN_HERE"

Verify with claude mcp list.

Talk to Claude.

Open a chat with the integration enabled and describe what you want. Claude picks the right tools and runs them.

Add Sarah, Mike, Priya, John, and David to my waitlist — party of 2 each, here for the 6pm seating. Then text Sarah she's on the list.

Adding all five now.

add_entry name="Sarah", party_size=2 #3

add_entry name="Mike", party_size=2 #4

add_entry name="Priya", party_size=2 #5

add_entry name="John", party_size=2 #6

add_entry name="David", party_size=2 #7

notify_entry id=Sarah's id, event="added" SMS sent

Done. Sarah is #3, Mike #4, Priya #5, John #6, David #7. Sarah just got a text confirming she's on the list. Want me to text the rest?

Reference

What Claude can do.

13 tools across queue management, customer notifications, and embedded widgets. Claude reads the schema automatically — you don't have to memorize anything.

Queue

list_queue
See everyone currently waiting.
add_entry
Add a walk-in or booking.
update_entry
Change name, party size, contact info.
remove_entry
Cancel an entry.

Notifications

notify_entry
Send the SMS template for a queue event (added / notified / seated).
mark_seated
Mark a party seated & auto-send the seated SMS.
send_sms
Send a custom SMS to any number via your Twilio integration.

Embed Widgets

widgets_list
List your embeddable widgets.
widget_get
Inspect a widget's schema and domains.
widget_entries_list
List entries from an embedded form.
widget_entry_search
Find an entry by name or email.
widget_entry_update_status
Move entries through their lifecycle.

The model

One account, every mode, one report.

Waitlist App is organized around a few ideas that keep a whole operation coherent — modes as lenses, stations as the backbone, and a single place everything rolls up into.

Stations

Organization → Locations → Stations is the backbone. A station is a cross-mode endpoint with stackable features you toggle on.

Check-in, pick-an-option, point-of-sale, inventory, collect-details
Pickup, kitchen & delivery are planned
One station can serve several modes at once
Managed in the shared Business ▸ Stations area — a "vendor" is a station with point-of-sale on

Event check-in

People identify — scan a personal QR, tap an employee/member ID, or just a name — then the station's features drive what happens next.

Just count, pick an option (e.g. a meal), buy an item, or fill a short form
Crew register once — one personal QR works at every station in the event
Cross-vendor rules: one per vendor, one event-wide, or unlimited-but-counted

Business reporting

Every mode records a business event at fulfilment through a single analytics gateway, so everything rolls up into one place.

Check-ins, paid orders, ticket sales & waitlist adds land on the same source
Reports live in the shared Analytics area
Counts and revenue across every mode — per location and per station

Modes (Waitlist, Ticketing, Fulfilment, Memberships, Event check-in, Creator) are lenses over one shared account — your customers and settings persist across every one, and an account is entitled to some modes while others show locked.

Security

Built for shared workspaces.

Token-scoped, revocable

Issue a token per device. Revoke instantly from your dashboard if a laptop walks away.

Encrypted credentials

Twilio account credentials are stored with industry-standard AES-256 envelope encryption and never returned to clients.

Your queue, your data

Tools only ever see entries owned by your account. No cross-tenant access, no data sold to third parties.

Ready to talk to your queue?

The Enterprise plan ($749/mo) unlocks the MCP server, server-side SMS, and unlimited tokens — purchased through our team.

Waitlist App assistant

Run your waitlist with Claude.