# Sequenzy/mcp [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/Sequenzy/mcp  
**GitHub Stars:** 2  
**npm Downloads (last month):** 7120  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/sequenzy-mcp

## Description
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.

## Tools
Capabilities this server exposes over MCP:

- **get_account** — Get account info, available companies, current key permissions, and the API Keys management URL.
- **select_company** — Set the active company for future tool calls.
- **get_app_urls** — Build dashboard URLs for campaigns, landing pages, sequences, emails, settings, subscription management, domains, and sent email details. `settingsTab: "billing"` resolves to Account -> Subscription.
- **create_company** — Create a new company or brand.
- **get_company** — Read company details, product info, brand context, localization, reply-tracking settings, current From/Reply-To defaults, and the effective read-only `emailBranding` entitlement with plan/status reason and subscription URL; STO is explicitly identified as campaign-only.
- **update_company** — Edit product info, brand context, email theme, reply tracking, and account-wide From/Reply-To profile defaults or names.
- **get_sync_rules** — Read the company's event-to-tag rules and whether it uses the inherited platform preset.
- **update_sync_rules** — Replace all sync rules; pass `[]` to disable them or `null` to opt into the SaaS/ecommerce platform preset.
- **get_shopify_automation_settings** — Read browse-abandonment, cart-abandonment, and price-drop settings for the connected Shopify store.
- **update_shopify_automation_settings** — Partially update Shopify automation settings or reset an individual section to its platform defaults.
- **create_api_key** — Create a company API key and return its one-time secret on standard MCP; omitted from the OpenAI-reviewed route.
- **request_api_key_handoff** — Prepare an owner-reviewed create/rotation URL when the active key cannot manage API keys itself.
- **list_api_keys** — List company API keys as non-secret metadata for safe identification and cleanup.
- **update_api_key** — Rename a company API key or replace its permission preset or scopes without changing the key value.
- **revoke_api_key** — Permanently revoke an exact company API key by ID after checking it with `list_api_keys`.
- **delete_api_key** — Compatibility alias for `revoke_api_key`.
- **list_websites** — List sending domains with stored aggregate, SPF, DKIM, and MAIL FROM status.
- **add_sending_domain** — Add a sending domain and return its cohort-specific DNS setup records.
- **add_website** — Compatibility alias for `add_sending_domain`.
- **check_website** — Read a sending domain's stored SPF, DKIM, MAIL FROM, and aggregate verification details.
- **verify_sending_domain** — Run a fresh sending-domain DNS/provider verification and return current status and diagnostics.
- **list_integrations** — List connected integrations with connection and sync health, without returning credentials.
- **get_sending_status** — Diagnose active, paused, or suspended sending, including enforcement denominators, review gates, and remediation steps.
- **resume_sending** — Restore an eligible hard-bounce pause after explicitly confirming the list has been sanitized.
- **get_tracking_settings** — Read account-wide and Transactional API open/click defaults, unsubscribe, attribution, UTM, click-domain, reply-tracking, and double-opt-in settings.
- **update_tracking_settings** — Update account-wide and Transactional API tracking defaults, attribution, UTM, and account-wide double opt-in.
- **get_integration_guide** — Get framework-specific integration examples.
- **get_integration** — Inspect one connected integration, its event wiring, list targeting, recent activity, and recommendations.
- **list_integration_capabilities** — Compare provider capabilities whether or not they are connected.
- **connect_integration** — Connect supported API-key or webhook-secret providers on standard MCP, including managed Lemon Squeezy webhooks, outbound-only Attio, and optional PostHog/Segment history import; omitted from the OpenAI-reviewed route.
- **get_event_schema** — Inspect published event payload examples, property paths, types, and merge tags by provider.
- **list_integration_activity** — Read the retained integration-specific webhook and sync activity log.
- **set_integration_sync_enabled** — Enable or disable bulk imports and backfills while leaving live webhooks connected.
- **set_integration_list_targeting** — Choose which lists contacts created by a supported integration join on future provider writes.
- **sync_integration** — Queue payment revenue, Supabase users, or a PostHog/Segment event-history import using the saved integration configuration.
- **get_integration_pixel** — Read Shopify's live pixel/configuration state and distinguish confirmed dark events from an unknown read.
- **activate_integration_pixel** — Install or repoint Shopify's storefront pixel; idempotent when it is already current.
- **list_web_tracking_keys** — List publishable website-tracking keys, origin restrictions, usage state, and install snippets.
- **get_web_tracking_key** — Get one website-tracking key with its exact install snippet and ingest endpoint.
- **create_web_tracking_key** — Create a publishable tracking key for a non-Shopify storefront or website.
- **update_web_tracking_key** — Rename, restrict, revoke, or re-enable a website-tracking key.
- **delete_web_tracking_key** — Permanently delete a website-tracking key after its snippet has been removed.
- **list_sender_profiles** — List sender and reply-to profiles, defaults, and sending-domain readiness.
- **update_sender_profile** — Rename one sender or reply-to profile without changing the account defaults.
- **delete_sender_profile** — Permanently delete an unused sender profile, with guards for live sending surfaces and the last remaining sender.
- **get_notification_preferences** — Read the current user's per-company account notification settings and supported modes, including the Monday weekly report.
- **update_notification_preferences** — Update the current user's account notification delivery modes, including weekly-report opt-out, without affecting teammates.
- **render_email** — Render final email-safe HTML and diagnose unresolved merge tags, including typos hidden by defaults. The OpenAI-reviewed route accepts sample data or a policy-checked inline subscriber, not a stored subscriber ID.
- **add_subscriber** — Add one subscriber; status is creation-only, so use `update_subscriber` for an existing contact.
- **create_subscriber_import** — Queue up to 5,000 full CRM records with an optional retry-safe `idempotencyKey`; enabled email-hygiene checks continue separately after ingestion.
- **get_subscriber_import** — Read progress, row outcome counts, and failure summaries for a queued import.
- **update_subscriber** — Update native profile and phone fields, SMS consent, attributes, tags, or global status.
- **remove_subscriber** — Unsubscribe while preserving suppression history, or permanently delete only with `hardDelete: true`.
- **get_subscriber** — Fetch subscriber details by email or external ID.
- **search_subscribers** — Search by query, tags, list, status, segment, or one custom attribute, with automatic or resumable pagination.
- **trigger_subscriber_event** — Emit one custom event exactly as an integration would, applying sync rules and matching sequence triggers.
- **trigger_subscriber_events** — Emit several ordered custom events for one subscriber.
- **import_subscriber_events** — Import up to 25 source-identified events across contacts; silent history requires every row for a contact to be over an hour old.
- **bulk_add_subscriber_tags** — Add tags to up to 500 existing subscribers; requires `subscribers:tag` and may also require `tags:write`.
- **bulk_remove_subscriber_tags** — Remove tags from up to 500 existing subscribers; requires `subscribers:tag` or `subscribers:write`.
- **list_products** — List synced products from Stripe, Shopify, WooCommerce, manual, or Commerce API data.
- **upsert_products** — Create or update up to 100 Commerce API products keyed by your product ID.
- **delete_product** — Delete a product previously pushed through the Commerce API.
- **attach_product_file** — Attach a hosted or locally uploaded delivery file to a product.
- **remove_product_file** — Remove an attached product delivery file.
- **sync_products** — Queue a Stripe product catalog sync, optionally selecting an integration by ID.
- **upload_image_asset** — Upload an email image and return its hosted media record plus a ready-to-insert image block.
- **list_tags** — List all tags.
- **create_tag** — Create a tag definition with an optional color.
- **update_tag** — Update a tag color.
- **delete_tag** — Delete a tag and remove it from subscribers.
- **list_lists** — List subscriber lists.
- **create_list** — Create a subscriber list.
- **update_list** — Rename or describe a subscriber list.
- **delete_list** — Delete a subscriber list.
- **add_subscribers_to_list** — Add up to 500 subscribers to a list from an email array.
- **remove_subscribers_from_list** — Remove up to 500 subscribers from a list.
- **list_segments** — List saved segments and counts.
- **create_segment** — Create nested or same-element array-filtered segments.
- **update_segment** — Update segment name, filters, root group, or join operator.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

**Requires environment variables:** `SEQUENZY_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Sequenzy/mcp MCP server does

Sequenzy/mcp MCP server exposes Sequenzy's email marketing platform as structured MCP tools. It covers both operational work and account administration: an agent can select a company, inspect account permissions, manage company and brand settings, configure sending identities, and generate dashboard URLs for common resources.

Email workflows include subscribers, tags, lists, dynamic segments, campaigns, sequences, transactional templates, landing pages, signup forms, popups, and analytics. The material also supports AI-generated email copy, subject lines, translations, and multi-step sequence drafts. Campaigns and sequence content can be rendered to email-safe HTML for inspection before sending.

The server also handles delivery foundations. It can add and verify sending domains, inspect SPF, DKIM, MAIL FROM, and aggregate status, diagnose paused or suspended sending, and resume an eligible hard-bounce pause after list cleanup has been confirmed. Tracking, attribution, UTM settings, unsubscribe behavior, double opt-in, integrations, and Shopify automation settings are available through dedicated operations.

## How it works

For local clients, the package runs as an stdio MCP process launched with `npx -y @sequenzy/mcp`. The client sends tool calls, and the server communicates with Sequenzy using the configured API key. Company selection matters for subsequent calls, so workflows can first identify or select the active company before changing company-scoped resources.

Sequenzy also provides a hosted Streamable HTTP endpoint at `https://api.sequenzy.com/v1/mcp`. Supported remote clients can use OAuth when available. The OpenAI-reviewed endpoint uses a reduced surface: several credential- or webhook-related operations are excluded there, including integration connection and API-key creation.

Tools publish read-only, destructive, and open-world annotations, along with output schemas and structured content. This gives compatible clients information about the expected risk and result shape of each operation.

## Setup and configuration

The basic local requirement is the `SEQUENZY_API_KEY` environment variable. The package can be added to an MCP client's server configuration with `npx` as the command and `-y @sequenzy/mcp` as its argument. The optional `SEQUENZY_API_URL` variable changes the API base URL, while `SEQUENZY_APP_URL` changes the dashboard base URL used by application URL helpers.

An alternative setup path is Sequenzy's `npx @sequenzy/setup` wizard. The README names Claude Desktop, Claude Code, Codex, Cursor, Windsurf, and VS Code Copilot as supported client examples.

## Tools and capabilities

The available operations include:

- Read and update company context, email branding, sending defaults, tracking settings, synchronization rules, and Shopify automation settings.
- Create, inspect, rename, update, list, and revoke company API keys, subject to the permissions of the active key and the route being used.
- Add, inspect, and verify sending domains, then review deliverability and sending-status diagnostics.
- Inspect integrations, compare provider capabilities, connect supported providers, and retrieve framework-specific integration guidance.
- Build application links for campaigns, landing pages, sequences, emails, settings, subscriptions, domains, and sent-message details.
- Manage campaigns, sequences, transactional email templates, landing pages, signup forms, popups, audiences, and analytics through the broader Sequenzy tool set described in the README.

## Limitations and notes

The active company and API-key or OAuth scopes determine what a client can access. Some operations are deliberately unavailable on the OpenAI-reviewed route, and standard MCP may return secrets for operations such as API-key creation or credential-based integration setup. The README advises using the dashboard or local CLI when secrets should not enter an AI conversation.

Sequenzy/mcp MCP server can process workspace, subscriber, campaign, engagement, commerce, delivery, and integration data depending on the requested tool. The provided privacy guidance prohibits submitting payment-card data, health information, government identifiers, credentials, precise geolocation, and other restricted data in open-ended fields. Sending recovery also has a condition: a hard-bounce pause must be explicitly confirmed as cleaned before it can be resumed.

_Full upstream README: https://allmcps.com/mcp/sequenzy-mcp/readme_