@Waitlister/

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:

• "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 [email protected] to my waitlist"
• "How many subscribers do I have?"
• "Look up the subscriber [email protected]"
• "Update John's points to 500"
• "Show me the top 10 subscribers by referral count"

Tools

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

Using npx (recommended)

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

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

Links

• Waitlister — create waitlists for your product launches
• API Documentation
• MCP Protocol

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