GitHub Repos Manager

GitHub Repos Manager MCP Server that enables your MCP client (e.g., Claude Desktop, Roo Code, etc.) to interact with GitHub repositories using your GitHub personal access token.
  • javascript

18

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "kurdin-github-repos-manager-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "github-repos-manager-mcp"
      ],
      "env": {
        "GH_TOKEN": "ghp_YOUR_ACTUAL_TOKEN_HERE"
      }
    }
  }
}

This MCP server lets your MCP clients control GitHub repositories through a token-based connection. It runs without Docker for simplicity and performance, and exposes a rich toolkit of GitHub operations via direct API calls. Use a single GitHub Personal Access Token to configure and operate the server from your MCP client, enabling streamlined repository management, issue handling, collaboration, and more.

How to use

You connect to the server from your MCP client (for example, Claude Desktop or other MCP-enabled assistants) using a token-based configuration. Provide your GitHub token in the client’s environment for authentication, or run the server locally and point the client to the local endpoint. Once connected, you can set a default repository to streamline commands, restrict access to specific repos, enable or disable individual tools, and perform a wide range of GitHub operations without leaving your MCP interface.

How to install

Prerequisites are minimal. You need Node.js version 18 or higher and a GitHub Personal Access Token (PAT) with appropriate scopes. The following options show how to run the server via MCP-friendly startup patterns.

# Quick start with npx (no installation required)
npx -y github-repos-manager-mcp

# Optional: run on Windows with npx.cmd
# npx.cmd -y github-repos-manager-mcp

# Or run locally after cloning
# 1) Clone the repository
# 2) Install dependencies
# 3) Run the server via Node
```} ,{

Configuration and usage notes

Configure the server through environment variables in your MCP client configuration. The token controls authentication, and you can optionally set a default repository, restrict access to specific repos, and limit tools. The examples below show common configurations you can adapt.

{
  "mcpServers": {
    "github-repos-manager": {
      "command": "npx",
      "args": ["-y", "github-repos-manager-mcp"],
      "env": {
        "GH_TOKEN": "ghp_YOUR_ACTUAL_TOKEN_HERE"
      }
    }
  }
}
```} ,{

Available MCP connection methods

You can connect using one of the supported startup methods shown here. Each method passes the necessary command and optional environment variables to the MCP client. If you prefer a local run, point your MCP client to the absolute path of server.cjs.

Example MCP server configurations

[
  {
    "type": "stdio",
    "name": "github_repos_mcp_npx_macos",
    "command": "npx",
    "args": ["-y", "github-repos-manager-mcp"],
    "env": {
      "GH_TOKEN": "ghp_YOUR_ACTUAL_TOKEN_HERE"
    }
  },
  {
    "type": "stdio",
    "name": "github_repos_mcp_npx_windows",
    "command": "npx.cmd",
    "args": ["-y", "github-repos-manager-mcp"],
    "env": {
      "GH_TOKEN": "ghp_YOUR_ACTUAL_TOKEN_HERE"
    }
  },
  {
    "type": "stdio",
    "name": "github_repos_mcp_local",
    "command": "node",
    "args": ["/full/path/to/your/project/github-repos-manager-mcp/server.cjs"],
    "env": {
      "GH_TOKEN": "ghp_YOUR_ACTUAL_TOKEN_HERE"
    }
  }
]
```}]} ,{

Security and access controls

To protect your workflows, you can restrict which repositories the server can access and control which tools are available. Use environment variables or runtime tool calls to enforce allowed repositories and tool permissions. For example, you can set a default repository and enable a curated set of tools to minimize risk.

Troubleshooting and tips

If you encounter authentication or permission issues, verify that your GH_TOKEN is correct and has the required scopes. Ensure the path to server.cjs is correct when using a local setup, and confirm that Node.js is version 18 or newer. If rate limits are hit, wait for the reset window or use a different token.

Usage scenarios

With the MCP server, you can discover repositories, manage issues, create pull requests, handle branches and commits, collaborate with team members, and perform advanced searches and analytics — all through your MCP client.

Available tools

create_pull_request

Create a new pull request with title, body, and branch specifications.

edit_pull_request

Update an existing pull request's title, body, state, or base branch.

get_pr_details

Get comprehensive information about a pull request including status and merge details.

list_prs

List pull requests with state filtering and pagination.

list_issues

List issues with filtering by state and comprehensive pagination.

create_issue

Create feature-rich issues with image uploads, labels, and assignees.

upload_file

Upload a local file to the repository (binary files supported).

list_repo_info

Get comprehensive information about a repository including stats and metadata.

list_branches

List all branches with protection status and commit information.

create_branch

Create a new branch from an existing branch or commit.

get_repo_stats

Get comprehensive repository statistics including contributor activity.

search_repos

Search for repositories across GitHub with advanced sorting options.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational