Data as of
GitHub MCP Server for VS Code: Setup & Config
GitHub MCP Server connects VS Code to repository content, issues, pull requests, and platform workflows.
GitHub MCP Server VS Code configuration
Choose VS Code configuration scope
For GitHub MCP Server, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.
Add GitHub MCP Server to VS Code
Use the github-mcp-server entry below in servers. Keep GitHub MCP Server's documented stdio connection fields and your other VS Code entries.
Check GitHub MCP Server in VS Code
GitHub MCP Server: Start in VS Code’s MCP controls; inspect output and trust prompts.
Config file · Workspace: .vscode/mcp.json
{
"servers": {
"github-mcp-server": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GITHUB_PERSONAL_ACCESS_TOKEN",
"ghcr.io/github/github-mcp-server"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "<your GitHub personal access token with appropriate permissions>"
}
}
}
}GitHub in VS Code: stdio checks
- Make docker and a running Docker engine available in the workspace, container, or remote environment hosting GitHub MCP Server. Start through VS Code's MCP controls; inspect output and trust prompts.
- For GitHub MCP Server, keep GITHUB_PERSONAL_ACCESS_TOKEN out of version control; VS Code documents input variables and secret handling.
- GitHub MCP Server uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
GitHub MCP Server — details. VS Code guide
Frequently asked questions
For GitHub MCP Server, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.
VS Code's github-mcp-server example uses stdio.
GitHub MCP Server's VS Code configuration invokes docker and a running Docker engine.
VS Code's GitHub MCP Server example references GITHUB_PERSONAL_ACCESS_TOKEN. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.