MCP server for VS Code

Cold email MCP server for VS Code and GitHub Copilot

Copilot agent mode can run cold email from your workspace. Add Outreach2day in .mcp.json (or ~/.copilot/mcp-config.json) and Copilot orders mailboxes, starts warmup, builds campaigns from your files and reads replies.

https://public.outreach2day.com/mcp
Install in VS Code

Opens VS Code with the server configuration filled in

Setup guide
  1. Confirm the installation and trust the server
  2. Sign in with your Outreach2day account
  3. Open Copilot Chat in Agent mode
Use an install script
curl -fsSL https://outreach2day.com/install | sh -s -- --client vscode

Adds the server to VS Code / GitHub Copilot, after a backup of each config. Each client asks you to sign in to Outreach2day on first use. View the script

  • Orders paid through Stripe after you approve them
  • $2.50 per mailbox a month
VS Code · Outreach2day MCP

#outreach2day how many emails a day can our warm mailboxes send, and do we need more for 2,000 a day?

called outreach2day tools

34 warm mailboxes, 30 emails a day each: 1,020 a day.

For 2,000 a day you need 33 more mailboxes on 9 more domains.

Quote it? You pay on Stripe before anything is ordered.

teams have used Outreach2day
3,600+
emails sent a day
40M+

Among them

Can GitHub Copilot in VS Code run cold email through MCP?

Yes. An entry in .mcp.json (or ~/.copilot/mcp-config.json) with the server URL, then a sign-in when VS Code asks, gives Copilot agent mode tools for domains, mailboxes, warmup, campaigns and replies; you pay each order on Stripe.

Cold email in VS Code, step by step

  1. 1

    Add the server

    Add Outreach2day to .mcp.json (or ~/.copilot/mcp-config.json) and sign in with Prepare orders turned on. Copilot lists its tools in agent mode

  2. 2

    Size and order

    Copilot works out the mailboxes you need for your volume, quotes them and hands you the Stripe link

  3. 3

    Build from the workspace

    It turns copy and lead files in the repo into a draft campaign and checks the copy

  4. 4

    Launch and review

    After 14 days of warmup it launches, then reports replies and per-mailbox stats in the chat

Outreach2day in VS Code: where to connect

Setup details

VS Code: files, sign-in and limits

What VS Code's own documentation says about connecting a remote MCP server.

Config files
Portable format: .mcp.json at the workspace root or ~/.copilot/mcp-config.json for your user, with a top-level mcpServers object. VS Code still reads .vscode/mcp.json and the profile mcp.json (servers object) and lists them as deprecated destinations. VS Code docs: MCP configuration
Entry
type "http" (or "sse") and url. headers only when you use an API key. VS Code docs: MCP configuration
Entry
{  "mcpServers": {    "outreach2day": {      "type": "http",      "url": "https://public.outreach2day.com/mcp"    }  }}
OAuth
When the server asks for sign-in, VS Code runs the OAuth flow itself and keeps the token. Install in VS Code links open the same entry in the editor. VS Code docs: MCP authorization and install links
Keep the key out of the file
For an API key, put this example in .vscode/mcp.json or the file opened by MCP: Open User Configuration. It uses the VS Code servers format and a password input; VS Code asks once and stores the key. Use OAuth for Agent Host sessions. VS Code docs: MCP configuration
Keep the key out of the file
{  "inputs": [    { "type": "promptString", "id": "o2d-key", "description": "Outreach2day API key", "password": true }  ],  "servers": {    "outreach2day": {      "type": "http",      "url": "https://public.outreach2day.com/mcp",      "headers": { "Authorization": "Bearer ${input:o2d-key}" }    }  }}
First start
VS Code asks you to trust the server before it starts. Organizations can manage MCP access through GitHub policies. VS Code docs: MCP servers in Copilot

Works with Outreach2day

  • Copilot agent mode in VS Code with OAuth or a header
  • Workspace, user-profile and portable .mcp.json files

Does not work

  • Servers that need ${input:...} values in Agent Host sessions: VS Code does not forward them there, so use OAuth

The tools VS Code gets and the guardrails on orders are the same in every client: tool list, what the agent can and cannot do.

Prompts

Things to ask VS Code

Plain language is enough. The agent picks the tools and asks before anything costs money.

  • How many emails a day can our warm mailboxes send, and how many more do we need for 2,000?
  • Create a draft campaign from outreach/sequence.md and outreach/leads.csv.
  • Which domains have DNS records missing?
  • Show replies from the last 3 days that ask for pricing.
  • Pause the Q4 campaign until the bounce rate is back under 2%.

What VS Code can do with the server, job by job

Each page lists the tools for the job, an example session, prompts per assistant and the limits.

Setup

Connect VS Code

Add https://public.outreach2day.com/mcp to VS Code and sign in with your Outreach2day account when it asks. Then ask: "Check my Outreach2day account status". An API key is only for CI and headless setups.

Setup steps

OAuth sign-in

VS Code

  1. Click Install in VS Code, or add the block to .mcp.json at the workspace root (~/.copilot/mcp-config.json for every workspace)
  2. Start the server. VS Code asks you to sign in to Outreach2day
  3. The first time the client connects, it opens an Outreach2day sign-in page in your browser. Sign in, turn on Prepare orders so the assistant can quote orders and create Stripe checkout links, and allow access
  4. Open Copilot Chat in agent mode and check the tools list
Install in VS CodeVS Code docs: MCP authorization and install links
.mcp.json
{  "mcpServers": {    "outreach2day": {      "type": "http",      "url": "https://public.outreach2day.com/mcp"    }  }}

Or set up VS Code on this computer with one command

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

Sets up VS Code and adds the server by URL, after a backup of each config. Each client asks you to sign in to Outreach2day on first use. View the script

Book a call

Book a 30-minute call

Talk to the team that runs the MCP server. We check your setup for VS Code and your first order.

  • Free 30-minute call
  • Size domains and mailboxes for your volume
  • Walk through a quote and the Stripe checkout
  • Check your VS Code setup

See open times in your time zone and book on this page.

Or open the booking page

Customers

Teams that send with Outreach2day

  • “That was the best infrastructure and value for money I saw.”
    Ido RebhunIdo RebhunRenaissance
  • “…deliverability with your inboxes is better than our outlook/google inboxes…”
    Daniel DultsinDaniel DultsinControl
  • “We really would like to thank you for that report. We don’t know what we are doing with email and it is very reassuring to us to know we have a partner on top of the ball.”
    ReilcapBill OConnorReilcap

Questions

Or talk to the team

Does it work with GitHub Copilot?

Yes. Copilot agent mode in VS Code uses the MCP servers from mcp.json, so the Outreach2day tools show up there.

Does mcp.json hold a secret?

No. VS Code signs in to Outreach2day with OAuth and keeps the token itself, so the file has only the URL. If you use an API key instead, read it from an input variable (${input:o2d-key}) or ${env:OUTREACH2DAY_API_KEY} so the file holds no secret.

Why do the tools not show up in an Agent Host session?

VS Code does not forward servers that need interactive input, such as ${input:...}, to Agent Host. Sign in with OAuth for those sessions.

Other AI clients

The same server and the same tools in every client. Only the setup differs.

Guides for MCP and the API

Run cold email from VS Code

Domains, mailboxes, warmup, campaigns and replies from VS Code. You approve every order.

Setup stepsGet API key