MCP

VS Code (GitHub Copilot)

Last verified: 2026-07-21

Works in Copilot Chat's Agent mode on any individual Copilot plan, including Copilot Free — MCP has been built in since VS Code 1.102 (July 2025), so just keep VS Code up to date. Business and Enterprise workspaces may need an admin to allow MCP servers first.

Prerequisites

  • A Manyreach account + your API key (Manyreach web app → API & Integrations)
  • VS Code (latest stable recommended) with the GitHub Copilot Chat extension and an active Copilot subscription (Free counts)
  • Business / Enterprise: confirm with your admin that MCP servers are allowed for your organization

Steps

The fastest path is the official one-click link:

Install in VS Code →

VS Code asks you to confirm, then adds and starts the server — continue at step 3. Prefer to see exactly what you're adding? Do it by hand:

  1. In your project, open (or create) the file .vscode/mcp.json — this version travels with the project, so your team gets it too. For a personal setup that applies to every project instead, run MCP: Open User Configuration from the Command Palette (Ctrl/Cmd+Shift+P) — or let the guided MCP: Add Server command (choose HTTP, paste the URL, pick Global or Workspace) write the file for you.

  2. Add:

    {
  "servers": {
    "manyreach": {
      "type": "http",
      "url": "https://mcp.manyreach.com/mcp"
    }
  }
}

  3. VS Code starts the server automatically (or click Start above the entry). Approve the trust prompt the first time it appears.

  4. Open Copilot Chat, switch to Agent mode, click Configure Tools, and confirm manyreach's tools are listed and enabled.

What the authorization looks like

VS Code opens your browser to a Manyreach authorization page — a separate step from the trust prompt above. Paste your API key there and click Authorize. The key is checked once and never shown to the AI — afterwards the connection stays signed in on its own.

Verify

Ask Copilot to "describe the Manyreach catalog". It should call the describe tool and list resources like campaign, prospect, and sender.

Troubleshooting

  • "Cannot have more than 128 tools per request" — deselect other tools or servers you're not using for this task in Configure Tools; our own 3-tool design adds very little to this ceiling.
  • Keeps re-prompting to trust the server — expected after every config change; run MCP: Reset Trust if it seems stuck regardless.
  • Nothing happens after editing mcp.json — restart the server from MCP: List Servers, or reload the window. The same list's Show Output entry has the server log if it won't start.
  • Server missing entirely on a Business/Enterprise account — your organization's MCP servers in Copilot policy may not allow custom servers yet; ask an admin to check it (and whether access is restricted to registry servers only).