# Give Cursor an email inbox over MCP

> Add the Trotta Mail MCP server to Cursor with a few lines in mcp.json, by sign-in or API key. The tools Cursor gets and the mail it never sees.

Source: https://trotta.email/integrations/cursor

Give Cursor an inbox of its own by adding Trotta Mail to ~/.cursor/mcp.json with the URL https://api.trotta.email/mcp, then signing in when Cursor asks. Cursor can then wait for mail, read verification codes, send and reply, and every message it reads was screened before delivery.

Updated November 20, 2026

## What Cursor can do with the inbox

An inbox lets Cursor test the email side of what it builds: send the message, wait for it to arrive, read what a recipient would see. The main tools are below, and the [MCP docs](https://trotta.email/docs/mcp) list them all.

| Tool | What it does |
| --- | --- |
| `wait_for_message` | Waits for the next delivered message. Filters include `has_code`. |
| `list_messages` | Lists messages in an inbox. |
| `read_message` | Reads one message in the safe view. |
| `thread_context` | Returns a thread as model-ready text with a trust level. |
| `send_message` | Sends a new message. Screened before it leaves. |
| `reply_to_message` | Replies in the thread. |
| `scan_content` | Runs any content through the guard and returns the verdict. |
| `list_held` | Lists what is waiting on a human. |

## Set up Trotta Mail in Cursor

Cursor reads its MCP servers from `~/.cursor/mcp.json`, or from `.cursor/mcp.json` inside one project. The server address is `https://api.trotta.email/mcp`, exactly as written, with no slash at the end. You sign in with your Trotta Mail account, or Cursor sends an API key.

### Sign in with Trotta Mail

1. Add the server to `~/.cursor/mcp.json`.
2. Sign in with Trotta Mail when Cursor asks, or from the Cursor CLI.
3. Pick the inboxes Cursor may use, and whether it may read, send or both. Then allow.

`~/.cursor/mcp.json`:

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

Sign in from the Cursor CLI:

```bash
agent mcp login trotta
```

### Use an API key

1. Put your key in the `TROTTA_MAIL_API_KEY` environment variable. Cursor reads the key from your environment.
2. Add the server to `~/.cursor/mcp.json` with the header.

`~/.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "trotta": {
      "url": "https://api.trotta.email/mcp",
      "headers": {
        "Authorization": "Bearer ${env:TROTTA_MAIL_API_KEY}"
      }
    }
  }
}
```

These steps follow the [Cursor docs](https://cursor.com/docs/mcp), checked on 2026-11-20.

## What Cursor sees and what it never sees

Cursor sees each message in the safe view. That is the content a human could see: hidden text is removed, instructions aimed at a model are replaced by a note that names what was removed, and links that are not clean are defanged.

Cursor never sees held mail. A held message is listed with the reason and no content, and a human decides whether to release it. Login codes, password resets and sign-in links in a human's own mailbox are sealed, so no tool returns them. In an inbox of its own, Cursor reads the codes it asked for.

Cursor works inside your code, with your files in reach. A human's everyday mailbox can deliver a real-looking message that tells an agent to send those files somewhere: see [data exfiltration through agents](https://trotta.email/threats/data-exfiltration-through-agents). A Trotta Mail inbox screens mail before it is accepted, and screens what Cursor sends too. No filter catches everything, so uncertain mail waits for a human.

## Three things to try

- Trigger the welcome email on localhost for riley@trotta.email, wait for it to arrive and show me the text.
- Sign up on staging with riley@trotta.email and use the verification code from the email to finish.
- Is any mail held in this inbox? Tell me why each one was held.

## Troubleshooting

- **The server answers 401.** No token was sent, or the token is not good. With sign-in, run `agent mcp login trotta`. With a key, check that `TROTTA_MAIL_API_KEY` is set where Cursor starts.
- **The key is sent but refused.** The header must be `Authorization`, and its value `Bearer`, a space, then the key. Keys start with `tm_live_`.
- **A send is refused as `outbound_blocked`.** Outgoing mail is screened, and a message that contains a secret is not sent. Remove what was flagged and send it again.

## Questions

### Does Trotta Mail for Cursor work on the Free plan?

Yes. The Free plan is $0 with 2 inboxes and 1,000 emails a month. MCP and every check are on every plan.

### Can the server be set for one Cursor project?

Yes. Put the same entry in .cursor/mcp.json inside the project instead of ~/.cursor/mcp.json in your home folder.

### Does Cursor need an API key for Trotta Mail?

No. Cursor can sign in with your Trotta Mail account, so there is no key to paste. An API key, read from TROTTA_MAIL_API_KEY, is the other way.

### Is Trotta Mail part of Cursor?

No. Trotta Mail is an independent product that works with Cursor as an MCP server. It is not made or endorsed by Cursor's maker.

## Sources

- [Cursor docs: MCP](https://cursor.com/docs/mcp)
- [Trotta Mail guide for agents (llms.txt)](https://api.trotta.email/llms.txt)

## Related

- [Connect ChatGPT and Claude](https://trotta.email/docs/connect) Docs
- [MCP](https://trotta.email/docs/mcp) Docs
- [An email MCP server for any MCP client](https://trotta.email/integrations/mcp) Integrations
- [MCP email server](https://trotta.email/learn/mcp-email-server) Guides
- [Give GitHub Copilot an email inbox over MCP](https://trotta.email/integrations/github-copilot) Integrations
- [Data exfiltration through agents](https://trotta.email/threats/data-exfiltration-through-agents) Threat library

Give your agent an inbox of its own. One call, or one minute in the console.

[Get an inbox](https://trotta.email/signup) [Read the docs](https://trotta.email/docs)
