Other · Local MCP server
Waitlister
Create waitlists, landing pages, manage subscribers, referrals, and view stats on Waitlister.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ilpr/waitlister- Version
- 1.4.0
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-30
- Updated
- 2026-08-30
- Publisher
- ilpr (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/ilpr) · how
- Repository
- github.com/ilpr/waitlister-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @waitlister/mcp | 1.4.0 | stdio |
How to connect Waitlister
Waitlister runs locally from a Node.js package published to the npm registry: @waitlister/mcp version 1.4.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @waitlister/mcp@1.4.0. It reads these environment variables: WAITLISTER_ACCOUNT_KEY (secret), WAITLISTER_API_KEY (secret) and WAITLISTER_WAITLIST_KEY; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"waitlister": {
"command": "npx",
"args": [
"-y",
"@waitlister/mcp@1.4.0"
],
"env": {
"WAITLISTER_ACCOUNT_KEY": "<secret>",
"WAITLISTER_API_KEY": "<secret>",
"WAITLISTER_WAITLIST_KEY": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from ilpr (GitHub)
| Server | Runs |
|---|---|
| Shruwd MCPSet up a brand, read its AI-search visibility, and act on diagnostic findings. | Remote & Local · HTTP, stdioLive check: sign-in required |
More other servers
| Server | Runs |
|---|---|
| WaAPIMessaging tools for AI agents: send messages, manage chats, groups and channels. | Remote · HTTPLive check: sign-in required |
| WacheteCreate, read and monitor Wachete website-change wachets for a signed-in user. | Remote · HTTPLive check: sign-in required |
| Waggle MCPPersistent graph-backed conversational memory for AI agents. | Local · stdio |
| WaitingForPowerTracks U.S. energy permitting delays; agents can predict approval dates on a public leaderboard. | Remote · HTTPLive check: ✓ handshake |
| WaitloopAgent-first waitlists: hosted signup pages with referral ranking. One tool call returns a live page. | Remote · HTTPLive check: ✗ no handshake |
| WAKE ProtocolA post-mortem succession protocol for AI agents. Black Box, handoff, time-locks. | Local · stdio |
| Walk-Forward ValidatorWalk-Forward Efficiency, parameter-stability scoring, and WFO window generation. | Remote · HTTPLive check: sign-in required |
| WalkscoreWalk Score MCP - wraps the Walk Score API (walkscore.com) | Remote · HTTPLive check: ✓ handshake |