EmailOctober 12, 20265 min read

How to Give Cursor an Email Address

Give Cursor a dedicated agent inbox over Mermail MCP — OAuth, no Gmail credential in the agent loop. Same pattern as Claude Code, Grok, Muse, and Codex.

By Toan Nhu

Mermail explainer: give Cursor an email address

Cursor talks to tools over MCP. Builders searching for cursor email or how to get Cursor sending and receiving mail often reach for personal Gmail first — the wrong default for an agent that can list, draft, and send unattended. Give Cursor a dedicated agent inbox instead.

Mermail hosts a remote MCP server so Cursor gets its own mailbox identity — without an x-api-key in the config. Product surface: mermail.app/integrations/cursor.

TL;DR — Do not wire Cursor to your personal Gmail. Add Mermail's hosted MCP URL (OAuth, no API key header), create a Free mailbox, then ask Cursor to list_mailboxes / create_mailbox / list_emails. Same agent-inbox pattern as Claude Code, Grok Bot, Muse, and Codex — one mailbox identity across hosts.

Why Cursor + personal Gmail is the wrong default

Cursor's agent loop can call MCP tools whenever a task needs mail. If those tools ride on a human Google identity, every list, search, or send shares credentials, reputation, and threads with your work and personal inbox. The model does not become safer because it lives in an IDE — Google still sees automation on a consumer or Workspace account.

People looking up cursor email, cursor send email, or cursor email sending usually want the IDE agent to own a mail tool surface — not to merge Cursor with a personal inbox. An MCP email server answers that with typed tools (create mailbox, list messages, read a thread, send when you allow it) instead of raw Gmail scopes.

What breaks when the agent shares your Gmail

Blast radius — a bad send, a prompt injection, or a noisy loop can flag the same account that holds your work and personal mail
Scope — OAuth to Gmail is broad; Cursor then has tool-level access to everything that token can reach
Identity — replies land in your human inbox; the agent cannot own a clean address for verification codes or vendor threads
Audit — you cannot cleanly answer what did this Cursor session send or read when the mailbox is shared
Lifecycle — spinning agents up and down should not require creating Google users or rotating personal passwords

If you already connected Cursor (or any MCP host) to Gmail for a demo, revoke that OAuth grant and move the agent to a dedicated mailbox before you leave it running overnight.

What an agent inbox looks like for Cursor

An agent inbox is a mailbox the agent owns: address, receive path, optional send path, retention, and MCP or API access. Cursor discovers tools at runtime from an MCP server — the same pattern Mermail uses for Claude Code, Codex, Grok Bot, and Muse.

Checklist for Cursor mail:

Dedicated mailbox (not your @gmail.com)
Remote MCP over Streamable HTTP with OAuth (no API key header in the Cursor config)
Receive-first profile for verification codes and vendor replies (agent-inbox) when you want a narrower tool surface
Clear workspace isolation if you run more than one agent

How to give Cursor an email address with Mermail

Four practical steps. Exact Cursor MCP UI labels can move between releases — adapt to your Cursor MCP settings and the current Cursor MCP docs — but the Mermail side is stable:

1. Create a Free Mermail workspace at console.mermail.app. Free includes 1 inbox and 1,000 emails/month — enough to prove the Cursor loop.

2. Add Mermail as a remote MCP server in Cursor. Fastest path: open the one-click install from mermail.app/integrations/cursor. Or add the URL manually — Streamable HTTP, no headers.

json

# Example shape — adapt to your Cursor MCP settings (.cursor/mcp.json or ~/.cursor/mcp.json)
{
  "mcpServers": {
    "mermail": {
      "url": "https://console.mermail.app/mcp"
    }
  }
}

# Receive-first tool surface (optional):
# "url": "https://console.mermail.app/mcp?profile=agent-inbox"
# Full catalog: https://console.mermail.app/mcp

3. Authenticate. Select Authenticate in Cursor, finish OAuth through console.mermail.app, then confirm Mermail no longer shows Authenticate. Do not put an x-api-key header in the Cursor config for this hosted server.

4. Verify in a new chat. Ask Cursor to list mailboxes (list_mailboxes). Then create a mailbox and work mail with tools such as create_mailbox, list_emails, get_email, and send when your workflow needs it.

Hands-on MCP walkthrough: How to Use MCP with Mermail's Email API. Conceptual primer: What Is an MCP Email Server?.

Same mailbox across Claude Code, Grok, Muse, and Codex

If you also run agents in Claude Code, Grok Bot, Meta Muse, or Codex, reuse the same Mermail MCP server and mailbox. The host changes; the inbox identity stays on Mermail. See Claude Code, Grok Bot, Muse, and Codex.

When Gmail still makes sense

If Cursor only drafts replies that a human pastes from a personal inbox, you do not need agent email. If you only need transactional send (receipts, password resets) with no agent-owned receive identity, a send API may be enough. Connect Gmail only when a human — not the agent — is the mailbox principal.

Mermail fit (live plans)

From mermail.app/pricing:

Free — $0: 1 inbox, 1,000 emails/mo — enough to prove the Cursor loop
Developer — $19/mo: 5 inboxes, custom domains
Growth — $49/mo: more capacity for small fleets
Enterprise — custom

Next step

Open console.mermail.app, create a Free mailbox, add Mermail from integrations/cursor (or point Cursor at https://console.mermail.app/mcp), finish OAuth, and let the agent own its address. That is email for AI agents — without putting Gmail in the blast radius.

FAQ

How do I give Cursor an email address?

Connect Cursor to a dedicated agent inbox over MCP — not your personal Gmail. Mermail's hosted MCP uses OAuth and no API key header; create a mailbox, then use list_emails / get_email / send as needed.

What does "cursor email" usually mean?

Builders searching cursor email, cursor send email, or cursor email sending usually want the Cursor agent to send or receive mail via tools — typically an MCP email server — rather than borrowing a human Gmail account.

Can Cursor and Claude Code share one Mermail inbox?

Yes. Both hosts can point at the same Mermail MCP URL; the mailbox identity stays on Mermail.

Do I need an API key in Cursor's MCP config?

No for Mermail's hosted Cursor integration. Use the URL only and finish OAuth. If the deeplink does not open Cursor, add a remote HTTP server manually with https://console.mermail.app/mcp and no headers.