github-mcp-server

GitHub MCP Server Installation Guides

This directory contains detailed installation instructions for the GitHub MCP Server across different host applications and IDEs. Choose the guide that matches your development environment.

Installation Guides by Host Application

Support by Host Application

Host Application Local GitHub MCP Support Remote GitHub MCP Support Prerequisites Difficulty
Copilot in VS Code ✅ Full (OAuth + PAT) Local: Docker or Go build, GitHub PAT
Remote: VS Code 1.101+
Easy
Copilot Coding Agent ✅ Full (on by default; no auth needed) Any paid copilot license Default on
Copilot in Visual Studio ✅ Full (OAuth + PAT) Local: Docker or Go build, GitHub PAT
Remote: Visual Studio 17.14+
Easy
Copilot in JetBrains ✅ Full (OAuth + PAT) Local: Docker or Go build, GitHub PAT
Remote: JetBrains Copilot Extension v1.5.53+
Easy
Claude Code ✅ PAT + ❌ No OAuth GitHub MCP Server binary or remote URL, GitHub PAT Easy
Claude Desktop ✅ PAT + ❌ No OAuth Docker or Go build, GitHub PAT Moderate
Cursor ✅ PAT + ❌ No OAuth Docker or Go build, GitHub PAT Easy
Google Gemini CLI ✅ PAT + ❌ No OAuth Docker or Go build, GitHub PAT Easy
Windsurf ✅ PAT + ❌ No OAuth Docker or Go build, GitHub PAT Easy
Copilot in Xcode ✅ Full (OAuth + PAT) Local: Docker or Go build, GitHub PAT
Remote: Copilot for Xcode 0.41.0+
Easy
Copilot in Eclipse ✅ Full (OAuth + PAT) Local: Docker or Go build, GitHub PAT
Remote: Eclipse Plug-in for Copilot 0.10.0+
Easy

Legend:

Note: Remote MCP support requires host applications to register a GitHub App or OAuth app for OAuth flow support – even if the new OAuth spec is supported by that host app. Currently, only VS Code has full remote GitHub server support.

Installation Methods

The GitHub MCP Server can be installed using several methods. Docker is the most popular and recommended approach for most users, but alternatives are available depending on your needs:

📦 Pre-built Binary (Lightweight Alternative)

🔨 Build from Source (Advanced Users)

Important Notes on the GitHub MCP Server

General Prerequisites

All installations with Personal Access Tokens (PAT) require:

Optional (depending on installation method):

Security Best Practices

Regardless of which installation method you choose, follow these security guidelines:

  1. Secure Token Storage: Never commit your GitHub PAT to version control
  2. Limit Token Scope: Only grant necessary permissions to your GitHub PAT
  3. File Permissions: Restrict access to configuration files containing tokens
  4. Regular Rotation: Periodically rotate your GitHub Personal Access Tokens
  5. Environment Variables: Use environment variables when supported by your host

Getting Help

If you encounter issues:

  1. Check the troubleshooting section in your specific installation guide
  2. Verify your GitHub PAT has the required permissions
  3. Ensure Docker is running (for local installations)
  4. Review your host application’s logs for error messages
  5. Consult the main README.md for additional configuration options

Configuration Options

After installation, you may want to explore: