Waitlister

by ilpr

303 downloads

Not rated

GitHub Website

About

Official MCP server for the Waitlister API — create waitlists, add subscribers, and track signups through AI assistants like Claude, Cursor, and Windsurf

Details

Author: ilpr
Downloads: 303
Categories: Productivity, Other, AI, Marketing

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name Waitlister

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

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

JSON

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

JSON

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

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

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

JSON

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

JSON

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

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

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

JSON

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

JSON

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

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

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

JSON

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

JSON

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

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

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

JSON

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

JSON

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

From the repository

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

`create_waitlist`

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.

`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 discovering the cap from an error), remaining AI credits, and the key's name/created/last-used. An invalid or revoked key fails here cleanly, which distinguishes a dead key from a malformed request. Requires an account key (wl_acct_…) and works on every plan. Never returns the key itself.

`list_waitlists`

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

`get_stats`

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

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

`list_subscribers`

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

`get_subscriber`

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.

`update_subscriber`

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.

`delete_subscriber`

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.

`log_view`

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

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

`create_landing_page`

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.

`update_landing_page`

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.

`publish_landing_page`

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.

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

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

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

McpServers

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

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

AI pages vs standard pages:aftergenerate_landing_page, the page's copy lives inside the generated page —update_landing_pagerejects copy/structure fields with guidance to usegenerate_landing_page+is_editinstead (themeandseostill update normally). Generated pages are saved as drafts, and the AI conversation carries over to the dashboard's AI chat.

- Node.js 18+
- AWaitlisteraccount — the free plan works
- Anaccount API key(recommended), or a per-waitlist API key (Growth plan+)

Account key (recommended — works on every plan, covers every waitlist you own):
- Log in to Waitlister
- Go toSettings→API keys→ create a key (wl_acct_…)

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

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 itswaitlist_keyparameter (ask the assistant to runlist_waitlistsfirst).

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

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

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

Go toSettings→MCP→Add new MCP serverand use the same configuration.

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

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

WAITLISTER_ACCOUNT_KEY=wl_acct_your-key npm run inspect

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

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.

Third-party sharing.Waitlister does not sell your data. Landing-page designs requested throughgenerate_landing_pageare 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.

Persistent memory for any AI assistant. Zero token cost until recall. Stores memories in local SQLite, ranks by 6-factor scoring, returns results 79% smaller than JSON. Works with Claude, ChatGPT, Grok, Cursor, Windsurf, and any MCP client.

After Effects MCP is a full-featured automation bridge that connects AI clients (like VS Code, Claude Desktop, and Claude Code) to Adobe After Effects through MCP, enabling scripted control of compositions, layers, effects, keyframes/graph easing, presets, markers, audio levels, waveform analysis, and effect discovery via a live bridge panel.

Project management your AI can actually run — connect Claude, ChatGPT, Cursor & Codex to one board over MCP.

AIOProductOS spine over MCP — customers, revenue, feedback, work, analytics on one typed record.

The memory layer for AI coding tools. Local-first, semantic, 9 MCP tools with consolidation and project scoping. Works with Claude Code, Cursor, Windsurf & any MCP client.

One MCP server for Claude, ChatGPT & Gemini — wraps your ERPs, CRMs, APIs and knowledge base into a single governed endpoint.

Run your field service business from Claude: answer calls, book and dispatch jobs, build estimates, chase invoices. Built for HVAC, plumbing, electrical, roofing and pest control.

Complete Swiss accounting integration for Bexio via MCP. Works with Claude Desktop, n8n, and any MCP client. 221 tools for invoices, contacts, projects & more.

Persistent memory MCP server for Claude Desktop — remembers context, time, and topics across sessions

An MCP extension for the Claude Desktop application that enables automation and integration.

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Details

Jump to

Setting up with Highlight

From the repository

Claude Desktop

Cursor

Claude Code

create_waitlist

get_account

list_waitlists

get_stats

add_subscriber

list_subscribers

get_subscriber

update_subscriber

delete_subscriber

log_view

get_landing_page

create_landing_page

update_landing_page

publish_landing_page

generate_landing_page

Claude Desktop / Cursor

McpServers

Install

More like this

Sequential Thinking

Time

Filesystem

EverArt

Google Drive

Context 7

`create_waitlist`

`get_account`

`list_waitlists`

`get_stats`

`add_subscriber`

`list_subscribers`

`get_subscriber`

`update_subscriber`

`delete_subscriber`

`log_view`

`get_landing_page`

`create_landing_page`

`update_landing_page`

`publish_landing_page`

`generate_landing_page`