mcpField
W
waitloop

waitloop

Remote
waitloop.devBusiness & Marketing0Updated 16w ago

About waitloop

waitloop is an agent-oriented waitlist service for creating hosted signup pages and managing signups. Referral rankings and MCP, CLI, and REST interfaces support pre-launch audience collection.

Key features

  1. 01Create hosted waitlist pages
  2. 02Capture email and rank referrals
  3. 03View stats and export CSV
  4. 04Provide webhooks and an embed widget
  5. 05Support MCP, JSON CLI, and REST API

Use cases

  1. 01Collect signups before a product launch
  2. 02Rank waitlist members through referral links
  3. 03Export signup data for follow-up

MCP support

waitloop provides an MCP server with tools to create, list, update, and delete waitlists, as well as inspect stats, signups, and exports.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://waitloop.dev/api/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://waitloop.dev/api/mcpAuth required

Tools

Details

From the project README

● 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, docs
  • packages/cli — the waitloop-cli npm package (npx waitloop-cli)
  • skills/waitloop — agent skill (SKILL.md) for coding agents

License

AGPL-3.0

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.