Manage GitHub Repositories and Issues
GitHub Repos Manager MCP Server: Manage GitHub repos, issues, and PRs with 89 tools. Install via NPX or source. Token auth, no Docker.
Maintainer of this project? Claim this page to edit the listing.
1.0.0Add to Favorites
Why it matters
Automate your GitHub repository management, issue tracking, and collaboration processes with a comprehensive MCP server. Interact with GitHub via a personal access token, streamlining your development lifecycle without Docker.
Outcomes
What it gets done
Create and manage pull requests with detailed lifecycle support.
Handle repository and branch management, including commit history.
Track and manage issues with rich content and image upload capabilities.
Configure fine-grained access control for repositories and tools.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-github-repos-manager-mcp-server | bash Capabilities
Tools your agent gets
Create a new pull request by specifying title, description, and branches
Update an existing pull request: title, description, status, or base branch
Retrieve detailed information about a pull request, including status
Set or change the default repository to simplify workflows
Overview
GitHub Repos Manager MCP Server
The GitHub Repos Manager MCP Server is a tool that provides 89 functionalities for managing GitHub repositories, issues, and pull requests. It allows for token-based authentication and does not require Docker. Key features include repository listing and filtering, advanced issue management with image uploads, and pull request lifecycle support. Use this server when you need to automate GitHub workflows, manage repositories programmatically, or integrate GitHub issue tracking and collaboration into an AI-driven application. It's suitable for developers who require fine-grained control over their GitHub interactions without manual intervention.
What it does
As a developer, I want to manage my GitHub repositories, issues, and pull requests programmatically so that I can automate my development workflow.
This MCP server provides 89 tools for comprehensive GitHub interaction, including repository management, issue tracking, and collaboration. It authenticates using a personal access token and does not require Docker. Installation can be done via NPX:
npx -y github-repos-manager-mcp
Or from source:
git clone https://github.com/kurdin/github-repos-manager.git
cd github-repos-manager
npm install
Configuration for Claude Desktop (macOS/Linux) using NPX:
{
"mcpServers": {
"github-repos-manager": {
"command": "npx",
"args": [
"-y",
"github-repos-manager-mcp"
],
"env": {
"GH_TOKEN": "ghp_YOUR_ACTUAL_TOKEN_HERE"
}
}
}
}
Key features include repository and issue management, pull request lifecycle support, branch and commit management, and fine-grained access control. Environment variables like GH_TOKEN are used for authentication.
Source README
A comprehensive MCP server for interacting with GitHub repositories through a personal access token, providing 89 tools for repository management, issue tracking, and collaboration without requiring Docker.
Installation
NPX
npx -y github-repos-manager-mcp
From Source
git clone https://github.com/kurdin/github-repos-manager.git
cd github-repos-manager
npm install
Configuration
Claude Desktop (NPX - macOS/Linux)
{
"mcpServers": {
"github-repos-manager": {
"command": "npx",
"args": [
"-y",
"github-repos-manager-mcp"
],
"env": {
"GH_TOKEN": "ghp_YOUR_ACTUAL_TOKEN_HERE"
}
}
}
}
Claude Desktop (NPX - Windows)
{
"mcpServers": {
"github-repos-manager": {
"command": "npx.cmd",
"args": [
"-y",
"github-repos-manager-mcp"
],
"env": {
"GH_TOKEN": "ghp_YOUR_ACTUAL_TOKEN_HERE"
}
}
}
}
Claude Desktop (Local Installation)
{
"mcpServers": {
"github-repos-manager": {
"command": "node",
"args": ["/full/path/to/your/project/github-repos-manager-mcp/server.cjs"],
"env": {
"GH_TOKEN": "ghp_YOUR_ACTUAL_TOKEN_HERE"
}
}
}
}
Available Tools
| Tool | Description |
|---|---|
create_pull_request |
Create a new pull request by specifying title, description, and branches |
edit_pull_request |
Update an existing pull request: title, description, status, or base branch |
get_pr_details |
Retrieve detailed information about a pull request, including status |
set_default_repo |
Set or change the default repository to simplify workflows |
Features
- 89 powerful tools for complete GitHub workflow management
- Token-based authentication without requiring Docker
- Repository management with intelligent listing and filtering
- Advanced issue management with rich content support and image uploads
- Pull request management with comprehensive lifecycle support
- Branch and commit management with history exploration
- Collaboration and user management tools
- Fine-grained access control with allowed repositories and tool management
- Default repository configuration to simplify workflows
- Built-in GitHub API rate limit handling
Environment Variables
Required
GH_TOKEN- GitHub personal access token for API authentication
Optional
GH_DEFAULT_OWNER- Default repository owner to simplify workflowsGH_DEFAULT_REPO- Default repository name to simplify workflowsGH_ALLOWED_REPOS- Comma-separated list of allowed repositories (owner/repo or owner)GH_DISABLED_TOOLS- Comma-separated list of disabled toolsGH_ALLOWED_TOOLS- Comma-separated list of allowed tools (takes priority over disabled tools)
Usage Examples
List issues for microsoft/vscode
Create a new issue with title and description
Set default repository to microsoft/vscode
List all branches with protection status
Upload and embed images directly in issues
Notes
Requires Node.js version 18 or higher. The GitHub personal access token must have 'repo', 'user:read' or 'user:email', and 'read:org' access permissions. The server provides comprehensive GitHub workflow management with 89 tools and supports fine-grained access control for security.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.