GitHub MCP Server

@tomo-cps

Repository

Basic information

About GitHub MCP Server

GitHub MCP Server implementation and testing repository

#mcp #github #server #api

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?

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

Frequently asked questions

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.

Comments

More Version Control MCP servers

Atlassian Jira MCP Server

aashari

Node.js/TypeScript MCP server for Atlassian Jira. Equips AI systems (LLMs) with tools to list/get projects, search/get issues (using JQL/ID), and view dev info (commits, PRs). Connects AI capabilities directly into Jira project management and issue tracking workflows.

GitLab MCP Server

yoda-digital

Production-grade GitLab MCP server with 86 tools — full GitLab control from any AI agent (Claude, Cursor, Zed).

GitLab

modelcontextprotocol

Model Context Protocol Servers

88.1K

GitHub MCP Server Extension for Zed

LoamStudios

A GitHub MCP Server extension for Zed

AIO-MCP Server

athapong

🚀 All-in-one MCP server with AI search, RAG, and multi-service integrations (GitLab/Jira/Confluence/YouTube) for AI-enhanced development workflows. Folk from https://github.com/nguyenvanduocit/all-in-one-model-context-protocol