GitHub MCP server in VS Code (Copilot) first-party on both ends.
VS Code's Copilot agent and the GitHub MCP Server are built by the same company, and it shows: OAuth sign-in instead of token pasting, and a one-line mcp.json entry.
This is the smoothest pairing in the MCP ecosystem. GitHub builds the server (github/github-mcp-server, 30.6k stars), Microsoft and GitHub build the client, and the integration uses your existing GitHub sign-in — no personal access token required for the basic setup.
Copilot's agent mode gains repo management, issue triage, PR workflows, and Actions visibility. Setup is one JSON entry or one Command Palette command.
Two ways in: command or file
Fastest path: open the Command Palette and run MCP: Add Server, choose HTTP, and paste the endpoint URL. VS Code writes the config for you — into your user-level mcp.json if you pick global, or .vscode/mcp.json if you scope it to the workspace.
If you prefer editing files (or want to commit the config so your whole team gets it), create .vscode/mcp.json in the repo yourself. Note that VS Code's key is servers, not the mcpServers key most other clients use:
{
"servers": {
"github": {
"type": "http",
"url": "https://api.githubcopilot.com/mcp/"
}
}
}Auth is OAuth, not a pasted token
No Authorization header needed here. When the server first starts, VS Code prompts you to authorize via GitHub's OAuth flow using the account you're already signed into for Copilot. That's a meaningful security upgrade over PAT-in-a-config-file: no plaintext secret on disk, and revocation happens from your GitHub account's authorized apps page.
The tools then act as you — they can touch whatever repos your account can, so the usual judgment about letting an agent write to production repos still applies.
Start the server and confirm tools
After saving the config, a Start link appears above the server entry in the JSON editor — click it, or run MCP: List Servers and start it from there. Open Copilot Chat in agent mode and click the tools icon: the github server should be listed with its tools toggled on.
Try "list the open issues in this repo assigned to me." An inline tool call with live results confirms the OAuth grant and the connection. The server's complete tool inventory is also published on its Loomal listing at https://loomal.ai/marketplace/github.
Troubleshooting in VS Code
Server won't start: run MCP: List Servers, select github, and choose Show Output — each MCP server gets its own Output channel where handshake and auth errors are printed plainly. Re-run the OAuth prompt if you dismissed it the first time.
Tools missing from agent mode: confirm you're in agent mode rather than ask mode, and that the server's tools are enabled in the tools picker. If you committed .vscode/mcp.json, teammates need to trust the workspace before VS Code will start its servers.
Key-name mistakes are common when migrating configs from Cursor or Claude Desktop: VS Code wants servers with a type field, and silently ignores an mcpServers block.
FAQ
How do I add the GitHub MCP server to VS Code Copilot?
Run MCP: Add Server from the Command Palette and paste https://api.githubcopilot.com/mcp/ as an HTTP server, or add it to .vscode/mcp.json under the servers key. Start the server, complete the OAuth prompt, and the tools appear in agent mode.
Do I need a personal access token?
Not for the standard setup — VS Code authenticates the remote GitHub server through OAuth with your signed-in GitHub account. PATs are only relevant if you self-host the server's Docker image or need to act as a different identity.
Why doesn't VS Code see my mcpServers config block?
VS Code uses a different schema from most MCP clients: the top-level key is servers, and each entry needs a type (http for this server). Configs copied from Cursor or Claude Desktop with an mcpServers key are ignored without an error.
Where are the MCP logs in VS Code?
Each server gets its own Output channel. Run MCP: List Servers, pick the server, and choose Show Output to see startup, OAuth, and per-call errors. It's the first place to look when tools silently fail.
More MCP servers for VS Code.
Every Loomal listing includes a live-probed tool list.