# Connect ChatGPT and Claude to email

> Add Trotta Mail to ChatGPT, Claude, Claude Code, Codex or Cursor with one MCP server URL. Sign in, pick the inboxes it may use. No key to paste.

Source: https://trotta.email/docs/connect

Add Trotta Mail to an assistant with one URL. It signs in with your Trotta Mail account, so there is no key to paste.

MCP server URL:

```text
https://api.trotta.email/mcp
```

Use it exactly as written, without a slash at the end.

## What happens when you sign in

1. The assistant sends you to Trotta Mail. Sign in if you are not already.
2. Pick the inboxes it may use, or a pod, and whether it may read, send, or both.
3. Allow, and you are back in the assistant.

### It can

- Read the safe view of mail in the inboxes you picked: hidden text removed, risky links defanged.
- Send and reply as those inboxes, screened before anything leaves.
- Write drafts in your own mailbox, for you to send.

### It cannot

- Read held mail, or release it. Only a human does.
- See login codes, password resets or sign-in links in your own mailbox.
- Change protection, create inboxes or keys, or reach an inbox you did not pick.

### Email sending

On the same screen, choose how it sends email. Change it any time.

- **Ask before every email**, the default. The assistant asks you before each email.
- **Don't send email (drafts only)**. It writes drafts, and you send them.
- **Send without asking**. Every email is still screened before it leaves.

Change it or disconnect any time in the console under [Connected apps](https://trotta.email/console/apps). It applies at once.

## ChatGPT

1. On the web, open **ChatGPT Plugins**, select the plus button, then **Add custom MCP server**.
2. Enter a name, such as Trotta Mail. Under **Connection**, enter the Server URL `https://api.trotta.email/mcp`.
3. For authentication, choose **OAuth**.
4. Select **I understand and want to continue**, then **Create as a plugin**.
5. Install it from your plugins, and sign in to Trotta Mail when it asks.
6. In a chat, type `@` and pick it.

Custom MCP servers in ChatGPT depend on your plan and your workspace settings.

## Claude

1. Go to **Customize**, then **Connectors**. Select **Add**, then **Add custom connector**.
2. Enter a name and the URL `https://api.trotta.email/mcp`, then **Continue**.
3. Keep what Claude marks **Detected**: **Sign in now**, and **Use Claude's published identity**.
4. Click **Add**, then **Connect**, and sign in to Trotta Mail.

On Team and Enterprise plans, an Owner adds it under **Organization settings**, **Connectors**: **Add**, **Custom**, **Web**. Each member then clicks **Connect**.

## Claude Code

```bash
claude mcp add --transport http trotta-mail https://api.trotta.email/mcp
```

Then run `/mcp` in Claude Code, or `claude mcp login trotta-mail` in your shell, and sign in in the browser.

## Codex

```bash
codex mcp add trotta-mail --url https://api.trotta.email/mcp
codex mcp login trotta-mail
```

In the desktop app and the IDE extension, select **Authenticate** when it asks.

## Cursor and other MCP clients

In Cursor, add it to `~/.cursor/mcp.json`, or `.cursor/mcp.json` in a project. Cursor signs in with OAuth.

`mcp.json`:

```json
{
  "mcpServers": {
    "trotta-mail": { "url": "https://api.trotta.email/mcp" }
  }
}
```

Any client that follows the MCP Authorization spec needs only the URL: it finds the rest on its own. One without OAuth sends an API key instead, as `Authorization: Bearer tm_live_...`. See [MCP](https://trotta.email/docs/mcp).

## For developers

| What | Where |
| --- | --- |
| Protected resource metadata | `https://api.trotta.email/.well-known/oauth-protected-resource/mcp` |
| Authorization server metadata | `https://api.trotta.email/.well-known/oauth-authorization-server` |
| Registration | Client ID Metadata Documents, or `POST /oauth/register` |
| Flow | Authorization code with PKCE (S256 only), resource indicator required |
| Scopes | `mail:read`, `mail:send` |
| Tokens | Access 1 hour. Refresh 30 days, rotated on every use; a reused one ends the connection. |
| Redirects | https, or http on 127.0.0.1, [::1] or localhost with any port |
