GitHub MCP
Enables self-hosted, read-only remote interaction with GitHub repositories, allowing listing repositories, searching code, and inspecting commits, pull requests, issues, and diffs via authenticated MCP clients.
README
GitHub MCP
A generic, read-only remote MCP connector for querying GitHub repositories selected through a GitHub App installation. It is designed for self-hosting and contains no GitHub, Cloudflare, or MCP-client account identifiers.
The connector uses two authorization layers:
- A user authorizes the GitHub App to prove their GitHub identity. Only operator-configured logins may finish connecting.
- Tool calls use short-lived GitHub App installation tokens restricted to the requested installed repository.
The GitHub user token is discarded after identity verification. The connector exposes no write tools.
Capabilities
- Discover repositories selected in GitHub App installations.
- Search code and retrieve text files or directory listings.
- Inspect commits, pull requests, diffs, reviews, and comments.
- Inspect issues and issue comments.
- Authenticate remote MCP clients using OAuth, PKCE, and Dynamic Client Registration.
Local development
Requirements: Node 22 or newer and Yarn 1.22.
yarn install
yarn type-check
yarn lint
yarn test
yarn build
Tests use fake identities and mocked GitHub services. No GitHub App or Cloudflare account is needed for local verification.
To run the Worker against real services, follow the operator setup guide. Do not commit wrangler.jsonc, local secrets, or GitHub App private keys.
MCP tools
| Tool | Purpose |
|---|---|
list_repositories |
List repositories selected in the app's installations. |
search_code |
Search within one installed repository. |
list_directory |
List one repository directory at a ref. |
get_file |
Retrieve a UTF-8 text file, optionally by line range. |
list_commits / get_commit |
Inspect repository history. |
list_pull_requests / get_pull_request |
Inspect pull requests, files, reviews, and comments. |
get_pull_request_diff |
Retrieve a pull request's unified diff. |
list_issues / get_issue |
Inspect issues and comments. |
Results are live GitHub API responses, normalized into bounded JSON with canonical GitHub URLs. Pagination defaults to 20 items and caps at 50. Text and diff output caps at 100,000 characters.
Security model
AUTHORIZED_GITHUB_LOGINSis mandatory and fails closed when empty.- GitHub App installations determine which repositories exist to the connector.
- Each repository tool call mints a one-hour token restricted to that repository.
- Required GitHub App permissions are read-only Metadata, Contents, Issues, and Pull Requests.
- OAuth codes, user tokens, installation tokens, client secrets, and private keys are never returned or intentionally logged.
This project is intended as a personal or small-team connector, not a hosted multi-tenant service.
License
This project is available under the MIT License.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.