Official MCP server for the Waitlister API — create waitlists and manage subscribers through AI assistants like Claude, Cursor, and more. Account-key
Connect Waitlister MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Official MCP server for the Waitlister API — create waitlists and manage subscribers through AI assistants like Claude, Cursor, and more. Account-key support: works on every plan. (Successor to the waitlister-mcp package.). The waitlister mcp mcp server is what makes that connection.
wl_acct_…)The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
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 calllist_waitlists — List every waitlist you own, with subscriber/view countsget_stats — Subscriber + view counters for a waitlist (cheap social proof)add_subscriber — Add a new subscriber to a waitlistlist_subscribers — List subscribers with pagination and sortingget_subscriber — Get details for a specific subscriber by ID or emailupdate_subscriber — Update a subscriber's name, phone, points, or metadatadelete_subscriber — Permanently delete a subscriber (irreversible)log_view — Record a waitlist page view for analyticsget_landing_page — Structured view of the hosted landing page: status, copy, theme, SEO, live URL, analyticscreate_landing_page — Create the page from structured fields (draft; one page per waitlist)update_landing_page — Update copy/theme/background/SEO; live pages update immediatelyConfiguration is passed through the environment: WAITLISTER_ACCOUNT_KEY, WAITLISTER_WAITLIST_KEY, WAITLISTER_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Waitlister MCP's toolset — create_waitlist, list_waitlists, get_stats and 11 more — is a fair guide to whether it matches your workflow. It is maintained by ilpr; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| 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 |
| list_waitlists | List every waitlist you own, with subscriber/view counts |
| get_stats | Subscriber + view counters for a waitlist (cheap social proof) |
| add_subscriber | Add a new subscriber to a waitlist |
| list_subscribers | List subscribers with pagination and sorting |
| get_subscriber | Get details for a specific subscriber by ID or email |
| update_subscriber | Update a subscriber's name, phone, points, or metadata |
| delete_subscriber | Permanently delete a subscriber (irreversible) |
| log_view | Record a waitlist page view for analytics |
| get_landing_page | Structured view of the hosted landing page: status, copy, theme, SEO, live URL, analytics |
| create_landing_page | Create the page from structured fields (draft; one page per waitlist) |
| update_landing_page | Update copy/theme/background/SEO; live pages update immediately |
| publish_landing_page | Go live at waitlister.me/p/{slug} (or unpublish) |
| generate_landing_page | AI-generate or AI-edit the whole page from a prompt (**1 AI credit per call**, ~20–50s) |
{
"mcpServers": {
"waitlister": {
"command": "npx",
"args": ["-y", "@waitlister/mcp"],
"env": {
"WAITLISTER_ACCOUNT_KEY": "wl_acct_your-key"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| WAITLISTER_ACCOUNT_KEY | Credential the server authenticates with. | Yes |
| WAITLISTER_WAITLIST_KEY | Credential the server authenticates with. | Yes |
| WAITLISTER_API_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.