Skip to main content
Glama
@waitlister/mcp

@waitlister/mcp

by ilpr

Waitlister MCP Server — @waitlister/mcp

An MCP (Model Context Protocol) server that connects AI assistants like Claude, Cursor, and Windsurf to the Waitlister API. Create waitlists and manage subscribers through natural language.

This is the official package, superseding waitlister-mcp (1.0.x). Existing waitlister-mcp configurations keep working, but new setups should use @waitlister/mcp — it adds account-key support, waitlist creation, stats, and deletion, and works on every plan.

What Can You Do With This?

Once connected, you can ask your AI assistant things like:

  • "Is my Waitlister key working, and can I create another waitlist?"

  • "Create a waitlist for my new product and give me the signup form URL"

  • "Launch my waitlist with a landing page — dark theme — and publish it"

  • "Change the page headline to 'Join 500+ others'"

  • "Generate a landing page: bold, dev-tool aesthetic" (AI builder, 1 credit)

  • "Add test@gmail.com to my waitlist"

  • "How many subscribers do I have?"

  • "Look up the subscriber john@acme.com"

  • "Update John's points to 500"

  • "Show me the top 10 subscribers by referral count"

  • "Tag everyone with 3+ referrals as beta, then list who's tagged beta"

Related MCP server: MCP Memory

Tools

Tool

Description

Plan

get_account

Check the key and what the account may do: plan, waitlist count vs cap, whether the next create_waitlist would succeed, AI credits. Read-only

Every plan (account key)

create_waitlist

Create a new waitlist; returns its key + a form URL that collects signups immediately. Optionally provisions its landing page (draft) in the same call

Every plan (account key)

list_waitlists

List every waitlist you own, with subscriber/view counts

Every plan (account key)

get_stats

Subscriber + view counters for a waitlist

Every plan

add_subscriber

Add a new subscriber to a waitlist

Every plan

list_subscribers

List subscribers with pagination and sorting, optionally only those with one tag

Growth+

get_subscriber

Get details for a specific subscriber by ID or email, including tags

Growth+

update_subscriber

Update a subscriber's name, phone, points, metadata, or tags (add, remove, or replace; new tag names are created)

Growth+

delete_subscriber

Permanently delete a subscriber (irreversible)

Growth+

list_tags

List the waitlist's subscriber tags and how many subscribers have each

Growth+

log_view

Record a waitlist page view for analytics

Every plan

get_landing_page

Structured view of the hosted landing page: status, copy, theme, SEO, live URL, analytics

Every plan

create_landing_page

Create the page from structured fields (draft; one page per waitlist)

Every plan

update_landing_page

Update copy/theme/background/SEO; live pages update immediately

Every plan

publish_landing_page

Go live at waitlister.me/p/{slug}

Every plan

unpublish_landing_page

Take the live page offline (page and subscribers are kept)

Every plan

generate_landing_page

AI-generate or AI-edit the whole page from a prompt (1 AI credit per call, ~20–50s)

Every plan

AI pages vs standard pages: after generate_landing_page, the page's copy lives inside the generated page — update_landing_page rejects copy/structure fields with guidance to use generate_landing_page + is_edit instead (theme and seo still update normally). Generated pages are saved as drafts, and the AI conversation carries over to the dashboard's AI chat.

Prerequisites

  • Node.js 18+

  • A Waitlister account — the free plan works

  • An account API key (recommended), or a per-waitlist API key (Growth plan+)

Getting Your Key

Account key (recommended — works on every plan, covers every waitlist you own):

  1. Log in to Waitlister

  2. Go to Settings → API keys → create a key (wl_acct_…)

Per-waitlist key (legacy, Growth plan+): waitlist → Integrations → API access. You'll also need the waitlist key from the waitlist's settings.

Installation

No installation needed — just configure your MCP client:

{
  "mcpServers": {
    "waitlister": {
      "command": "npx",
      "args": ["-y", "@waitlister/mcp"],
      "env": {
        "WAITLISTER_ACCOUNT_KEY": "wl_acct_your-key"
      }
    }
  }
}

With an account key you can optionally add "WAITLISTER_WAITLIST_KEY": "your-waitlist-key" to set a default waitlist — otherwise each tool call can target any waitlist you own via its waitlist_key parameter (ask the assistant to run list_waitlists first).

{
  "mcpServers": {
    "waitlister": {
      "command": "npx",
      "args": ["-y", "@waitlister/mcp"],
      "env": {
        "WAITLISTER_API_KEY": "your-api-key",
        "WAITLISTER_WAITLIST_KEY": "your-waitlist-key"
      }
    }
  }
}

Global install

npm install -g @waitlister/mcp

Then configure with "command": "waitlister-mcp" and the same env.

Setup by Client

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows) with the JSON above.

Cursor

Go to Settings → MCP → Add new MCP server and use the same configuration.

Claude Code

claude mcp add waitlister --env WAITLISTER_ACCOUNT_KEY=wl_acct_your-key -- npx -y @waitlister/mcp

Environment Variables

Variable

Required

Description

WAITLISTER_ACCOUNT_KEY

One of the two keys

Account API key (wl_acct_…, Settings → API keys). Every plan; every waitlist you own; unlocks create_waitlist/list_waitlists.

WAITLISTER_API_KEY

One of the two keys

Per-waitlist API key (Growth+). Requires WAITLISTER_WAITLIST_KEY.

WAITLISTER_WAITLIST_KEY

With WAITLISTER_API_KEY; optional otherwise

Default waitlist for the waitlist-scoped tools.

Notes

  • Uniqueness: waitlist names and URL slugs are unique across all of Waitlister. create_waitlist rejects a taken name/slug with a message telling you what to change.

  • Async counters: signups and deletions update get_stats counters and queue positions within a few seconds, not instantly.

  • Plan gating: creating waitlists, adding subscribers, and stats work on every plan (lower rate limits on free plans). Reading/updating/deleting subscriber data requires Growth or higher — see rate limits.

  • Built on the official waitlister SDK (typed errors, automatic retries with backoff).

Development

git clone https://github.com/ilpr/waitlister-mcp.git
cd waitlister-mcp
npm install
npm run build

Test with the MCP Inspector:

WAITLISTER_ACCOUNT_KEY=wl_acct_your-key npm run inspect

Privacy

Full policy: https://waitlister.me/privacy-policy

What this extension collects. Nothing on its own. It runs locally on your machine and holds no database, no telemetry, and no analytics. It stores only the credential you enter — your Waitlister account API key — which Claude Desktop keeps in your operating system's secure credential storage.

What it sends, and where. The extension sends the API requests you ask it to make, over HTTPS, to the Waitlister API at https://waitlister.me/api/v1, authenticated with your key. That means the arguments you (or Claude, on your instruction) pass to a tool: for example a waitlist name, landing-page copy, or a subscriber's email address when you add one. Nothing is sent anywhere else. There are no third-party analytics, error trackers, or intermediary services in the path.

How requests identify themselves. Like any SDK, those requests carry identification headers so Waitlister can tell agent traffic from ordinary API traffic and support it properly: this package's name and version (waitlister-mcp/1.4.0), the SDK version, the Node version, and the name and version your MCP host announces in the protocol handshake (e.g. claude-ai/0.1.0). No prompt text, no file paths, no machine or user identifiers. Nothing extra is sent — these ride along on requests you already made.

How that data is used and retained. Data reaching the Waitlister API is handled under the Waitlister privacy policy linked above — the same terms that apply when you use the web dashboard. Waitlist and subscriber records persist in your Waitlister account until you delete them, from the dashboard or with the delete_subscriber tool. The extension itself retains nothing after a request completes.

Third-party sharing. Waitlister does not sell your data. Landing-page designs requested through generate_landing_page are produced by Waitlister's AI page builder, which passes your design prompt to a third-party model provider; see the privacy policy for the current subprocessor list.

Your controls. Revoke the API key at any time in Waitlister under Settings → API keys, which immediately stops this extension from reaching your account. Uninstalling the extension removes the stored key from your machine. Account and data deletion requests follow the process in the privacy policy.

Contact. https://waitlister.me/contact

License

MIT — see LICENSE.

Available Tools

14 tools
add_subscriberA

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. Works on every plan.

Inputs: email (required), name, phone, metadata, +2 more.

create_landing_pageA

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.

Inputs: headline (required), seo, theme, background, +5 more.

create_waitlistA

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 — a taken name/slug is rejected with guidance to pick another.

Inputs: name (required), slug, category, description, +3 more.

delete_subscriberA

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.

Inputs: id_or_email (required), waitlist_key.

generate_landing_pageA

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 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.

Inputs: prompt (required), is_edit, waitlist_key.

get_landing_pageA
Read-only

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.

Inputs: waitlist_key.

get_statsA

Get a waitlist's subscriber and view counters — cheap social proof, works on every plan. Counters update asynchronously (within seconds of a signup or delete).

Inputs: waitlist_key.

get_subscriberA

Retrieve 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.

Inputs: id_or_email (required), waitlist_key.

list_subscribersA

Retrieve a paginated list of a waitlist's subscribers, sortable by position, points, date, referral_count, or email. Requires the Growth plan or higher.

Inputs: page, limit, sort_by, sort_dir, +1 more.

list_waitlistsA

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

Inputs: no named parameters.

log_viewA

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

Inputs: visitor_id, waitlist_key, referring_domain.

publish_landing_pageA
Idempotent

Publish 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.

Inputs: unpublish, waitlist_key.

update_landing_pageA
Idempotent

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 on every plan.

Inputs: seo, theme, headline, background, +5 more.

update_subscriberA

Update 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.

Inputs: id_or_email (required), name, phone, points, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.3/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: waitlists (create/list), stats, subscribers (add/list/get/update/delete), views, and landing pages (get/create/update/publish/generate). There is no overlap between tools; even get_stats and get_landing_page serve different purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (create_waitlist, list_subscribers, publish_landing_page, etc.). Verbs are appropriate and uniformly placed at the start, making the set predictable and easy to navigate.

    Tool Count5/5

    14 tools is well within the ideal 3-15 range and each tool serves a clear purpose in managing waitlists, subscribers, and landing pages. The count feels proportionate to the domain's complexity without being bloated.

    Completeness3/5

    The waitlist lifecycle is incomplete: you can create and list waitlists but cannot update or delete them. There is also no single-waitlist getter (only list), which forces agents to filter through the list. However, subscriber and landing page coverage is thorough, so the gaps are workable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers