Waitlister MCP server

Read from the package source without running it. The installed server may list more.

• add_subscriber

  Add 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. If the waitlist uses double opt-in or welcome emails, the subscriber is emailed, exactly as with a form signup. Works on every plan.

• create_landing_pagewrite action

  Create 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_waitlistwrite action

  Create 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

• delete_subscriberwrite action

  Permanently 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_page

  Generate 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 re

• get_account

  Check the configured API key and what this account may do — the cheapest first call, and the one to make when anything looks misconfigured. Returns the account, the plan name, whether the general API is available, how many waitlists the account has against its cap, whether creating another would succeed right now (can_create — a true dry run, so check it before create_waitlist rather than discover

• get_landing_page

  Get 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_stats

  Get a waitlist's subscriber and view counters. Works on every plan. Counters update asynchronously (within seconds of a signup or delete).

• get_subscriber

  Retrieve detailed information about a specific subscriber by their ID or email address — position, points, referral info, tags, metadata, location, and more. Requires the Growth plan or higher.

• list_subscribers

  Retrieve a paginated list of a waitlist's subscribers (each with its tags), sortable by position, points, date, referral_count, or email, and optionally filtered to one tag. Requires the Growth plan or higher.

• list_tags

  List a waitlist's subscriber tags (the dashboard's Tags column) and how many subscribers have each. Use these names with list_subscribers' tag filter and update_subscriber's add_tags/remove_tags. Requires the Growth plan or higher.

• list_waitlists

  List every waitlist your account owns, with subscriber and view counts (requires an account key).

• log_view

  Record a view of a waitlist page — useful for tracking engagement and conversion rates when you host your own landing page.

• publish_landing_pagewrite action

  Publish the landing page to its live URL (https://waitlister.me/p/{slug}, or the waitlist's custom domain), making it publicly visible. 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. To take a page offline, use unpublish_landing_page.

• unpublish_landing_page

  Take the published landing page offline (status becomes "unpublished"); its URL stops serving the page and stops collecting signups. The page and its subscribers are kept, and publish_landing_page brings it back. Works on every plan.

• update_landing_pagewrite action

  Update 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

• update_subscriberwrite action

  Update an existing subscriber's name, phone, points, custom metadata, and/or tags. Only include fields you want to change; updating points triggers a queue position recalculation. Tags are named case-insensitively (or by id): add_tags and remove_tags change some, tags replaces the whole set. A tag name the waitlist doesn't have yet is created, so call list_tags first and reuse an existing name rat

• Code scan7 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 11 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

83/100

higher than 65% of 48,243 servers

Tools

17

the typical server has 7

Tools that change things

35%

typical: 0%. Fewer write tools means less an agent can break

Downloads a week

84

more than 58% of 12,306 servers with a package

Waitlister: common questions

Is Waitlister MCP server safe?

Mostly: it is graded B (83/100). Read the Waitlister safety report

How do I install Waitlister?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Waitlister need an API key?

Yes. The registry entry asks for WAITLISTER_ACCOUNT_KEY, WAITLISTER_API_KEY.

Is Waitlister maintained?

The last commit was 18 days ago (2026-10-19). The latest release is v1.5.0.

How does Waitlister compare with other MCP servers?

safety score 83/100 (higher than 65% of 48,243 servers); tools 17 (the typical server has 7); tools that change things 35% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.