io.github.zexiro/waitloop
Agent-first waitlists: hosted signup pages with referral ranking. One tool call returns a live page.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http waitloop 'https://waitloop.dev/api/mcp' --header 'Authorization: <Bearer token: your Waitloop API key (create one at https://waitloop.dev/dashboard/keys)>'
{
"mcpServers": {
"waitloop": {
"type": "http",
"url": "https://waitloop.dev/api/mcp",
"headers": {
"Authorization": "<Bearer token: your Waitloop API key (create one at https://waitloop.dev/dashboard/keys)>"
}
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
● waitloop
Waitlists your agent can launch.
A hosted waitlist page with referral ranking, created by one MCP tool call. Agent-first: MCP server + JSON CLI + REST API. The dashboard is optional.
waitloop.dev · Docs · llms.txt
Your agent builds the product. Waitloop starts the line:
> create a waitlist for my new CLI tool, dark page, orange accent
● waitloop create_waitlist(...)
✓ live at https://waitloop.dev/w/ship-faster
Every waitlist gets a live hosted page, email capture, referral links (each signup gets a unique URL — when someone joins through it, the referrer moves up the list), stats, CSV export, webhooks, and an embeddable widget.
For agents
MCP (the primary interface):
claude mcp add --transport http waitloop https://waitloop.dev/api/mcp \
--header "Authorization: Bearer wl_YOUR_KEY"
8 tools: create_waitlist, list_waitlists, update_waitlist, delete_waitlist, get_stats, list_signups, export_signups, add_signup.
CLI — every command outputs structured JSON, designed for LLMs and pipelines:
WAITLOOP_API_KEY=wl_YOUR_KEY npx waitloop-cli waitlists:create --name "Acme Robots"
npx waitloop-cli stats acme-robots
npx waitloop-cli export acme-robots --format csv
REST:
curl -X POST https://waitloop.dev/api/v1/waitlists \
-H "Authorization: Bearer wl_YOUR_KEY" -H "Content-Type: application/json" \
-d '{"name": "Acme Robots"}'
Docs are agent-readable: llms.txt, and every docs page is raw markdown when you append .md.
Self-host
git clone https://github.com/zexiro/waitloop
cd waitloop
docker compose up -d
App on :3000, Postgres included, migrations run on boot. No license keys, no feature gates — everything in the cloud product works self-hosted. See self-hosting docs.
Development
pnpm install
pnpm --dir apps/waitloop dev
No database needed for local dev — it falls back to embedded Postgres (PGlite) under .data/. Log in at /login; without RESEND_API_KEY, the magic link is printed to the server log.
Repo layout
apps/waitloop— Next.js app: hosted pages, dashboard, REST API, MCP server, docspackages/cli— thewaitloop-clinpm package (npx waitloop-cli)skills/waitloop— agent skill (SKILL.md) for coding agents
License
Frequently asked questions
What is io.github.zexiro/waitloop?
Agent-first waitlists: hosted signup pages with referral ranking. One tool call returns a live page.
How do I install io.github.zexiro/waitloop?
It runs as a remote server. In Claude Code: claude mcp add --transport http waitloop 'https://waitloop.dev/api/mcp' --header 'Authorization: <Bearer token: your Waitloop API key (create one at https://waitloop.dev/dashboard/keys)>'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.zexiro/waitloop need an API key?
Yes. It expects Authorization, which you set in its configuration.
Is io.github.zexiro/waitloop open source?
Yes. Its code is on GitHub under the AGPL-3.0 license.
Who maintains io.github.zexiro/waitloop?
It is published by zexiro. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.