Back to Guides

How to Create Your Waitlist with Roo Code

Connect Roo Code to the UseWait MCP server and let it build your waitlist inside VS Code: page, slug, confirmation email and custom domain. One config, one prompt.

Roo Code is a capable open-source agent that lives in VS Code and speaks MCP fluently. With the UseWait server connected it turns a short brief into a live waitlist: it picks a slug, writes the page, sets up the confirmation email and can connect a custom domain. Here is how to create your waitlist with Roo Code.

Set up your waitlist with Roo Code

1

Create a UseWait API key

In UseWait, open Dashboard, Settings, API Keys and create a key (uw_live_...). Copy it once. The free plan includes full API and MCP access.

2

Add the server in Roo Code

Open the Roo Code MCP panel and edit the project .roo/mcp.json or the global MCP settings. Paste the snippet below with your key. The type must be "streamable-http" with the hyphen: Roo Code cannot infer the transport from a url alone and will error without it.

.roo/mcp.json (or the global MCP settings)
{
  "mcpServers": {
    "usewait": {
      "type": "streamable-http",
      "url": "https://usewait.com/api/mcp/mcp",
      "headers": {
        "Authorization": "Bearer uw_live_YOUR_KEY"
      }
    }
  }
}
3

Ask the agent

Prompt Roo Code: "Set up a waitlist for my design newsletter and make the page minimal and typographic." It reads get_started for the flow and get_page_format for the page contract, then creates the waitlist and writes the page, live at usewait.com/w/<slug>.

4

Polish and grow

Ask it to connect your domain (it gives you the exact A record), upload assets to the CDN, or manage the confirmation email. Call list_entries whenever you want to see signups and referral stats.

What Roo Code handles for you

Picks and claims a unique slug
Writes page code matched to your brand
Creates the confirmation email template
Uploads logos and images to the CDN
Walks you through custom domain DNS
Reads signups and referral stats on demand

Frequently asked questions

How does Roo Code connect to a remote MCP server?

Through a streamable HTTP entry: type set to streamable-http, the url of the server, and a headers object with your Authorization token. Roo Code reaches UseWait's hosted endpoint directly.

Why does the config need a type?

For any URL-based MCP server Roo Code requires an explicit type. Omitting it causes an immediate error because the transport cannot be inferred from the URL.

Does this work in the Cline family too?

The same UseWait endpoint works with any MCP client. The exact field names vary, but the pattern is always the server URL plus an Authorization header carrying your uw_live_ key.

Get your API key and let Roo Code launch it

Free plan includes full API and MCP access. Your agent does the rest.

Create your free API key

Full reference at docs.usewait.com and a quick overview on the developers page.