MCP SERVER · OFFICIAL PROJECTRun a waitlist from the conversation — create it, collect and rank signups, and build and publish the hosted landing page.
LABSCO SUMMARY
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.
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
USE CASES
Create the waitlist with its landing page in the same call, adjust the headline and theme, then publish — the page stays a draft until you say so.
Describe the look you want and have the whole page generated, then revise it with the same tool rather than editing copy fields, which an AI page refuses.
Add them by email and read back the position and referral code. Doing it twice returns the existing record instead of creating a duplicate.
Page through the subscribers sorted by referral count or points, then open the ones at the top for their full record.
Award points to a subscriber and let the position recalculate, rather than editing an order by hand.
List every waitlist you own with its subscriber and view counts, then aim each following call at the one you mean by its key.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
add_subscriberAdd a new subscriber to a waitlist. Returns their position, referral code, and sign-up token. Idempotent per email: an existing email returns is_new_sign_up: false with their current position, not an error. Works on every plan.
create_landing_pageCreate the waitlist's hosted landing page from structured fields, as a draft (nothing goes live until publish_landing_page). One page per waitlist — returns a 409 error if one already exists (use update_landing_page then). headline is required. Works on every plan. Tip: when creating a new waitlist AND its page, use create_waitlist's landing_page parameter instead — one call.
create_waitlistCreate a new waitlist on your Waitlister account (requires an account key, works on every plan within its waitlist cap). Returns the waitlist key and a form_action_url that collects signups immediately. Pass landing_page to also provision the hosted landing page (as a draft — go live with publish_landing_page) in the same call. Note: waitlist names and URL slugs are unique across all of Waitlister — a taken name/slug is rejected with guidance to pick another.
delete_subscriberPermanently delete a subscriber (and their email history) from a waitlist by ID or email address. This cannot be undone. Counters and queue positions update asynchronously within a few seconds. Requires the Growth plan or higher.
generate_landing_pageGenerate a complete custom landing page from a natural-language prompt with Waitlister's AI builder (same engine as the dashboard), or edit the existing AI page with is_edit: true. COSTS 1 AI CREDIT per call (shared with the dashboard AI builder; errors with the balance when out of credits) — don't call repeatedly for small tweaks a human should review. Synchronous, typically 20-50 seconds. The result is saved as a draft: review in the dashboard or go live with publish_landing_page. The AI conversation is saved, so the dashboard's AI chat continues where this left off. After generating, the page is an AI page — see update_landing_page for what that changes.
get_landing_pageGet the structured view of a waitlist's hosted landing page: status (draft/published/unpublished), page_type (standard or ai), copy fields, theme, SEO, the live URL (null until published), and view/signup analytics. AI-built pages also return remaining AI credits. Works on every plan. 404 if the waitlist has no page yet — create one with create_landing_page.
get_statsGet a waitlist's subscriber and view counters — cheap social proof, works on every plan. Counters update asynchronously (within seconds of a signup or delete).
get_subscriberRetrieve detailed information about a specific subscriber by their ID or email address — position, points, referral info, metadata, location, and more. Requires the Growth plan or higher.
list_subscribersRetrieve a paginated list of a waitlist's subscribers, sortable by position, points, date, referral_count, or email. Requires the Growth plan or higher.
list_waitlistsList every waitlist your account owns, with subscriber and view counts (requires an account key).
log_viewRecord a view of a waitlist page — useful for tracking engagement and conversion rates when you host your own landing page.
publish_landing_pagePublish the landing page to its live URL (https://waitlister.me/p/{slug}, or the waitlist's custom domain) — or take it offline with unpublish: true. Publishing validates the page has an email field, a submit button, and a headline of at least 3 characters. API publishes skip the custom social-share (OG) image; publishing once from the dashboard generates it. Works on every plan.
update_landing_pageUpdate any subset of the landing page's structured fields. On a published page the change goes live immediately. IMPORTANT: on an AI-built page (page_type "ai"), the copy/structure fields (headline, description, button_text, collect_name, collect_phone, background) return a 409 error — edit those with generate_landing_page and is_edit: true; theme and seo still work here on both page types. Works on every plan.
update_subscriberUpdate an existing subscriber's name, phone, points, and/or custom metadata. Only include fields you want to change; updating points triggers a queue position recalculation. Requires the Growth plan or higher.
BEFORE YOU INSTALL
14 tools when we connected; the project documents 15. The missing one is get_account, which checks your plan and waitlist cap. The subscriber list, get, update and delete tools need a Growth plan or higher, and create_waitlist and list_waitlists need the account key (wl_acct_…).
WAITLISTER_API_KEY in your environment
All 5 documented setups run the server on your machine.
INSTALLATION
npm install -g @waitlister/mcp{
"mcpServers": {
"waitlister": {
"command": "npx",
"args": [
"-y",
"@waitlister/mcp"
],
"env": {
"WAITLISTER_ACCOUNT_KEY": "<YOUR_WAITLISTER_ACCOUNT_KEY>"
}
}
}
}claude mcp add waitlister --env WAITLISTER_ACCOUNT_KEY=<YOUR_WAITLISTER_ACCOUNT_KEY> -- npx -y @waitlister/mcp{
"mcpServers": {
"waitlister": {
"command": "waitlister-mcp",
"env": {
"WAITLISTER_ACCOUNT_KEY": "<YOUR_WAITLISTER_ACCOUNT_KEY>"
}
}
}
}{
"mcpServers": {
"waitlister": {
"command": "npx",
"args": [
"-y",
"@waitlister/mcp"
],
"env": {
"WAITLISTER_API_KEY": "<YOUR_WAITLISTER_API_KEY>",
"WAITLISTER_WAITLIST_KEY": "<YOUR_WAITLISTER_WAITLIST_KEY>"
}
}
}
}MCP servers
refgrow
AdsMCP
HumanTone
Egomessss