Back to MCP Servers

Sequenzy Mcp

Email marketing automation MCP server for Sequenzy. Manage subscribers, lists, segments, templates, campaigns, sequences, transactional emails, analytics, and AI-generated email content. Install: `npx -y @sequenzy/mcp`.

communicationautomationai
By Sequenzy
1Updated 2 days agoTypeScript

Installation

npx -y @sequenzy/mcp

Configuration

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": ["-y", "mcp"]
    }
  }
}

How to use

  1. Run the installation command above (if needed)
  2. Open your Claude Code settings file (~/.claude/settings.json)
  3. Add the configuration to the mcpServers section
  4. Restart Claude Code to apply changes

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.
  • Sync segments to Meta custom audiences for Facebook and Instagram retargeting.
  • Manage products and attach digital delivery files for purchase automations.
  • Draft, update, schedule, and inspect campaigns.
  • Create and edit email sequences, including event-triggered and segment-entry automations.
  • Cancel, pause, resume, duplicate, or delete campaigns and enroll contacts into sequences.
  • Manage transactional email templates and send single transactional emails.
  • Create, edit, publish, unpublish, and delete landing pages.
  • Connect and verify custom domains for published landing pages.
  • Manage team invitations, inbox conversations, and outbound webhook endpoints.
  • Generate email copy, subject lines, and multi-step sequences.
  • Inspect analytics, subscriber activity, deliverability health, and dashboard URLs.
  • Configure company product info, sender websites, and integration examples for common frameworks.

Every published MCP tool includes explicit readOnlyHint, destructiveHint, and openWorldHint annotations so compatible clients can display accurate tool-use affordances. Tools also publish outputSchema definitions and return structuredContent, giving clients and models machine-readable result shapes for follow-up calls.

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.

Hosted Remote MCP

For clients that support Streamable HTTP MCP, use Sequenzy's hosted endpoint instead of running a local stdio process:

https://api.sequenzy.com/v1/mcp

Remote clients should authenticate with the Sequenzy OAuth flow when supported. Local and automation clients can still use the stdio package below with SEQUENZY_API_KEY.

Machine-readable discovery files:

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 120 MCP tools.

Account, Companies, Setup

ToolDescription
get_accountGet account info, available companies, and the current company.
select_companySet the active company for future tool calls.
get_app_urlsBuild dashboard URLs for campaigns, landing pages, sequences, emails, settings, domains, and sent email details.
create_companyCreate a new company or brand.
get_companyRead company details, product info, brand colors, AI writing context, and localization settings.
update_companyEdit product info and brand context AI uses for generated emails.
create_api_keyCreate an API key for a company.
list_websitesList configured sender websites and domains.
add_websiteAdd a sender website. Processing can take around 30 seconds.
check_websiteCheck whether a website is processed and ready.
get_integration_guideGet framework-specific integration examples.

Subscribers

ToolDescription
add_subscriberAdd a subscriber with attributes, tags, status, opt-in mode, and optional list IDs.
update_subscriberUpdate attributes, add tags, or remove tags.
remove_subscriberUnsubscribe a subscriber or hard-delete them.
get_subscriberFetch subscriber details by email or external ID.
search_subscribersSearch by query, tags, list, status, segment, or pagination.

Products & Digital Delivery

ToolDescription
list_productsList synced products from Stripe, Shopify, WooCommerce, manual, or Commerce API data.
upsert_productsCreate or update up to 100 Commerce API products keyed by your product ID.
delete_productDelete a product previously pushed through the Commerce API.
attach_product_fileAttach a hosted or locally uploaded delivery file to a product.
remove_product_fileRemove an attached product delivery file.
sync_productsQueue a Stripe product catalog sync.

After a product delivery file is attached, matching purchase events include download.url and download.name, so purchase-triggered emails can use merge tags like {{event.download.url}}.

Lists, Tags, Segments

ToolDescription
list_tagsList all tags.
create_tagCreate a tag definition with an optional color.
update_tagUpdate a tag color.
delete_tagDelete a tag and remove it from subscribers.
list_listsList subscriber lists.
create_listCreate a subscriber list.
update_listRename or describe a subscriber list.
delete_listDelete a subscriber list.
add_subscribers_to_listAdd up to 500 subscribers to a list from an email array.
remove_subscribers_from_listRemove up to 500 subscribers from a list.
list_segmentsList saved segments and counts.
create_segmentCreate saved segments from filters or nested AND/OR groups.
update_segmentUpdate segment name, filters, root group, or join operator.
delete_segmentDelete a saved segment.
get_segment_countPreview the active subscriber count for a segment.

For subscriber exports, search_subscribers accepts listId, exact listName, or list (ID first, then exact name). If limit is omitted, the tool fetches all matching subscribers using 100-row API pages.

For bulk list population, use add_subscribers_to_list; the backing API endpoint is POST /api/v1/lists/{listId}/subscribers with no /bulk suffix:

{
  "emails": ["ada@example.com", "grace@example.com"],
  "duplicateStrategy": "skip",
  "enrollInSequences": false,
  "optInMode": "default"
}

Send at most 500 emails per request. Standard API rate limits still apply: 100 requests per minute per API key and 20 requests per second burst. For CSV-driven CLI imports, accepted email headers include email, e-mail, email address, and mail; if no recognized header exists, the CLI reads the first column.

Segment filters support attributes, events, saved segment membership, engagement events, Stripe product purchase rules, and commerce product purchase rules. Us

View source on GitHub