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.

Interactive email and sequence previews

In clients that support MCP Apps, including compatible ChatGPT and Claude connections, you can review your saved emails and sequences directly in the conversation.

• render_email opens the rendered email with Desktop (640px) and Mobile (375px) views, its subject, preview text and personalization warnings. Pass a campaign ID, template ID, or sequence ID plus node ID using the existing tool inputs. It renders your saved content through Sequenzy's email renderer. Personalization and locale options remain available through the same tool.
• preview_sequence({ companyId, sequenceId }) opens the saved sequence as a connected diagram with triggers, delays, branches and actions. Select an email to render it, switch between available A/B variants, or use the Emails tab to browse the sequence's emails. Random splits show their configured allocation. Refresh reloads saved content, and failed requests offer an explicit retry.
• list_sequence_email_variations, generate_sequence_email_variations, list_campaign_variations and generate_campaign_variations open the design variations side by side, each rendered as it would send. While some are still generating, the view updates every few seconds for up to five minutes; after a generate call it follows only the new ones. Use for Email 1 and Use for every email (campaigns: Use this design) ask for confirmation, then save through use_sequence_email_variation or use_campaign_variation with your existing permissions and tell your assistant what changed. Nothing changes until you confirm.

Supporting workflows use compact cards in the same Sequenzy style:

• open_image_upload({ companyId }) opens an image picker. Choose a PNG, JPEG, GIF or WebP up to 10 MB, optionally describe it, then select Upload image. Opening the widget does not write anything. Submission uses upload_image_asset with your existing permissions and returns the saved asset to your assistant. After an uncertain failure, check your image library before retrying; uploads are never automatically retried.
• monitor_subscriber_import({ companyId, importId }) shows counts and progress for an existing import. It polls get_subscriber_import every five seconds while running, for up to five minutes. Completion, blocked status, errors or leaving the view stop polling. Refresh status restarts monitoring. This does not start or retry imports.

Both widgets pin the company explicitly. Clients without MCP Apps can use upload_image_asset and get_subscriber_import directly; the same operations are available through the existing REST API and CLI.

The sequence preview requires an explicit company ID from get_account and keeps every email render pinned to that company. Previews never activate sequences, enroll subscribers or send email. A/B previews require the existing access to variant content; unavailable variants are shown as unavailable instead of being replaced with the control email.

Email content is isolated from the widget. Scripts, forms, nested frames and link navigation are disabled; external stylesheets and fonts are not loaded. HTTPS email images may load from their original hosts, subject to the client's policy. The widget itself bundles its logo and font and uses authenticated MCP tool calls without exposing credentials. Actual email-client rendering can differ, so use test sends for final inbox verification.

Clients without MCP Apps still receive the existing rendered HTML or sequence data. The same workflows are available through the existing public render and sequence-read endpoints and CLI render/sequence commands. No new REST endpoint or CLI command is needed for this presentation layer.

What You Can Do

Use create_campaign_for_audience for a frozen group of selected contacts or all contacts matching contact/activity filters. It creates a blank draft, reports selected and currently eligible counts, and preserves existing campaign read/update/clear/schedule workflows. The limit is 100,000 contacts and 8 MiB; drafting sends no email.

• Manage subscribers, tags, lists, and dynamic segments, including bulk tag reconciliation and synthetic event testing.
• Sync segments to Meta custom audiences for Facebook and Instagram retargeting.
• Sync contacts and events from Snowflake, BigQuery, Redshift or Postgres on a schedule.
• Stream email events, custom events and subscriber snapshots to your S3 or GCS bucket for your data warehouse.
• Manage products and attach digital delivery files for purchase automations.
• Upload hosted email images with alt text and reusable responsive crop settings.
• Draft, update, schedule, and inspect campaigns, including resolved audience previews, persisted conversion goals, and From, Reply-To, CC, and BCC identities.
• Render campaigns, sequence steps, and templates to their exact email-safe HTML without sending.
• Add one-click Poll and NPS survey blocks to emails and inspect campaign response summaries.
• Create and edit email sequences, including multi-list/tag triggers, entry-audience and property-filtered stop conditions, sending identity overrides, existing graph restructuring, and direct step test sends to internal reviewers.
• Cancel, pause, resume, duplicate, or delete campaigns and enroll contacts into sequences.
• Manage transactional email templates and send transactional emails to shared To, Cc, and Bcc recipient lists.
• Supply localized template variants or queue AI translation for enabled locales.
• Create, preview, edit, publish, unpublish, and delete landing pages.
• Create list-scoped saved signup forms with responsive stack, row, grid, and single-image overlay block groups (including foreground gap controls), then return client-safe static-site embeds.
• Create, target, publish, duplicate, and deploy saved signup popups with the same recursive block layouts.
• Connect and verify custom domains for published landing pages.
• Manage team invitations, the inbox (its address, conversations, replies, forwards), and outbound webhook endpoints.
• Manage geofences (places the mobile SDKs watch) and bulk-import them by external ID. Visits become app.geofence_* events for sequence triggers and geofence segment filters.
• Generate email copy, subject lines, and multi-step sequences.
• Inspect analytics, subscriber activity, deliverability health, company-level sending pauses, integrations, published event payload schemas, sending identities, tracking settings, and dashboard URLs.
• Inspect whether "Sent with Sequenzy" is visible for a workspace, why the owner subscription does or does not remove it, and open the canonical subscription page for an upgrade or renewal. Entitlement changes apply to future sends from existing live sequences without editing their blocks.
• Diagnose why sending is paused and restore eligible hard-bounce pauses after confirming list cleanup.
• Inspect exact-recipient bounce, complaint, and email-hygiene suppression, and clean up eligible stale bounces without exposing the shared SES suppression list.
• Configure company product info, account-wide sending identity defaults, rename individual sender and reply-to profiles, manage sender domains, and inspect integration examples for common frameworks.

Every published MCP tool includes explicit readOnlyHint, destructiveHint, idempotentHint, and openWorldHint annotations so compatible clients can display accurate tool-use affordances. Any write that overwrites, cancels, deletes, changes a live sequence, or can send email or SMS is marked destructive; tools that can email real contacts, publish a public link, or reach a third-party service are marked open-world. Tools also publish outputSchema definitions (except on the OpenAI-reviewed route) and return structuredContent, giving clients and models machine-readable result shapes for follow-up calls.

Tool results and recovery

Tool failures retain isError: true and readable error text, and also return structuredContent with { success: false, error: { code, message, howToFix, docsUrl } }. HTTP errors include statusCode; a valid API Retry-After header adds retryAfterSeconds. These fields are omitted when unavailable. The OpenAI profile uses safe recovery descriptions and known codes or status-derived fallbacks, omitting raw backend diagnostics.

Use the error code and recovery guidance to choose your next step. The client retries a read (GET) up to 3 times within about 3 seconds after a 502, 503, 504 or network error, waiting out a Retry-After of 5 seconds or less, and never retries a write. After an uncertain send_email outcome, reuse the original idempotencyKey with unchanged input and inspect emailSendId when available. A retry hint alone does not mean repeating a write is safe.

Segment counts and segment-filtered reads fail with SEGMENT_REFERENCE_DEPTH_EXCEEDED or SEGMENT_REFERENCE_COUNT_EXCEEDED when segments reference other segments too deeply or too many times. Retrying does not help; reduce the nesting or the number of references with update_segment first.

Successful results keep their existing shapes. Recoverable partial subscriber event imports retain their counts and row failures without isError; inspect those rows before retrying failed records.

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

The Sequenzy plugin in the ChatGPT plugin directory uses the reviewed hosted surface, which ChatGPT custom connectors can also add directly:

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

That surface shares the same implementation and keeps the standard tool set except for operations that accept or manage credentials, or return unprojected payloads: connect_integration, create_api_key, list_api_keys, update_api_key, revoke_api_key, delete_api_key, request_api_key_handoff, create_data_export, update_data_export, create_warehouse_connection, update_warehouse_connection, preview_warehouse_query, create_webhook, the geofence tools (list_geofences, get_geofence, create_geofence, update_geofence, delete_geofence, import_geofences; they carry place coordinates), list_webhook_deliveries, list_capture_submissions, replay_webhook_delivery, and rotate_sequence_inbound_webhook_secret. It also omits add_website, a compatibility alias of add_sending_domain, and submit_feedback. API keys, including the one behind the ChatGPT connection, are managed in the dashboard. The surface also omits subscription and upgrade links: subscriptionUrl fields, the get_app_urls subscription URL, and the emailBranding tier and upgrade action are removed, and get_app_urls rejects the billing and subscription settings tab aliases. The surface also omits the push credential tools set_apns_credentials and set_fcm_credentials, which take customer private keys as input, and register_push_device, an app-backend call whose required device token the surface's credential policy rejects.

Four tools use clearer names on this surface; standard MCP and the stdio package keep the original names:

| Standard MCP