Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Agent-first waitlists: hosted signup pages with referral ranking. One tool call returns a live page.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http waitloop https://waitloop.dev/api/mcp --header 'Authorization: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"waitloop": {
"url": "https://waitloop.dev/api/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"waitloop": {
"type": "http",
"url": "https://waitloop.dev/api/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account zexiro, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, AI Deprecations
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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.
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.
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.
apps/waitloop — Next.js app: hosted pages, dashboard, REST API, MCP server, docspackages/cli — the waitloop-cli npm package (npx waitloop-cli)skills/waitloop — agent skill (SKILL.md) for coding agentsAGPL-3.0