Connect AI Assistants (MCP)

Add this remote MCP server URL to your AI assistant’s custom connector settings, then sign in to Sequenzy when it asks:

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

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

There is no API key to copy. Step-by-step instructions for each assistant are below. Sequenzy’s Model Context Protocol (MCP) server lets your AI assistant work in your Sequenzy workspace. Ask it to build a trial onboarding sequence, draft a launch campaign, tag your paying customers or explain last week’s open rates, and it uses Sequenzy’s tools to do the work.

Pick your setup

Find your assistant below and follow that section. Most people are connected in under five minutes.

You use	How it connects	What you need
ChatGPT	Remote connector	Sign in to Sequenzy when prompted
Claude (web, desktop, mobile)	Remote connector	Sign in to Sequenzy when prompted
Claude Code, Codex, Cursor, Windsurf, VS Code	Local server, installed by a setup wizard	Node.js, so `npx` works
Any other MCP client	Remote URL or local command	OAuth support or an API key

Remote connectors run on Sequenzy’s servers. You paste one URL into your assistant and approve access in the browser; there is no API key to copy. Local servers run on your computer through npx, using a personal API key that the setup wizard creates for you.

Sequenzy AI Agent Setup with callouts showing agent selection and connection instructions

The dashboard walks you through the same steps. Click AI Agent Setup at the bottom of the dashboard sidebar, choose your assistant, and copy the URL or command it shows. For local clients it can also create a key and fill it into the config for you.

ChatGPT

Turn on developer mode

In ChatGPT, open Settings → Connectors → Advanced settings and enable Developer mode. Custom connectors need a ChatGPT plan with connector support. ChatGPT sometimes renames these menus; look for custom connectors or apps in Settings if the labels differ.

Create the connector

Back in Settings → Connectors, choose Create. Name it Sequenzy and enter this server URL:

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

Approve access

ChatGPT opens Sequenzy in your browser. Sign in, choose what ChatGPT may do (see permissions) and select Allow.

Use it in a chat

Start a new chat, open the tools menu in the message box and enable Sequenzy. Then check the connection.

ChatGPT uses a dedicated URL ending in /openai. It has the same account permissions, but leaves out tools that return secrets or raw webhook payloads, such as creating API keys and subscription links. Use the dashboard or a local client for those. A few tools have clearer names there, such as list_sending_domains for list_websites. What this surface filters.

ChatGPT tasks can also be woken by Sequenzy events, such as a reply to a campaign or a new subscriber. See MCP Events.

Claude

One connector works across Claude on the web, the desktop app and mobile.

Sequenzy AI agent connection flow with callouts showing connector and authorization steps

Add a custom connector

In Claude, open Settings → Connectors and choose Add custom connector. On Team and Enterprise plans, an organization owner may need to add it first.

Enter the Sequenzy URL

Name it Sequenzy and enter:

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

Approve access

Claude opens Sequenzy in your browser. Sign in, choose what Claude may do (see permissions) and select Allow.

Use it in a chat

In a new chat, make sure Sequenzy is enabled in the tools menu, then check the connection.

Claude calls Sequenzy from Anthropic’s cloud, so the connector keeps working on your phone without the desktop app open.

Coding assistants

For Claude Code, Codex, Cursor, Windsurf and VS Code Copilot, run the setup wizard in your terminal:

npx @sequenzy/setup

The wizard:

Opens your browser so you can sign in and choose permissions
Creates a personal API key for you
Finds the supported assistants installed on your computer, including Claude Desktop
Adds Sequenzy to each one, using the assistant’s own CLI where it has one

Restart your assistant when the wizard finishes, then check the connection.

Configure a client manually

Use manual setup if the wizard does not detect your assistant or you manage configs yourself. You need a personal API key (it starts with seq_user_). In the dashboard, open AI Agent Setup, pick your assistant, switch to Local MCP and use Manual fallback to create one. You can also create it under Account Settings → API Keys. Replace seq_user_your_key_here below with your key, then restart the assistant.

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

To share the server with a project, add it to .mcp.json instead, using the same JSON as the Cursor tab. Keep real keys out of committed files.

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

Run codex mcp list to confirm Codex sees the server. To edit the config by hand, add this to ~/.codex/config.toml:

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

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

Add this to ~/.cursor/mcp.json, creating the file if needed:

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

Use the same JSON as the Cursor tab in:

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

VS Code Copilot uses a servers object in its MCP config:

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

The Claude connector is the simplest option. To run Sequenzy locally instead, add the Cursor tab’s JSON to:

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

Use the remote URL instead

Coding assistants that support remote MCP servers with OAuth sign-in can use https://api.sequenzy.com/v1/mcp instead of the local server, the same way Claude does. In AI Agent Setup, switch your assistant to Remote MCP to see this option. Remote connections need no Node.js and no key in your config.

Other MCP clients

For OpenClaw, Hermes and other MCP clients, use either option:

Remote: https://api.sequenzy.com/v1/mcp. Clients that support OAuth open the Sequenzy approval page. Clients that only support custom headers can send Authorization: Bearer seq_user_your_key_here instead.
Local: command npx, args -y @sequenzy/mcp, and environment variable SEQUENZY_API_KEY=seq_user_your_key_here. If the client asks for JSON, use the mcpServers shape from the Cursor tab above unless its docs say otherwise.

Check that it works

Ask your assistant:

Use the Sequenzy MCP tools to tell me my current company, subscriber count, and one landing page, campaign, or sequence I can work on.

It should name your workspace and answer from your real data. If it says it has no Sequenzy tools, see troubleshooting. Then try a real task:

“Create a welcome sequence for my SaaS with a 14-day free trial. Keep it as a draft so I can review it.”
“How did my last campaign perform compared with the one before?”
“Create a segment of customers who bought our Pro plan in Stripe.”
“Draft a product update campaign about our new feature and show me a preview.”

New sequences and campaigns start as drafts. Your assistant can only send or activate them if you gave it permission. Browse everything it can do in the MCP tool reference.

Choose what your assistant can do

When you approve a remote connector or run the setup wizard, you pick a permission preset. Safer agent access is the default and suits most people.

Preset	Your assistant can
Safer agent access	Inspect data and draft content. It can’t send live emails or delete data
AI drafting	Draft campaigns, lists and sequences. It can’t send live emails
Marketing sender	Manage and send campaigns and live sequences
Transactional sender	Send transactional emails through the API
Full access	Everything, including sending, settings, API keys and deletes

Your workspace role still applies: an assistant never does more than you can do in the dashboard. You can widen permissions later without reconnecting. See MCP permissions and privacy for exact scopes, how to fix a missing permission and what data your AI provider receives.

Some setup, billing, destructive account actions, advanced configuration and final send decisions may still need the dashboard or your explicit review. MCP covers many common workflows, but not every dashboard feature.

Hand off from the dashboard

The AI assistant sidebars in the sequence builder and the email editor include an Open in menu next to the message box. Type what you want to change, then:

Copy prompt copies an agent-ready prompt that includes your company ID and the current sequence or campaign, for use with any agent
Open in ChatGPT or Open in Claude opens the prompt in a new chat
Open in Cursor opens the prompt in the Cursor desktop app
Set up Sequenzy MCP opens AI Agent Setup if your agent is not connected yet

Agents connected through Sequenzy MCP use the IDs in the prompt to inspect and edit the exact resource you were working on. The prompt is self-sufficient: it names your workspace and ends with the two ways an unconnected agent can get access: add the remote MCP server URL in its connector settings (with a link to this page), or use an API key you create in the dashboard under Settings → API Keys & SMTP against the REST API. The prompt never contains an API key, because it travels through the clipboard and hosted agent URLs. Paste a key to the agent directly instead.

Troubleshooting

My assistant doesn't show any Sequenzy tools

Fully quit and reopen the assistant after changing its config. In Claude Code run claude mcp list, and in Codex run codex mcp list, to confirm the sequenzy server is registered. In ChatGPT and Claude, enable the Sequenzy connector in the chat’s tools menu. Local servers need Node.js: run npx --version in a terminal to check.

Missing MCP API key or MCP_AUTH_REQUIRED

The local server started without SEQUENZY_API_KEY. It still lists its tools, but every call returns this error. Run npx @sequenzy/setup, or add the key to your config as shown in manual setup, then restart the assistant.

Invalid API key

The key was revoked or mistyped. Create a new one in AI Agent Setup or Account Settings → API Keys, update your config and restart. For a remote connector, disconnect Sequenzy in your assistant and connect again.

API key permission required

The connection works but your preset doesn’t allow that action. You can widen the permissions on the existing key without reconnecting. Follow Recover from missing permissions.

It's working in the wrong workspace

Ask your assistant to list your Sequenzy workspaces and switch to the right one. It uses get_account and select_company. See working across multiple workspaces.

I want to disconnect an assistant

Remove the connector or server in your assistant, then revoke its key under Account Settings → API Keys. Remote connections appear there as personal keys named Claude Remote MCP, whichever assistant created them.

Technical details

Endpoint or package	Use
`https://api.sequenzy.com/v1/mcp`	Remote server with the complete tool set. `/mcp` is an alias
`https://api.sequenzy.com/v1/mcp/openai`	Remote server reviewed for ChatGPT, without secret-producing tools
`@sequenzy/mcp`	Local stdio server with the complete tool set
`@sequenzy/setup`	Setup wizard that creates a key and configures local clients

The remote server speaks Streamable HTTP over POST. It is stateless and never pushes server-initiated messages, so it answers the optional GET event-stream request with 405 Method Not Allowed, the protocol’s way of saying no stream is on offer. Clients treat that as an expected response and use POST only. The endpoint speaks MCP specification 2026-07-28 and remains compatible with 2025-era clients that still use the initialize handshake. Remote sign-in uses OAuth with dynamic client registration and PKCE. The remote server also accepts a Sequenzy API key as Authorization: Bearer or x-api-key. The local server reads SEQUENZY_API_KEY; there is no workspace setting in the config, because your assistant chooses the workspace at runtime. Agents that support user-approved service registration can also discover the current flow through auth.md. For broader agent setup notes, including the difference between API/MCP auth and dashboard signup, read agents.md.

MCP tool reference

Every tool, resource and workflow your assistant can use

Permissions and privacy

Presets, scope recovery and what data MCP clients receive

CLI

Run the same workflows from your terminal or scripts

Skills

Give your agent a versioned Sequenzy workflow guide

Get Started

AI Agents

Connect Your App

Send Transactional Email

Audience

Automations and Campaigns

Email Design

Forms and Landing Pages

Analytics

Deliverability

SMS and Push

Integrations

Ecommerce

Workspace and Billing

Connect AI Assistants (MCP)

Pick your setup

ChatGPT

Claude

Coding assistants

Configure a client manually

Use the remote URL instead

Other MCP clients

Check that it works

Choose what your assistant can do

Hand off from the dashboard

Troubleshooting

Technical details

MCP tool reference

Permissions and privacy

CLI

Skills

​Pick your setup

​ChatGPT

​Claude

​Coding assistants

​Configure a client manually

​Use the remote URL instead

​Other MCP clients

​Check that it works

​Choose what your assistant can do

​Hand off from the dashboard

​Troubleshooting

​Technical details

​Related

MCP tool reference

Permissions and privacy

CLI

Skills

Pick your setup

ChatGPT

Claude

Coding assistants

Configure a client manually

Use the remote URL instead

Other MCP clients

Check that it works

Choose what your assistant can do

Hand off from the dashboard

Troubleshooting

Technical details

Related