Add a waitlist to Remix.

An action function runs on the server and returns the position. useFetcher keeps the user on the page.

app/routes/waitlist.ts

import { json } from '@remix-run/node';import { Enlist } from '@enlistdev/sdk';const enlist = new Enlist({ apiKey: process.env.ENLIST_API_KEY! });export async function action({ request }: { request: Request }) {  const form = await request.formData();  const email = form.get('email') as string;  const signup = await enlist.waitlists.addSignup(    process.env.WAITLIST_ID!,    { email },  );  return json({ position: signup.position, total: signup.total });}

What you get

Position in the response. Email on its way. Nothing else to wire up.

Position assigned server-side

Inside a locked transaction. The signup response already contains the position and total — no polling, no second request needed to render "you're #47".

Signup email included

Sent via your email provider with the position in the body. Delivery, open, and click state is written back onto the signup row.

One key, three entry points

REST, TypeScript SDK, and an MCP server for coding agents. All the same API key, all the same response shape.

Wire it into your agent too

Add the MCP server and prompt your coding agent — it creates the waitlist and wires the handler in one shot.

Get an API key MCP setup