One call gets you a waitlist plus a signup URL that already works, and a second can put a page in front of it. The tools also say which actions are irreversible and which go live the moment they run, so an assistant knows where to stop and ask.
The official Waitlister client, in two halves. One works the queue: waitlists, subscribers, positions, points and referral counts. The other works the hosted landing page the waitlist sits behind — draft, edit, publish, or have the AI builder write the whole page from a prompt.
- A waitlist created in one call, returning its key and a form_action_url that collects signups straight away — optionally with its landing page provisioned as a draft in the same call
- add_subscriber returns position, referral code and sign-up token, and is idempotent per email: a repeat returns is_new_sign_up: false with the current position instead of an error
- Subscribers paged and sorted by position, points, date, referral_count or email; one looked up by ID or email; fields updated selectively, and a points change recalculates the queue position
- Subscriber and view counters on every plan, updating within seconds of a signup or a deletion
- The landing page as a structured record — status, copy, theme, SEO, live URL and analytics — created as a draft, edited field by field, and published to waitlister.me/p/{slug} or your own domain
- An entire page generated from a natural-language prompt by the same AI builder the dashboard uses, and edited the same way with is_edit
- Page views logged with visitor and referring domain when you host the landing page yourself
- A subscriber and their email history deleted for good, with the tool saying plainly that it cannot be undone
Node.js 18 or newer and a Waitlister account — the free plan is enough. Runs over stdio from npm as @waitlister/mcp. One credential of two: WAITLISTER_ACCOUNT_KEY, a wl_acct_ key from Settings that covers every waitlist you own, or the legacy per-waitlist WAITLISTER_API_KEY, which needs WAITLISTER_WAITLIST_KEY beside it and a Growth plan. Creating waitlists, adding subscribers and reading counters work on every plan; reading, updating and deleting subscriber records need Growth or higher. Each generate_landing_page call spends one AI credit and takes roughly 20 to 50 seconds.
One command plus a key — npm install -g @waitlister/mcp, then supply credentials