> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mailkick.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect an AI assistant with MCP

> Use Claude, ChatGPT, Cursor, or Claude Code with your Mailkick workspace

MCP lets an AI assistant work with your Mailkick emails, components, images, and design tokens. Ask it to inspect an email, build a draft using your existing styles, or prepare a translation.

The assistant acts as the person who connects it. Its access follows your current workspace role, and changes appear under your name in version history.

## Choose how to connect

| Tool | Connection method |
| - | - |
| Claude.ai | Server URL, then sign in to Mailkick |
| ChatGPT | Server URL, then sign in to Mailkick |
| Claude Desktop | Generated configuration containing a personal API key |
| Cursor | Generated configuration containing a personal API key |
| Claude Code | Generated terminal command containing a personal API key |

## Get the connection details

<Steps>
  <Step title="Open MCP settings">
    In Mailkick, open **Settings → MCP**. Use **How it works** for an overview of access and permissions.
  </Step>

  <Step title="Create a personal key">
    Click **Create Key** and give it a recognizable name, such as "Cursor". **Read-only** is enabled by default. Leave it enabled for browsing, or turn it off if a tool using this key needs to edit your emails.
  </Step>

  <Step title="Select your assistant">
    In **Connect Mailkick**, select your tool. Mailkick displays the appropriate server URL, configuration, or command. Copy it before closing the dialog.
  </Step>
</Steps>

<Note>
  Claude.ai and ChatGPT use the server URL without an API key and ask you to sign in. The key's **Read-only** setting applies to tools using that key; it does not change a connection authorized through sign-in.
</Note>

## Claude.ai and ChatGPT

1. Select **Claude.ai** or **ChatGPT** in **Connect Mailkick** and copy the server URL.
2. Open the assistant's custom connector settings, using the button in the dialog if available.
3. Add the Mailkick server URL and start the connection.
4. Sign in to Mailkick, check the app and workspace shown on the consent screen, and approve the connection.

Custom connector availability depends on your assistant's plan and workspace settings. If the assistant does not offer custom connectors, use a supported tool from the table above.

## Cursor, Claude Code, and Claude Desktop

* **Cursor**: Copy the generated configuration into `.cursor/mcp.json`, merging it with any servers already configured, then reload Cursor.
* **Claude Code**: Copy and run the generated terminal command.
* **Claude Desktop**: Add the generated server entry to `claude_desktop_config.json`, keeping any existing server entries, then restart the app.

<Warning>
  Configurations and commands for these tools contain your personal API key. The full key is shown only once. Keep it private and do not commit it to a repository. If you lose it, create a replacement key and update your tool's configuration.
</Warning>

## What to ask your assistant

* "List my emails and summarize the structure of the welcome email."
* "Build a welcome email using our existing header, footer, colors, and button styles."
* "Translate this email into French using our translation rules."
* "Export the HTML of this email so I can use it in my sending tool."

If a change affects shared components or design tokens, Mailkick can return a review link. Open it in Mailkick and approve the proposed change there before asking the assistant to continue.

## Permissions and disconnecting

A connection does not grant a higher role. Changing your workspace role changes what the assistant can do; leaving the workspace removes its access. A read-only key can inspect content but cannot write changes.

* **Signed-in apps**: In **Settings → MCP → Connected apps**, click **Disconnect** to revoke the app's connection.
* **Personal API keys**: In **Settings → MCP**, delete the relevant key to revoke tools using it. Replace the key in your tool if you want to reconnect.

## Troubleshooting

| Issue | What to check |
| - | - |
| The assistant can read but cannot edit | For a key-based connection, check whether the key is read-only. Also check your workspace role. |
| Authentication fails | Copy the correct connection details for your tool. Signed-in apps use the URL without a key; other tools use the generated configuration or command. |
| A shared change is waiting | Open the Mailkick review link, review the affected content, and approve it before continuing. |
| A revoked connection still appears in the assistant | Remove or reconnect the server in that assistant's settings. |

For sending-tool synchronization, use the [ESP integration guides](/). To receive email HTML on your own endpoint, see [Webhooks](/integrations/webhook).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.