MCP.so
Sign In

GitHub MCP Server

@MCP-Mirror

Basic information

Category

Version Control

Transports

stdio

Author

MCP-Mirror

About GitHub MCP Server

Mirror of

#github#mcp-server#git-integration

GitHub MCP Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

GitHub MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is GitHub MCP Server?

A Model Context Protocol (MCP) server that provides GitHub integration capabilities. It enables developers and AI assistants to interact with GitHub repositories through MCP tools, supporting repository management, file operations, and commit handling.

How to use GitHub MCP Server?

Install the package via npm (npm install @modelcontextprotocol/server-github), then add it to your MCP settings file (e.g., cline_mcp_settings.json) with the command node /path/to/dist/index.js and environment variables GITHUB_TOKEN_1 and GITHUB_OWNER_1. After configuration, the server exposes tools that can be invoked by an MCP client.

Key features of GitHub MCP Server

  • Account management and authentication
  • Repository creation and management
  • File operations (read, write, push, pull)
  • Commit operations (create, list)
  • Directory synchronization (two-way sync)
  • Repository comparison and diffing

Use cases of GitHub MCP Server

  • Automate repository creation and renaming in a CI/CD pipeline
  • Push local files to a GitHub repository from an AI assistant
  • Pull files from a GitHub repository to a local development environment
  • Synchronize directories between local and remote GitHub repositories
  • List or create commits with multiple file changes

Frequently asked questions

1

What authentication is required?

GitHub personal access tokens are required. Tokens are provided via environment variables `GITHUB_TOKEN_<N>` along with the corresponding GitHub username via `GITHUB_OWNER_<N>`.

2

Can I use multiple GitHub accounts?

Yes. Multiple accounts can be configured by incrementing the number N (e.g., `GITHUB_TOKEN_1`, `GITHUB_TOKEN_2`) and using the `list_accounts` and `select_account` tools to switch between them.

3

What operations are supported?

The server supports repository management (create, clone, rename), file operations (push, pull), directory sync, commit operations (create, list), and account management (list, select). Each operation has a specific tool with typed parameters.

4

What are the runtime requirements?

The server runs on Node.js. It is built with `npm install && npm run build` and is executed as a Node process.

5

Where do files and data reside?

File data resides both on GitHub (remote repositories) and locally (the machine where the server runs). The server interacts with local directories and pushes/pulls files to/from GitHub repositories.

Comments

More Version Control MCP servers