How to Connect Cursor to Cold Email

Short answer: Cursor's agent has supported MCP servers since version 0.45 (January 2025), and since Cursor 1.0 (June 2025) remote servers can use OAuth or fixed headers. The hosted Outreach2day MCP server is live at https://public.outreach2day.com/mcp: the Add to Cursor link or one url entry in ~/.cursor/mcp.json adds it, you sign in to Outreach2day from Cursor (OAuth, no API key), and the agent can then check domains, quote mailboxes, run warmup and read replies. The agent can also call the REST API from your terminal, or you can run a small local MCP server over the same API.

Checked September 2026 against Cursor's MCP documentation, the Cursor 0.45 changelog and the Cursor 1.0 changelog.

Connection Methods

Cursor is a good fit when your cold email work already lives in files: lead CSVs, copy drafts, a script that sizes domains for a volume. The agent reads the repo and the API in the same session.

What Cursor Can Do With Your Cold Email Setup

Once Outreach2day is connected, Cursor can:

• Domains: check which names are free with POST /check_domains (up to 50 at a time) and list the workspace's domains with GET /domains. Buying domains through the API is paid right away — give an agent a billing-scoped key only if you want it to buy.

• Mailboxes: list mailboxes and their status with GET /mailboxes. New mailboxes are ordered in the app; the API lists and edits them.

• Warmup: read warmupState per mailbox with GET /warmup/mailboxes, and start or pause warmup with POST /warmup/operations and an idempotency key.

• Replies: list reply threads with a replyIntent label with GET /threads.

• Campaigns: draft sequences and copy in your repo. The campaign API is not enabled for every workspace yet; if you send from Instantly or Smartlead, the export endpoints add your mailboxes there.

Connect Cursor to Outreach2day, step by step

1. Add the server. Click Add to Cursor, or add an outreach2day entry with "url": "https://public.outreach2day.com/mcp" to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project); the installer writes the same entry: curl -fsSL https://outreach2day.com/install | sh -s -- --client cursor

2. Sign in from Cursor. Reload Cursor, open Cursor Settings, MCP, and sign in to outreach2day; Cursor opens the Outreach2day sign-in page and keeps the token

3. Check the tools. In Cursor's settings, confirm the server is listed with its tools

4. Ask a read-only question. Ask "list my domains" in agent mode and compare the answer with the app

5. No browser? Use an API key. For CI or a machine without a browser, run the installer with --use-key: it asks for the key once and the client config reads it from $OUTREACH2DAY_API_KEY

Without MCP, the agent can call the REST API from your terminal. Create a key only for Cursor on the API keys page (a key acts as your user in every workspace you belong to, so a separate key is easy to revoke), export it as OUTREACH2DAY_API_KEY in your shell profile or a git-ignored .env, and start a chat with: "The Outreach2day API is at https://public.outreach2day.com, auth is Authorization: Bearer $OUTREACH2DAY_API_KEY, docs at dev.outreach2day.com. Never print the key." Review each terminal command the agent proposes before it runs.

You can also run your own local MCP server over the API: save the read-only server from our cold email MCP server guide and register it as below. Cursor fills ${env:NAME} from your environment, so the key stays out of the file:

{
  "mcpServers": {
    "outreach2day-local": {
      "type": "stdio",
      "command": "/path/to/.venv/bin/python",
      "args": ["/path/to/o2d_mcp.py"],
      "env": {
        "OUTREACH2DAY_API_KEY": "${env:OUTREACH2DAY_API_KEY}",
        "O2D_WORKSPACE_ID": "${env:O2D_WORKSPACE_ID}"
      }
    }
  }
}

Add the Server by URL

Add an outreach2day entry with the server URL to ~/.cursor/mcp.json, or use the Add to Cursor link on the MCP page:

{
  "mcpServers": {
    "outreach2day": {
      "url": "https://public.outreach2day.com/mcp"
    }
  }
}

Then open Cursor Settings, MCP, and sign in to outreach2day. The installer writes the same entry:

curl -fsSL https://outreach2day.com/install | sh -s -- --client cursor

On Windows, in PowerShell: $env:O2D_CLIENT="cursor"; irm https://outreach2day.com/install.ps1 | iex. The installer asks for no API key. It backs up ~/.cursor/mcp.json and adds an outreach2day entry with the server URL only, next to the servers you already have. Reload Cursor, open Cursor Settings, MCP, and sign in to outreach2day: Cursor opens the Outreach2day sign-in page and keeps the token. For CI or a machine without a browser, run the installer with --use-key: it asks for the key once and the client config reads it from $OUTREACH2DAY_API_KEY.

Prompts to Try in Cursor

• "Read leads/q4.csv, count rows, and tell me how many mailboxes I need at 25 cold emails per mailbox per day to reach everyone in 10 working days."

• "Check whether these 10 domain ideas are free, and write the free ones to domains.txt. Do not buy anything."

• "Which mailboxes have been warming for less than 14 days? Output a table with address, domain and start date."

• "Lint copy/sequence.md: no links in any step, spintax on every subject, follow-up gaps 2, 3, 5 and 5 days."

More, grouped by task, in Cursor prompts for cold email.

Limits and Safety

• API limits and key safety: cold email API.

FAQ

Does Cursor support remote MCP servers?

Yes. An entry with url (and optional headers) connects to a remote server over Streamable HTTP or SSE; an entry with command starts a local stdio server. Cursor 1.0 added OAuth for servers that support it.

Is there an Outreach2day MCP URL I can paste into Cursor?

Yes: https://public.outreach2day.com/mcp. Cursor signs in to Outreach2day with OAuth, so the entry needs no key. The installer command above writes that entry to ~/.cursor/mcp.json for you. Without a browser, add "headers": { "Authorization": "Bearer ${env:OUTREACH2DAY_API_KEY}" } and keep the key in that variable.

Can Cursor buy domains or order mailboxes?

With the hosted server, Cursor quotes domains and mailboxes and gives you a Stripe checkout link; you pay on the Stripe page. Over the REST API it can call POST /domains/purchase, which is paid right away.

Where does Cursor store MCP settings?

In ~/.cursor/mcp.json for all projects or .cursor/mcp.json inside a project. Commit the project file only if it holds no secrets; use ${env:NAME} for keys.

Can Cursor send cold emails?

Yes, through a campaign on the hosted Outreach2day MCP server: Cursor builds the sequence and launch_campaign runs after 14 days of warmup, a passed preflight and your yes in the chat. The local read-only server has no send tool.

Related

• Outreach2day MCP for Cursor: what the hosted MCP server covers

• How to connect VS Code and GitHub Copilot to cold email

Create an account, add the server in Cursor and sign in; for CI, create a key on the API keys page.