Skip to main content
Subscriber.dev sends the emails your product sends automatically, like a welcome email when someone signs up, a reminder before their trial ends, or an announcement to everyone. They go out through your own email provider. There’s no dashboard: you set it up and run it through your AI agent over MCP, the CLI, or the REST API.

Quickstart

Sign in, connect a provider and send your first workflow email.

Connect your AI agent

Add the MCP server to Claude, Cursor or any MCP client.

Workflows

Email and webhook steps, delays, templates and Stripe triggers.

API reference

Every endpoint, with request and response examples.

​
How it fits together

There are four things to know about:
  • Workspaces hold your team’s billing and environments. Every workspace starts with a Production environment, and you can add more, such as staging.
  • Subscribers are the people you email. They belong to an environment and are matched by email, externalId (your own ID) or their publicId.
  • Integrations connect an environment to an email provider (any SMTP server, or Cloudflare Email) and to event sources such as Stripe. See Integrations.
  • Workflows are a list of email or webhook steps with delays. Your app, your agent or a Stripe event triggers them for one subscriber, or you send them to everyone as a broadcast.