GitHub MCP Server

What is GitHub MCP Server?

GitHub MCP Server is an implementation of the Model Context Protocol (MCP) that integrates with the GitHub API. It enables LLM agents to perform repository operations, code search, and issue/PR management through standardized endpoints.

How to use GitHub MCP Server?

Install by cloning the repository, installing dependencies (npm install or yarn install), and creating a .env file with your GitHub Personal Access Token and port. Start the server with npm run dev (development) or npm start (production). Then send HTTP POST requests to http://localhost:3000/mcp/execute with a JSON body containing a command and params object.

Key features of GitHub MCP Server

• Repository operations: create, edit files, manage branches
• Code search across GitHub
• Issue and pull request creation, update, and comments
• Secure authentication via GitHub Personal Access Token

Use cases of GitHub MCP Server

• Retrieve repository information (owner, repo) for analysis
• Create issues with labels and descriptions from LLM commands
• Search code across public repositories
• Manage pull requests and merge workflows programmatically

FAQ from GitHub MCP Server

What does GitHub MCP Server do compared to using the GitHub API directly?

It provides a standardized MCP interface that LLM agents can use via simple JSON commands, abstracting away raw API calls and authentication details.

What are the dependencies and runtime requirements?

Node.js version 16.0.0 or higher, npm or yarn, and a GitHub Personal Access Token with appropriate scopes (repo, user, read:org recommended).

Where does user data live?

Data is not persisted on the server; it is fetched from the GitHub API per request and returned directly to the client. The server runs locally on your machine.

Are there any known limits?

GitHub API rate limits apply. If the limit is reached, wait before retrying. CORS errors may occur during cross-origin calls; ensure the server sets proper CORS headers.

What transport and authentication does the server use?

The server uses HTTP transport. Authentication is handled via a GitHub Personal Access Token stored in the GITHUB_TOKEN environment variable.