Connect an MCP server to GitHub Copilot

Copilot speaks MCP in two places: agent mode in VS Code, configured with a mcp.json file, and the Copilot coding agent on github.com, configured in repository settings. Same protocol, different config — this page covers both.

VS Code — where the config lives

The guided route is the MCP: Add Server command; MCP: List Servers shows what's connected. Or write the file directly — note the key is servers, not the mcpServers every other client uses:

{
  "servers": {
    "github": {
      "type": "http",
      "url": "https://api.githubcopilot.com/mcp"
    },
    "example": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@vendor/mcp-server"]
    }
  }
}

Remote servers (type: "http", or "sse" for older ones) trigger the vendor's OAuth sign-in when needed. Ready to paste right now: fal.ai, Atlassian, Datadog, Buffer, Google Drive, Confluence.

For secrets, use an input variable instead of hardcoding the key — the file stays committable:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "vendor-key",
      "description": "Vendor API key",
      "password": true
    }
  ],
  "servers": {
    "example": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@vendor/mcp-server"],
      "env": { "VENDOR_API_KEY": "${input:vendor-key}" }
    }
  }
}

Then open the Chat view, switch to Agent mode, and pick the server's tools from the tools icon. Copilot asks before running a tool unless you allow it for the session.

The Copilot coding agent — github.com

The autonomous agent that works on issues gets its MCP servers from repository settings, not from your editor: Settings → Copilot → Coding agent, in the MCP configuration section. The GitHub MCP server and Playwright are enabled by default; anything else is JSON with a required tools allowlist:

{
  "mcpServers": {
    "example": {
      "type": "http",
      "url": "https://mcp.example.com/mcp",
      "headers": { "Authorization": "Bearer $COPILOT_MCP_EXAMPLE_TOKEN" },
      "tools": ["search", "read_item"]
    }
  }
}

Secrets must be created as Copilot environment secrets with names prefixed COPILOT_MCP_ before the config can reference them. Local (type: "local") servers run with a command inside the agent's ephemeral environment. The explicit tools list is a real security boundary — the agent works unattended, so give it the narrowest set that does the job.

When it doesn't work

A word on trust

Copilot's approval prompts exist because MCP tools act with real credentials — and the coding agent acts unattended. Prefer official servers, scope every token, and keep coding-agent tool allowlists narrow. More in our MCP security guide.

Questions