GitHub MCP Server

What is GitHub MCP Server?

A Go-based MCP server that connects GitHub to Claude Desktop, enabling direct repository operations such as listing repos, creating issues, and managing pull requests from Claude’s interface.

How to use GitHub MCP Server?

Install dependencies with go mod tidy, compile the server with go build -o github-mcp.exe main.go, generate a GitHub Personal Access Token with at least the repo scope, set the GITHUB_TOKEN environment variable in the Claude Desktop configuration file (claude_desktop_config.json), and restart Claude Desktop.

Key features of GitHub MCP Server

• List repositories of the authenticated user
• Create new repositories
• Get repository information
• List branches of a repository
• List and create pull requests
• List and create issues

Use cases of GitHub MCP Server

• Manage GitHub repositories directly from Claude Desktop conversations
• Automate issue and PR creation without leaving the chat interface
• Retrieve repository metadata and branch information on demand

FAQ from GitHub MCP Server

What permissions does my GitHub token need for all functions to work?

At minimum, the token requires the repo scope (full control of private repositories). For delete operations or workflow/webhook management, additional scopes like delete_repo, workflow, and admin:repo_hook are needed.

Why do I get a 403 error “Resource not accessible by personal access token”?

Your token does not have sufficient permissions. Generate a new token with the repo scope and restart Claude Desktop after updating the configuration.

Why do I get “null” responses from some tools?

For repositories that are empty or have no PRs/issues, “null” is expected behavior and indicates the MCP server is functioning correctly.