GitHub Copilot MCP Setup: VS Code, JetBrains, Visual Studio, Xcode and Cloud Agent

GitHub Copilot can use MCP servers in Copilot Chat's agent mode in five IDEs: VS Code, Visual Studio, JetBrains IDEs, Xcode and Eclipse. Each IDE has its own place to add servers, but they share one JSON shape with a top-level servers object. If you are on Copilot Business or Enterprise, an admin must first turn on the "MCP servers in Copilot" policy, which is off by default.

Copilot's cloud agent, the one that works on issues in GitHub, uses a different setup: a JSON block in the repository's settings. This guide covers both.

Checked against: GitHub's Extending Copilot Chat with MCP and Extending the cloud agent with MCP docs on 2 November 2026. eSEOspace did not test Copilot for this guide.

Step 0: Check the policy (Business and Enterprise)

GitHub's docs say the "MCP servers in Copilot" policy applies to Copilot Business and Enterprise users whose organization or enterprise sets it, and that "the policy is disabled by default." If MCP options are missing in your IDE, ask an admin to enable it. Individual plans (Free, Pro, Pro+ and Max) are not governed by it.

GitHub also runs an MCP Registry, in public preview. Its docs say "only MCP servers listed in the GitHub MCP Registry can be added through the registry," and others must be configured by hand.

Setup by IDE

VS Code

VS Code's MCP setup changed in 2026. Microsoft's VS Code docs now steer personal servers to a "Copilot Global" file at ~/.copilot/mcp-config.json and labels .vscode/mcp.json deprecated in its guided flow. GitHub's page still shows the older .vscode/mcp.json route. Our VS Code mcp.json guide walks through both and explains the format differences.

Visual Studio

Use the "Configure MCP server" dialog, which edits an mcp.json file. For the remote GitHub MCP server, GitHub says to sign in with OAuth using the Auth CodeLens that appears above the server entry.

JetBrains, Xcode and Eclipse

In these IDEs, GitHub's examples use a personal access token in a header for the remote GitHub server:

{
  "servers": {
    "github": {
      "url": "https://api.githubcopilot.com/mcp/",
      "requestInit": {
        "headers": {
          "Authorization": "Bearer YOUR_PAT_HERE"
        }
      }
    }
  }
}

A local server uses command and args:

{
  "servers": {
    "memory": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-memory"]
    }
  }
}

Both blocks were checked against GitHub's docs on 2 November 2026. Note the key is servers, not the mcpServers used by Claude Desktop and Cursor. Our JetBrains MCP setup guide also covers JetBrains' own AI Assistant, which uses mcpServers.

Use a fine-grained token with the fewest permissions the work needs. Our GitHub MCP server profile lists its toolsets so you can scope it.

Copilot cloud agent

The cloud agent (GitHub's docs now call the coding agent "Copilot cloud agent") runs in GitHub, not your IDE. To add servers:

1. Open the repository's Settings.
2. In the "Code, planning, and automation" section, click Copilot, then MCP servers.
3. Paste a JSON configuration with a top-level mcpServers object.

Rules from GitHub's docs:

• Each server's type can be local, stdio, http or sse.
• A tools list is required. GitHub recommends allowlisting specific read-only tools; "*" enables all of them.
• Only secrets and variables named with the COPILOT_MCP_ prefix are available to the configuration.
• "The GitHub MCP server and Playwright MCP server are enabled by default." The GitHub server uses a token with read-only access to the current repository.
• The agent uses configured tools "autonomously," without asking for approval.
• Remote servers that use OAuth are not currently supported for the cloud agent.

Because the agent will not stop to ask, the tools list is your main safety control. Keep it to read-only tools unless a write tool is essential.

Verify a server works

In the IDE, switch Copilot Chat to agent mode, open the tools picker and check your server's tools are listed. Then ask for a task that needs one of them and expand the tool call to see the result. For the cloud agent, assign it a small issue and read its session log for the tool calls.

Common mistakes

• Missing MCP options on a company plan. The org policy is off by default.
• Using mcpServers in IDE config. Copilot's IDE examples use servers; the cloud agent uses mcpServers.
• A secret without the COPILOT_MCP_ prefix. The cloud agent cannot see it.
• "tools": ["*"] on a write-capable server. The cloud agent runs tools without approval.

Next step

Read Microsoft and MCP for how Copilot fits with Copilot Studio and Windows, and our Copilot Studio MCP setup if you build business agents. To compare editors, see Cursor vs VS Code for MCP.

Frequently asked questions