Waitloop

io.github.zexiroPublished by GitHub account zexirov0.1.0Updated Oct 24, 2026

Agent-first waitlists: hosted signup pages with referral ranking. One tool call returns a live page.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Waitloop is a hosted waitlist service whose MCP server lets an assistant create, manage and analyze signup pages with referral ranking in one tool call.

What you can do
  • Create, update and delete hosted waitlist pages with names, themes and accents
  • List existing waitlists and add signups manually
  • Read signup statistics and browse captured signups
  • Export signups, for example as CSV
  • Each waitlist gets a live page, email capture, referral links, webhooks and an embeddable widget
When to use it
Useful when you want an assistant to stand up a launch waitlist page for a new product or tool, then track signups, referrals and stats without leaving the chat or opening a dashboard.
Requirements
Remote MCP endpoint over streamable HTTP; a Waitloop API key sent as a bearer token in the Authorization header, created in the Waitloop dashboard. No local runtime or packages needed.
Before you install
The API key grants access to your waitlists and signup data, so keep it out of shared logs and prompts. Tools can create, update and delete waitlists and add signups, which changes live public pages and collected data. Signup emails and referral data are stored on the hosted service.

Installation

In SourceWeft

  1. Open Waitloop in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.zexiro%2Fwaitloop/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "waitloop": {
      "type": "http",
      "url": "https://waitloop.dev/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

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

bash
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:

bash
WAITLOOP_API_KEY=wl_YOUR_KEY npx waitloop-cli waitlists:create --name "Acme Robots"npx waitloop-cli stats acme-robotsnpx waitloop-cli export acme-robots --format csv

REST:

bash
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

bash
git clone https://github.com/zexiro/waitloopcd waitloopdocker 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

bash
pnpm installpnpm --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

Source: README.md at commit 4860ffa

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts