How to Connect GitHub Copilot to Cold Email

Short answer: GitHub Copilot's agent mode in VS Code uses MCP servers, and MCP support has been generally available in VS Code since version 1.102 (July 2025). Servers are declared under mcpServers in .mcp.json (or ~/.copilot/mcp-config.json), and secrets can come from a password prompt instead of the file. The hosted Outreach2day MCP server is live at https://public.outreach2day.com/mcp: the Install in VS Code link or one url entry adds it, VS Code asks you to sign in to Outreach2day (OAuth, no API key), and Copilot can then check domains, quote mailboxes, run warmup and read replies. A small local server over the REST API is the other option.

Checked September 2026 against Add and manage MCP servers in VS Code, the MCP configuration reference and the VS Code 1.102 release notes.

Connection Methods

Organizations can manage which MCP servers Copilot may use through GitHub policies, so on a company account check with your admin first. With inputs, .vscode/mcp.json holds no secret and can be shared with the repo.

What Copilot Can Do With Your Cold Email Setup

Copilot in agent mode is at its best when the cold email work sits next to code: a repo with lead files, copy drafts and scripts. With the server connected it can:

• Plan capacity. Read a lead file and work out mailboxes and domains at 25 cold emails per mailbox a day and 5 mailboxes per domain.

• Check domain ideas. Call check_domains for up to 50 names and write the free ones to a file. Nothing is bought.

• Report warmup. List mailboxes by warmupState and flag any warming for less than 14 days.

• Read replies. Pull recent reply threads with their intent label and summarise them.

• Lint copy. Check a sequence file for links, missing spintax on subjects and follow-up gaps other than 2, 3, 5 and 5 days.

Starting or pausing warmup is a write; add it only with an approval step, as in MCP server for email warmup.

Connect Copilot in VS Code to Outreach2day, step by step

1. Add the server. Click Install in VS Code on the MCP page for VS Code, or add an outreach2day server with "type": "http" and "url": "https://public.outreach2day.com/mcp" under mcpServers in .mcp.json at the workspace root (~/.copilot/mcp-config.json for every workspace); the installer adds the same server: curl -fsSL https://outreach2day.com/install | sh -s -- --client vscode

2. Start the server and sign in. Use the Start action above the server entry, or run "MCP: List Servers" from the Command Palette; VS Code opens the Outreach2day sign-in page, you sign in and allow access

3. Use it in agent mode. Open Copilot Chat, switch to Agent and check the server's tools in the tools picker

4. Ask a read-only question. Ask "list my domains"; VS Code can ask you to confirm each tool call; 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

VS Code also reads a user-level configuration ("MCP: Open User Configuration") if you want the server in every workspace.

To run your own read-only server over the REST API instead, create a key only for Copilot on the API keys page, copy o2d_mcp.py from the cold email MCP server guide, install mcp and requests in a virtual environment and use absolute paths in the config. The inputs entry makes VS Code ask for the key once and store it, instead of writing it in the file:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "o2d-key",
      "description": "Outreach2day API key",
      "password": true
    }
  ],
  "servers": {
    "outreach2day-local": {
      "type": "stdio",
      "command": "/path/to/.venv/bin/python",
      "args": ["/path/to/o2d_mcp.py"],
      "env": {
        "OUTREACH2DAY_API_KEY": "${input:o2d-key}",
        "O2D_WORKSPACE_ID": "123"
      }
    }
  }
}

Add the Server by URL

Click Install in VS Code on the MCP page for VS Code, or add the server to .mcp.json at the workspace root (~/.copilot/mcp-config.json for every workspace). Start the server and sign in to Outreach2day when VS Code asks:

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

The installer adds the same server:

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

On Windows, in PowerShell: $env:O2D_CLIENT="vscode"; irm https://outreach2day.com/install.ps1 | iex. The installer asks for no API key. It backs up your VS Code user mcp.json and adds an outreach2day server of type http with the URL only. Reload VS Code and start the server: VS Code registers itself with our sign-in server and opens the Outreach2day sign-in page. Then open Copilot Chat in agent mode. 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.

More clients are on the MCP page.

Prompts to Try in Copilot Agent Mode

• "Read leads/list.csv and tell me how many mailboxes and domains I need to email everyone once in 10 working days."

• "Check the domain ideas in domains/ideas.txt and write the free ones to domains/free.txt. Do not buy."

• "List mailboxes still warming, with the number of days since warmup started."

• "Review copy/sequence.md: flag links, subjects without spintax and follow-up gaps that are not 2, 3, 5, 5 days."

Limits and Safety

FAQ

Does GitHub Copilot support MCP servers?

Yes, in agent mode. In VS Code, MCP support became generally available in version 1.102. Servers are declared under mcpServers in .mcp.json (or ~/.copilot/mcp-config.json); a remote server such as Outreach2day takes "type": "http" and its url.

How do I keep the API key out of .vscode/mcp.json?

With the hosted server there is no key: VS Code signs in with OAuth. For a key setup, declare an input with "type": "promptString" and "password": true, then reference it as ${input:o2d-key}. VS Code asks for the value once and stores it.

Is this the same as Microsoft Copilot Studio?

No. Copilot Studio builds business agents and connects to MCP servers and OpenAPI connectors on its own; see how to connect Copilot Studio to cold email.

Can Copilot send my cold emails?

Yes, through a campaign on the hosted Outreach2day MCP server: Copilot 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.

Do I pay extra for API access?

No. The API is part of every Outreach2day plan; see pricing.

• API limits and key safety: cold email API.

Related

• Outreach2day MCP for VS Code: what the hosted MCP server covers

• Cold email API

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