Skip to content
MCP Shelf

Pod to App: VS Code

How to install the GitHub MCP server in VS Code

By Sophie Filer · Updated 11 Nov 2026 · Steps checked against GitHub's own docs on 11 Nov 2026

The short answer

Click the Install in VS Code button in the GitHub MCP server README, or add the entry below to .vscode/mcp.json. VS Code 1.101 and later sign you in to GitHub with OAuth, so you do not need a token. Then switch Copilot Chat to Agent mode.

.vscode/mcp.json
{
  "servers": {
    "github": {
      "type": "http",
      "url": "https://api.githubcopilot.com/mcp/"
    }
  }
}
VS Code
1.101 or newer
Sign-in
OAuth, or a token
Used by
Copilot Chat in Agent mode
Price
Free server; Copilot needed

Before you start

  • VS Code 1.101 or later. That release added remote MCP servers with OAuth, which this setup depends on.
  • GitHub Copilot signed in inside VS Code, because MCP tools run through Copilot Chat in Agent mode.
  • If you work in a company organisation, any MCP policy it sets must allow the server. Ask an admin if tools stay greyed out.

Install it step by step

  1. Step 1: Open the GitHub MCP server README and press Install in VS Code (there is an Insiders button too). VS Code opens and asks you to confirm.
  2. Step 2: Or do it by hand: create .vscode/mcp.json in your workspace and paste the block at the top of this page. VS Code shows a small Start link above the entry.
  3. Step 3: Click Start. VS Code asks to sign in with GitHub; accept, and approve the GitHub app in the browser.
  4. Step 4: Open Copilot Chat and pick Agent from the mode menu next to the input box. The tools button lists GitHub tools.
  5. Step 5: Try: "Find the oldest open issue in this repository and draft a fix plan in the chat."

Prefer a token? Let VS Code prompt for it

If OAuth is blocked, or you want a token limited to a few repositories, keep the token out of the file. VS Code can ask for it once and store it securely, using an input variable:

.vscode/mcp.json
{
  "servers": {
    "github": {
      "type": "http",
      "url": "https://api.githubcopilot.com/mcp/",
      "headers": { "Authorization": "Bearer ${input:github_mcp_pat}" }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "github_mcp_pat",
      "description": "GitHub Personal Access Token",
      "password": true
    }
  ]
}

Make the token on GitHub's token page. Because the file only holds a placeholder, it is safe to commit and share with the team; each person types their own token the first time.

Workspace file or user settings

WhereWho gets GitHub tools
.vscode/mcp.json in the repoEveryone who opens this workspace, once they start the server
Your user MCP configuration (command palette: MCP: Open User Configuration)Only you, in every workspace

Trim the tool list

Copilot works better with fewer tools to choose from. You can untick GitHub tools in the chat's tools picker for a session, or ask the server for fewer from the start with headers such as "X-MCP-Toolsets": "repos,issues,pull_requests" and "X-MCP-Readonly": "true" next to the URL.

If it does not work

What you seeWhat to do
No Start link above the entryCheck the file is valid JSON and the key is servers. Then reload the window.
GitHub tools never show in chatSwitch to Agent mode. Ask and Edit modes do not call MCP tools.
The OAuth window never finishesUpdate to VS Code 1.101 or later, or use the token version above.
Tools are disabled with a policy messageYour organisation controls MCP access. An admin has to allow it.
It works locally but not with GitHub EnterprisePoint VS Code at your Enterprise host in its GitHub settings, as the README describes for OAuth with Enterprise.

MCP Shelf take

Is GitHub worth adding to VS Code?

In VS Code this is the smoothest GitHub MCP setup we have tested: one click, a GitHub sign-in you already trust, and no token to babysit. It makes Copilot's Agent mode much more useful for the chores around code, like reading an issue thread before you start, summarising review comments, or opening the pull request. The catch is that it lives inside Copilot, so you need a Copilot plan. Start with the default toolsets, add read-only while you try it, and commit the workspace file so the team gets the same setup.

Sophie Filer

Questions

Do I need a personal access token for the GitHub MCP server in VS Code?

No. On VS Code 1.101 or later the hosted server signs you in with OAuth. A token is only needed if OAuth is blocked or you want access limited to certain repositories.

Is "GitHub Copilot MCP" the same thing as the GitHub MCP server?

Mostly, yes. People search for it that way because the server is hosted at api.githubcopilot.com and is used through Copilot's Agent mode. It is GitHub's official open-source MCP server.

Why does VS Code ignore my GitHub MCP config?

Usually the top key is mcpServers copied from another app. VS Code expects servers. Also make sure you clicked Start and that Copilot Chat is in Agent mode.

Can my whole team share the setup?

Yes. Commit .vscode/mcp.json with the OAuth entry, or with the input-variable version if you use tokens. Nobody's credentials end up in the file.

Sources: the steps on this page are written in our own words from GitHub's own install docs, the README, remote-server.md. If they disagree with this page, the project's docs win; please tell us from the server page.