@enlistdev/mcp

MCP server for Enlist.

Add a waitlist to any project in one agent prompt. Connect once, your agent handles the rest: creates the waitlist, wires the signup endpoint, renders the response. No install. No key leaks. No extra setup.

Remote (recommended)

No install. Configure your key once. Your agent has immediate access.

Claude Code

claude mcp add --transport http enlist https://api.enlist.dev/mcp \
  --header "Authorization: Bearer en_live_your_key"

Cursor (~/.cursor/mcp.json) or Claude Desktop:

{
  "mcpServers": {
    "enlist": {
      "url": "https://api.enlist.dev/mcp",
      "headers": { "Authorization": "Bearer en_live_your_key" }
    }
  }
}

Local (stdio)

The remote server above needs no install and stays the recommended transport. Reach for this one when your client does not speak streamable HTTP, or when you want to point an agent at a non-production API.

Both transports expose identical tools — the remote endpoint imports them from this package — so this is a choice of transport, not of capability. The local server still calls the Enlist API over the network; only the client-to-server hop is local.

{
  "mcpServers": {
    "enlist": {
      "command": "npx",
      "args": ["-y", "@enlistdev/mcp"],
      "env": { "ENLIST_API_KEY": "en_live_your_key" }
    }
  }
}

Set ENLIST_BASE_URL to target a self-hosted or local API:

"env": {
  "ENLIST_API_KEY": "en_live_your_key",
  "ENLIST_BASE_URL": "http://localhost:3000"
}

Tools

| Tool | Does | | ---------------------- | ---------------------------------------------------- | | create_waitlist | Create a named waitlist, ready for collection | | list_waitlists | List all waitlists with live signup counts | | add_signup | Add an email, send signup email, return confirmation | | list_signups | Browse signups with status and utm source | | get_waitlist_stats | Signup trends, email engagement, top referrers | | get_signup_position | Look up one email's position and status | | remove_signup | Remove a signup by id; no positions shift | | list_waitlist_fields | List the custom field definitions for a waitlist | | update_waitlist | Rename a waitlist; ids and signups are untouched |

There is no delete-waitlist tool, by design. remove_signup takes one person off a list, but destroying a whole list of email addresses is not something an agent can do here — it is a dashboard action, or a deliberate DELETE /v1/waitlists/:id call over the REST API. update_waitlist only changes an internal label and is safe.

add_signup returns the new signup's own referral_code alongside position and total, and takes an optional referralCode — the one from the share link the person followed — which credits its owner. A code that is unknown, malformed, from another waitlist, or the signer's own is ignored rather than rejected, so an agent can pass a ?ref param on a hunch without risking the signup.

The API key is configured once on the server — it is never a tool argument, so an agent cannot leak it into a prompt or a file.

Programmatic use

import { createEnlistMcpServer } from '@enlistdev/mcp';

const server = createEnlistMcpServer({ apiKey: process.env.ENLIST_API_KEY! });
await server.connect(transport);

registerEnlistTools(server, enlistClient) is also exported if you want the tools on a server you already own.

MIT