Claude Code and GitHub MCP: setup and permissions

Learn to connect Claude Code 2.1.1+ to GitHub over HTTP, scope a token to one repository, and fix an issue-comment permission error.

Player not loading? Watch on YouTube

This tutorial connects Claude Code to GitHub's official MCP server so the coding assistant can read repository data and write issues from the terminal. The setup requires Claude Code 2.1.1 or newer and a GitHub personal access token. It uses the remote server over HTTP; this is a network-dependent workflow, not an offline setup.

The speaker recommends a fine-grained token scoped to one repository, with permissions for contents, issues, pull requests and metadata. The walkthrough adds the server with a JSON configuration containing the token, then checks registration with Claude's MCP list command.

The examples ask Claude to summarize five recent commits, prioritize three open issues, and create an issue with a title, body and enhancement label. The speaker explains that Claude reads the remote repository through MCP rather than the local checkout. A later comment request fails because the token has only read access to issues. The walkthrough changes that permission and obtains organization-owner approval before retrying successfully.

The closing advice is to treat the token like a password, keep it out of commits and chats, set a 90-day expiration, and revoke it promptly if it leaks. The speaker also recommends rotation when a teammate leaves. GitHub availability remains a dependency, so the tutorial advises keeping a local backup workflow for critical work.