# Connect Your AI

Flomailr runs a hosted connector that speaks the Model Context Protocol (MCP). Once your AI app is connected, you can ask it to design emails in your brand, preview them, save drafts, and send, using your own Flomailr workspace. Flomailr does the layout, typography and colour. Your AI writes the words and picks the sections.

The connector URL is the same for everyone:

```text
https://flomailr.com/api/mcp
```

`Settings > Connect your AI` in the dashboard shows this page's instructions with copy buttons.

## Claude on the web and in the desktop app

1. In Claude, open `Settings`, then `Connectors`.
2. Choose `Add custom connector`, name it Flomailr, and paste `https://flomailr.com/api/mcp`.
3. Claude opens Flomailr's approval screen. Sign in if asked, check the workspace name shown on the screen, and click `Allow access`.
4. Start a chat with the Flomailr connector turned on and ask for an email.

The first time Claude shows an email preview, it asks whether to allow it. Click `Allow` to see the rendered email, with desktop, mobile and dark mode views, inside the chat.

This route uses OAuth. You sign in with your own Flomailr login, and the connector acts in the workspace you approved.

## Claude Code

Add the connector from your terminal:

```bash
claude mcp add --transport http flomailr https://flomailr.com/api/mcp
```

Start Claude Code, run `/mcp`, pick `flomailr` and sign in. Your browser opens the same Flomailr approval screen.

To use an API key instead of signing in, pass it as a header. An admin creates the key under `Settings > API keys` (see [API Keys](/docs/api/api-keys)):

```bash
claude mcp add --transport http flomailr https://flomailr.com/api/mcp \
  --header "Authorization: Bearer <your API key>"
```

## Cursor

Not yet verified by Flomailr. Cursor supports remote MCP servers through its MCP settings. Add a server named `flomailr` with the URL above. If Cursor offers to sign in, approve access on the Flomailr screen. If it asks for a header instead, send `Authorization: Bearer <your API key>`. If a step does not match what you see, email hello@flomailr.com and say what happened.

## ChatGPT

Not yet verified by Flomailr. ChatGPT can add custom connectors in developer mode. Add a custom connector with the URL above, choose OAuth if it asks how to sign in, and approve access on the Flomailr screen. If a step does not match what you see or the connection fails, email hello@flomailr.com.

## Sign in or use an API key

|                       | Sign in (OAuth)                                                    | API key                                        |
| --------------------- | ------------------------------------------------------------------ | ---------------------------------------------- |
| Who approves          | You, with your own Flomailr login                                  | A workspace admin creates the key              |
| Workspaces            | Can list and switch between the workspaces your account belongs to | Locked to the one workspace the key belongs to |
| Brand and suppression | Only owners and admins can change them, as in the dashboard        | Allowed, because keys are created by admins    |
| Revoke                | `Settings > Connected apps`                                        | `Settings > API keys`                          |

Over OAuth the connector offers 34 tools. With an API key it offers 32, without `list_workspaces` and `switch_workspace`. See the [MCP Tool Reference](/docs/ai/tools).

Each workspace is a separate business. Contacts, lists and campaigns never cross between them. If you run several, name the business in your request and the AI will switch to it.

## Disconnect

Open `Settings > Connected apps` and click `Disconnect` next to the app. It stops working immediately and would have to ask for your approval again to reconnect. Members see the apps they approved. Owners and admins see every connection in the workspace.

To cut off a key, revoke it under `Settings > API keys`.

## See what the AI did

Every action the connector takes, such as saving a draft, a dry run, a send, a suppression change or a brand update, is written to an append-only log. Owners and admins can read it under `Settings > Activity`, and you can ask your AI to read it with the `get_action_log` tool. Revoking a key or disconnecting an app does not erase the log.

## What to ask first

- "Import our brand from https://yourwebsite.com and show me the logo, colors and fonts you picked up."
- "Write this month's newsletter in our brand, with these three posts as article cards and a button to the shop. Show me a preview."
- "Send the 'Spring sale' draft to the Customers list. Do a dry run first and tell me who would get it and who would be skipped."

More in [Designing Emails with AI](/docs/ai/design-emails) and [Sending Safely with AI](/docs/ai/send-safely).

## For agents and developers

Flomailr publishes machine-readable descriptions of itself, so AI agents and MCP clients can find and configure it without these instructions:

- [llms.txt](https://flomailr.com/llms.txt) lists every docs page, and each page has a Markdown copy at the same address with `.md` on the end (for example [this page](https://flomailr.com/docs/ai/connect.md)). [llms-full.txt](https://flomailr.com/llms-full.txt) is all of it in one file.
- The [MCP Server Card](https://flomailr.com/api/mcp/server-card) describes the connector and how to connect, and the [AI Catalog](https://flomailr.com/.well-known/ai-catalog.json) points domain-level discovery at it.
- The [OpenAPI spec](https://flomailr.com/openapi.json) describes the REST API, for coding agents that call it directly instead of using MCP.