MCP GitHub Server

What is MCP GitHub Server?

It is a server for working with the GitHub API, providing a REST interface for interacting with GitHub repositories. It is intended for developers who need to manage repositories, files, branches, and commits programmatically.

How to use MCP GitHub Server?

Clone the repository, run npm install, create a .env file with PORT and GITHUB_TOKEN, then run npm run dev for development or npm start for production. Interact via the documented REST API endpoints.

Key features of MCP GitHub Server

• List and retrieve details of user repositories
• Create new repositories with name, description, and privacy
• Read and create files in a repository
• List and create branches
• List commits with filtering and create commits with multiple file changes

Use cases of MCP GitHub Server

• Automating repository creation and management across GitHub accounts
• Programmatically writing and updating files in repositories
• Creating branches and commits as part of CI/CD workflows
• Integrating GitHub operations into external applications or scripts

FAQ from MCP GitHub Server

What authentication is required?

A GitHub personal access token is required, set as GITHUB_TOKEN in the .env file. Recommended scopes are repo and user.

How do I obtain a GitHub token?

Go to your GitHub account settings, select "Developer settings" -> "Personal access tokens" -> "Tokens (classic)", click "Generate new token", choose the required permissions, and copy the token into your .env file.

What runtime dependencies does the server need?

Node.js and npm. Dependencies are installed via npm install.

What transport does the server use?

The server runs over HTTP on the configured PORT (default 3000).

Are there any known limits?

The README does not mention specific server limits; it relies on GitHub’s own API rate limits.