GitHub Repos Manager MCP Server is a comprehensive Model Context Protocol (MCP) server built with Node.js that enables MCP clients (such as Claude Desktop, Roo Code, Cline, Cursor, Windsurf, etc.) to interact with GitHub repositories through a GitHub personal access token (PAT). Its core design philosophy is to simplify setup, improve efficiency, and enhance control. It requires no Docker and directly integrates with the GitHub API, providing 89 tools to cover the complete GitHub workflow.
Main capabilities include:
- Repository management: intelligently list repositories (filter by visibility, sort), get detailed information, browse files and directories, search repositories site-wide, set a default repository.
- Issue management: create, edit, and list issues; manage status, labels, and assignees; support image upload embedding, comment system, and locking/unlocking issues.
- Pull request management: create and edit PRs, get details, list reviews and file changes, submit reviews (approve/request changes/comment).
- Branch and commit management: list branches, create branches, view commit history (filter by date, author, branch), get commit details, compare any two commits/branches/tags.
- Collaboration and user management: get user profiles, manage repository collaborator permissions, team collaboration tools.
- File and content management: create and update files, upload local files (binary supported).
- Advanced features: image upload and embedding, batch operations, flexible token authentication, intelligent error handling.
Usage:
- Prepare Node.js (version 18 or higher) and a GitHub personal access token (at least repo permission is required; optionally user:read or user:email to read user profiles, read:org to access organization information).
- Run the server directly via npx (no installation required), or clone the repository locally and run server.cjs after installing dependencies.
- Specify the server path and GH_TOKEN environment variable in the MCP client configuration. The server will start automatically.
- Optional configuration: set the default repository via environment variables or command-line arguments (GH_DEFAULT_OWNER, GH_DEFAULT_REPO or --default-owner, --default-repo), or use set_default_repo tool to set it in the conversation.
- Security control: use GH_ALLOWED_REPOS or --allowed-repos to restrict accessible repositories (format is owner/repo or just owner); use GH_DISABLED_TOOLS or --disabled-tools to disable specific tools; use GH_ALLOWED_TOOLS or --allowed-tools to allow only specific tools (if both are set, GH_ALLOWED_TOOLS takes precedence).
Use cases: suitable for developers and teams that need to automate GitHub repository management, especially workflows that execute GitHub operations through natural language instructions in MCP clients, such as batch issue processing, PR review, code commits, repository monitoring, etc.
Limitations: requires a GitHub personal access token; some operations are subject to GitHub API rate limits; there are many tools, and the access scope can be controlled through configuration; no specific pricing or fee information is mentioned.
