Sequenzy MCP Server

Sequenzy MCP Server

Official MCP server for Sequenzy, the AI-powered email marketing platform.

Connect Sequenzy to Claude Desktop, Claude Code, Codex, Cursor, Windsurf, VS Code Copilot, OpenClaw, and other MCP clients so your AI assistant can manage email operations with structured tools instead of hand-written API calls.

What You Can Do

• Manage subscribers, tags, lists, and dynamic segments.
• Draft, update, schedule, and inspect campaigns.
• Create and edit email sequences, including event-triggered and segment-entry automations.
• Manage transactional email templates and send single transactional emails.
• Generate email copy, subject lines, and multi-step sequences.
• Inspect analytics, subscriber activity, deliverability health, and dashboard URLs.
• Configure sender websites and pull integration examples for common frameworks.

Quick Setup

The easiest setup path is the Sequenzy wizard:

npx @sequenzy/setup

The wizard opens the browser login flow, creates a personal API key, detects supported AI clients, and configures them automatically when possible.

Manual Setup

All stdio MCP clients use the same command:

• Command: npx
• Args: -y @sequenzy/mcp
• Required env: SEQUENZY_API_KEY=seq_user_your_key_here

Optional environment variables:

• SEQUENZY_API_URL - Sequenzy API base URL. Defaults to https://api.sequenzy.com.
• SEQUENZY_APP_URL - Sequenzy dashboard base URL used by app URL helpers. Defaults to https://sequenzy.com.

Claude Desktop

Add this to your Claude Desktop config:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "sequenzy": {
      "command": "npx",
      "args": ["-y", "@sequenzy/mcp"],
      "env": {
        "SEQUENZY_API_KEY": "seq_user_your_key_here"
      }
    }
  }
}

Restart Claude Desktop after editing the config.

Claude Code

claude mcp add --scope user --env=SEQUENZY_API_KEY=seq_user_your_key_here sequenzy -- npx -y @sequenzy/mcp

On native Windows, wrap npx with cmd /c:

claude mcp add --scope user --env=SEQUENZY_API_KEY=seq_user_your_key_here sequenzy -- cmd /c npx -y @sequenzy/mcp

For a shared project config, use .mcp.json:

{
  "mcpServers": {
    "sequenzy": {
      "command": "npx",
      "args": ["-y", "@sequenzy/mcp"],
      "env": {
        "SEQUENZY_API_KEY": "seq_user_your_key_here"
      }
    }
  }
}

Codex

codex mcp add sequenzy --env SEQUENZY_API_KEY=seq_user_your_key_here -- npx -y @sequenzy/mcp
codex mcp list

Manual Codex config in ~/.codex/config.toml:

[mcp_servers.sequenzy]
command = "npx"
args = ["-y", "@sequenzy/mcp"]

[mcp_servers.sequenzy.env]
SEQUENZY_API_KEY = "seq_user_your_key_here"

Cursor

Add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "sequenzy": {
      "command": "npx",
      "args": ["-y", "@sequenzy/mcp"],
      "env": {
        "SEQUENZY_API_KEY": "seq_user_your_key_here"
      }
    }
  }
}

Windsurf

Use the same JSON shape as Cursor.

• macOS: ~/Library/Application Support/Windsurf/mcp.json
• Windows: %APPDATA%\Windsurf\mcp.json

VS Code Copilot

VS Code uses a servers object:

{
  "servers": {
    "sequenzy": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@sequenzy/mcp"],
      "env": {
        "SEQUENZY_API_KEY": "seq_user_your_key_here"
      }
    }
  }
}

Other MCP Clients

For OpenClaw, Hermes, and other MCP-compatible clients, point the client at npx -y @sequenzy/mcp and set SEQUENZY_API_KEY.

Getting an API Key

1. Open the Sequenzy dashboard.
2. Go to Settings -> API Keys.
3. Create a personal key.
4. Add the key to your MCP client config.

Personal keys start with seq_user_. You can revoke them any time in the dashboard.

Tools

This server currently exposes 59 MCP tools.

Account, Companies, Setup

Subscribers

Lists, Tags, Segments

Segment filters support attributes, events, saved segment membership, engagement events, and Stripe product purchase rules. Use filterJoinOperator: "or" for match-any segments, or pass a v2 root group for nested logic.

Each segment filter field validates its own operators:

• status, segment: is, is_not
• tag: contains, not_contains, is_empty, is_not_empty
• email: contains, not_contains
• emailProvider, list: is, is_not, is_empty, is_not_empty
• firstName, lastName: contains, not_contains, is_empty, is_not_empty
• added: less_than, more_than
• attribute: is, is_not, is_empty, is_not_empty, gte, lte, gt, lt, contains, not_contains
• event, email engagement fields: is, is_not, at_least, less_than_count
• emailBounced: also supports is_temporary_bounce, is_permanent_bounce
• stripeProduct: is, is_not, at_least, less_than_count
• stripeCurrentProduct, stripeTrialProduct: is, is_not, gte, lte, gt, lt

Stripe product filter examples:

{ "field": "stripeProduct", "operator": "is", "value": "prod_pro" }
{ "field": "stripeProduct", "operator": "is_not", "value": "prod_pro" }
{ "field": "stripeProduct", "operator": "at_least", "value": "prod_pro:3" }
{ "field": "stripeProduct", "operator": "less_than_count", "value": "prod_pro:3" }

Engagement fields such as emailSent, emailDelivered, emailOpened, emailClicked, emailBounced, and emailComplained accept rolling windows like 7d, 30d, 90d, 180d, all, threshold values like 5:30d, or a campaign scope like campaign:cmp_123.

Templates

A/B Tests

Use get_ab_test to discover variant IDs before editing. Variant updates accept either html or blocks, not both.

Campaigns

Sequences

Sequence creation supports:

• trigger: "segment_entered" plus segmentId for saved-segment entry automations.
• trigger: "event_received" plus {{event.*}} merge tags in subjects or body content.
• goal for AI-generated email content.
• Explicit steps with Sequenzy blocks.
• Explicit steps with HTML, which Sequenzy converts into editable blocks.
• Discount action steps that expose merge tags like {{discount.code}} and {{discount.percentOff}}.
• enrollmentMode: "matching_field" and enrollmentFieldPath for product-, variant-, order-, or subscription-specific event automations.

Run cancel_sequence_enrollments with dryRun: true before applying bulk cancellation.

Email Block Styling

Tools that accept blocks persist per-block visual styling under a block's styles object:

{
  "type": "card",
  "title": "Your update",
  "content": "Everything is ready.",
  "variant": "default",
  "styles": {
    "backgroundColor": "#f8fafc",
    "backgroundOpacity": 85,
    "borderColor": "#cbd5e1",
    "borderWidth": 1,
    "borderRadius": 12
  }
}

For compatibility with older agent prompts, top-level style keys such as backgroundColor, backgroundOpacity, borderColor, borderWidth, and borderRadius are also accepted and saved under styles.

Transactional Email

send_email variables support nested arrays for repeat blocks, such as { "event": { "items": [...] } }.

Analytics

AI Generation

Generated content is returned as draft content for review.

Resources

The server also exposes read-only MCP resources.

Example Prompts

Add john@example.com with tags "vip" and "developer", then put them on the beta list.

Create a 4-email churn prevention sequence for users whose subscription expires soon. Leave it in draft mode.

Create a segment for subscribers who bought Stripe product prod_pro at least 3 times.

Draft a campaign about our new analytics dashboard, target the Pro users segment, and send a test to me.

How did the last campaign perform compared with the one before it?

Security

• Use personal API keys, not shared team secrets.
• Keys only access companies your Sequenzy user can access.
• Revoke keys from Settings -> API Keys when access is no longer needed.
• Keep client approval prompts enabled for sends, scheduling, deletes, and bulk changes.
• Prefer draft workflows for campaigns and sequences, then review in Sequenzy before launch.

Troubleshooting

SEQUENZY_API_KEY environment variable is required

Set SEQUENZY_API_KEY in the MCP client config, or run:

npx @sequenzy/setup

Invalid API Key

Create a new personal key in Settings -> API Keys, update your MCP config, and restart the client.

Duplicate Resources

If a tool call would create a duplicate segment name or sending domain, the server returns a stable code, an agent-friendly description, a concrete resolution, and a docsUrl. For segments, call list_segments and reuse the existing segment ID or choose a different name. For websites, call list_websites; if the domain is not listed for the selected company, it belongs to another company or account and must be removed, reassigned, or replaced with a different sending domain.

Tools Do Not Appear

• Confirm npx is available in the environment the client uses.
• Restart the MCP client after editing config.
• Check that the config is in the correct client-specific location.

Network or API URL Issues

The server uses https://api.sequenzy.com by default. If you override it, verify SEQUENZY_API_URL points at a reachable Sequenzy API base URL.

Development

bun install
bun test
bun run type-check
bun run build

MCP tool schemas must remain compatible with strict clients:

• Tool inputSchema roots must be plain type: "object" schemas.
• Do not publish anyOf anywhere in tool schemas.
• Do not put oneOf, allOf, enum, or not at the root of a tool schema.
• Enforce conditional requirements in handlers and cover them with tests.

This standalone repository mirrors the MCP package maintained in the main Sequenzy monorepo. See AGENTS.md for sync rules.

License

MIT