Sequenzy
AI-agent email marketing automation for subscribers, campaigns, sequences, transactional email, landing pages, inbox replies, webhooks, analytics, and…
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only
What it can do
- Get Account: Get current account information including available companies. IMPORTANT: If you have access to multiple companies, you MUST either: 1. Call select_company first to choose which company t
- Select Company: Select which company to operate on (for user-scoped API keys with access to multiple companies). Use get_account to see available companies. After selecting, all subsequent operations
- Get App Urls: Generate Sequenzy dashboard URLs for known resource IDs. Use this when the user asks where to review or edit a generated sequence, campaign, template, or company settings. If companyId i
What data it sees
Do you need an account
No: the server works without sign-in
AI-agent email marketing automation for subscribers, campaigns, sequences, transactional email, landing pages, inbox replies, webhooks, analytics, and deliverability.
Server tool list (60)
Raw names from tools/list. Only developers need these.
| get_account | Get current account information including available companies. IMPORTANT: If you have access to multiple companies, you MUST either: 1. Call select_company first to choose which company to work with, OR 2. Pass companyId explicitly in each tool call The response shows 'companies' (all available) and 'selectedCompanyId' (currently active). All subsequent operations will use the selected company unless you pass a companyId override. |
| select_company | Select which company to operate on (for user-scoped API keys with access to multiple companies). Use get_account to see available companies. After selecting, all subsequent operations will use this company unless you pass a companyId override. |
| get_app_urls | Generate Sequenzy dashboard URLs for known resource IDs. Use this when the user asks where to review or edit a generated sequence, campaign, template, or company settings. If companyId is omitted, the selected/current company is used when available. |
| create_company | Create a new company/brand. This will parse your website to extract brand information. The tool polls every 20 seconds until the company is fully processed (typically 30-60 seconds). |
| get_company | Get company details, processing status, and effective email localization settings |
| create_api_key | Create a new API key for a company. Use this when setting up Sequenzy integration in a project. The returned key should be saved to the project's .env file as SEQUENZY_API_KEY. The key can only be retrieved once at creation time. |
| list_websites | List all configured sender websites/domains |
| add_website | Add a new sender website. Takes ~30 seconds to process. |
| check_website | Check if a website has been processed and is ready to use |
| get_integration_guide | Get code examples for integrating Sequenzy into your project. CRITICAL - FOR SAAS/SUBSCRIPTION APPS: If the app uses Stripe, Polar, Paddle, Dodo, or Creem - tell the user to connect it in Sequenzy dashboard (Settings → Integrations). The native integration automatically handles all payment events and customer tags - no code needed! CRITICAL - FOR E-COMMERCE STORES: If the store runs on Shopify or WooCommerce - tell the user to connect the native integration in the dashboard instead (it syncs products, orders, and customers automatically). For any other e-commerce stack (custom checkouts, CheckoutChamp, Sticky.io, headless storefronts), use the 'ecommerce' use case to integrate via the Commerce API. Only provide manual event tracking code if the user explicitly asks for it. Use cases: - 'transactional': Sending one-off emails (welcome, password reset, receipts) - 'subscribe_form': Adding subscribers from signup forms - 'event_tracking': Tracking CUSTOM events only (not payment events - those come from the integration) - 'ecommerce': Connecting a custom e-commerce platform via the Commerce API (sync products, push orders/checkouts, power abandoned cart + back-in-stock automations) Before implementing, use create_api_key to generate an API key and save it to .env as SEQUENZY_API_KEY. |
| add_subscriber | Add a new subscriber to your list |
| update_subscriber | Update an existing subscriber's attributes or tags |
| remove_subscriber | Unsubscribe or delete a subscriber |
| get_subscriber | Get the full subscriber profile, including tags, list memberships, sequence enrollments, email stats, and recent activity |
| search_subscribers | Search subscribers by free-text query, tags, list, or segment. If you omit limit, the tool fetches all pages and returns every match. |
| list_products | List synced products (Stripe, Shopify, WooCommerce) including any attached digital delivery file. Useful before attaching a file or building a purchase sequence for a specific product. |
| upsert_products | Create or update products in the catalog (Commerce API, keyed by your productId, stored under the api provider). Use this to add products that are not synced from Stripe/Shopify/WooCommerce, then attach a deliverable file with attach_product_file and build a purchase sequence for them. |
| delete_product | Delete a product previously pushed via upsert_products (Commerce API products only), identified by your productId. |
| attach_product_file | Attach a distributable file to a product, either by public URL or by uploading a local file (filePath, local MCP server only). After a purchase of the product, sequence emails can link to it with {{event.download.url}} and {{event.download.name}}. |
| remove_product_file | Remove the attached distributable file from a product. |
| sync_products | Queue a sync of the Stripe product catalog into the products list. Requires an active Stripe integration. |
| list_tags | List all tags in the account |
| create_tag | Create a new tag definition. The name is normalized to lowercase with hyphens (e.g. 'VIP Customer' becomes 'vip-customer'). Color defaults to gray. |
| update_tag | Update a tag's color. System tags cannot be updated. |
| delete_tag | Permanently delete a tag and remove it from all subscribers. This cannot be undone. System tags and tags used by sequences cannot be deleted. |
| list_lists | List all subscriber lists |
| create_list | Create a new subscriber list |
| update_list | Update a subscriber list's name, description, or privacy. Only the provided fields are changed. |
| delete_list | Permanently delete a subscriber list and remove all of its memberships. Subscribers themselves are kept. This cannot be undone. |
| add_subscribers_to_list | Bulk add existing or new subscribers to a subscriber list from an email array. Existing subscribers are added to the list without requiring a per-subscriber update call. |
| remove_subscribers_from_list | Remove subscribers from a list by email address. Maximum 500 emails per call. Subscribers stay in the account; only the list membership is removed. Returns the removed count plus a notFound array of emails that did not match a subscriber. |
| list_segments | List all segments |
| create_segment | Create a new segment from explicit filter rules. Use `filters` plus `filterJoinOperator` for flat legacy rules, or `root` for nested AND/OR groups such as `{ "kind": "group", "joinOperator": "and", "children": [{ "kind": "filter", "field": "attribute", "operator": "gte", "value": "mrr:50" }, { "kind": "group", "joinOperator": "or", "children": [{ "kind": "filter", "field": "tag", "operator": "contains", "value": "vip" }, { "kind": "filter", "field": "event", "operator": "is_not", "value": "saas.purchase:30d" }] }] }`. Supports `event` and `segment` fields, Stripe product purchase/current/trial/date filters, and campaign-specific engagement filters. |
| update_segment | Update a segment's name and/or filter rules. Use the same `filters` plus `filterJoinOperator` or nested `root` shapes as create_segment; providing `filters` or `root` replaces the segment's existing rules. |
| delete_segment | Permanently delete a segment. This cannot be undone. Subscribers are not affected. |
| get_segment_count | Get the number of subscribers in a segment |
| list_audience_syncs | List Meta custom audience syncs (segment -> ad audience mappings) with their schedule and last sync status. Requires the Meta Ads integration to be connected in the dashboard. |
| list_ad_accounts | List the Meta ad accounts available through the connected Meta Ads integration. Use the returned account id as `adAccountId` when creating an audience sync. |
| create_audience_sync | Push a segment to a Meta custom audience and keep it synced on a schedule. Provide `segmentId` for an existing segment OR `predefinedSegmentId` for a ready-made template (for example "zero-ltv", "no-purchase-1y", "recent-buyers", "high-spenders-ecom", "non-buyers", "engaged") - the template segment is created automatically on first use. The first upload runs immediately. Note: audiences are add-only; subscribers who later leave the segment stay in the Meta audience. |
| update_audience_sync | Update an audience sync's frequency or pause/resume it (`isActive`). |
| delete_audience_sync | Remove an audience sync mapping. The Meta audience itself is kept (running ads are not disrupted) - only future syncs stop. |
| sync_audience_now | Trigger an immediate upload of the segment's subscribers to its Meta custom audience, outside the regular schedule. |
| list_templates | List all email templates, including per-locale localization sync status |
| get_template | Get a template's details, content, and all localized variants with sync status |
| create_template | Create a new email template |
| update_template | Update an existing template. At least one of `name`, `subject`, `html`, `blocks`, or `labels` is required, and only those update fields are accepted. |
| delete_template | Delete a template |
| list_ab_tests | List A/B tests and their variants |
| get_ab_test | Get A/B test details, variants, and per-locale localization sync status |
| get_ab_test_stats | Get A/B test aggregate stats and per-variant stats. Supports period or custom start/end ranges. |
| restart_ab_test | Run another sequence A/B test after a winner is selected. By default the winner becomes the new control; pass sourceVariantId to use another variant as the control email. |
| update_ab_test_variant | Update a draft A/B test variant. Provide at least one of subject, previewText, html, or blocks. Use either html or blocks, not both. |
| create_ab_test | Create a campaign A/B test. Control variant A is created automatically from the campaign's current email; optionally provide extra variants. The campaign must be in draft or rejected status, and each campaign can only have one A/B test. |
| add_ab_test_variant | Add a variant to a draft campaign A/B test. Variants cannot be added after the test has started. |
| delete_ab_test_variant | Permanently delete a variant from a draft campaign A/B test. This cannot be undone. Variant A is the control and cannot be deleted, and the test must keep at least the minimum number of variants. Variants cannot be removed after the test has started. |
| delete_ab_test | Permanently delete a campaign A/B test and all of its variants. This cannot be undone. Running tests (testing or winner_selected) cannot be deleted, and the linked campaign must be in draft or rejected status. |
| list_campaigns | List all campaigns |
| get_campaign | Get campaign details and stats |
| get_email_send | Get a sent email by emailSendId, including the stored HTML body when available and the ClickHouse event timeline. If the short-lived email send row has been cleaned up, returns the retained ClickHouse events and a sparse summary. |
| create_campaign | Create a new campaign (as draft) |