# Connect Mailnaptic to AI Assistants (MCP)

Let Claude, ChatGPT, Cursor and other AI assistants look at your campaigns and, if you allow it, work in your account.

## Connect Mailnaptic to AI Assistants

Mailnaptic has an MCP server. MCP (Model Context Protocol) is the standard way for AI assistants such as Claude, ChatGPT, Codex and Cursor to use another product. Once connected, you can ask an assistant things like “How did last week’s campaign do?”, “Which of my lists is the biggest?” or “Draft a campaign for the autumn sale to my customers list”.

Connecting is available on the **Growth plan and above**, and only an **owner or admin** can connect an assistant.

### Connect with one click

1. In your assistant, add a custom connector or MCP server with this address: `https://api.mailnaptic.com/mcp`. In Claude this is under **Settings → Connectors → Add custom connector**. In Claude Code run `claude mcp add --transport http mailnaptic https://api.mailnaptic.com/mcp`.
2. The assistant opens a Mailnaptic page. Sign in if you are asked to.
3. Choose what it may do and click **Allow**. If you use two-factor sign-in, enter a code from your authenticator app.
4. You are sent back to the assistant, which is now connected.

### Choose what it may do

- **Read only** (recommended). The assistant can see campaigns and their results, lists, contacts, segments, automations, sending domains and store revenue. It cannot change anything.
- **Read and write.** It can also add contacts and lists, create campaign drafts, send test emails, pause automations, and schedule or send campaigns. It cannot change sending domains, webhooks, store connections or account settings, and it cannot delete anything.

The connection is an API key with exactly those permissions, so Mailnaptic itself refuses anything else. The assistant only sees the tools its key allows.

### Sending stays in your hands

- Campaigns the assistant creates are **drafts**. Nothing is sent until a campaign is scheduled or sent.
- Scheduling or sending needs an explicit confirmation from the assistant, and the assistant is told to show you the subject, content and audience and to offer a test email first. Check what it shows you before you say yes.
- The normal sending rules still apply: a verified domain, a mailing address, spam checks and your plan’s limits.

### What the assistant can do

- **Look:** account overview, campaigns and their results, lists, contacts and their activity, segments, automations, sending domains and store revenue.
- **Change (read and write):** add a contact, unsubscribe a contact, create a list, create a campaign draft, send a test email, schedule or send a campaign, cancel a scheduled campaign and pause an automation.

### Connect with an API key instead

If your assistant cannot sign in with a click, create an API key under **Organization → API keys** with the scopes you want, and give the assistant the address `https://api.mailnaptic.com/mcp` and the header `Authorization: Bearer mnpk_…`.

### Disconnect

Each connection is an API key named after the assistant, for example **Claude (AI assistant)**. Revoke it under **Organization → API keys** to disconnect it straight away. A connection also stops by itself after a year. Connecting is recorded in the audit log.

> **Tip:**
> 
> Start with
> 
> **Read only**
> 
> . You can connect again with read and write later, when you want the assistant to draft campaigns.
