MCP.so
Sign In

GitHub Repos Manager MCP Server

@kurdin

About GitHub Repos Manager MCP Server

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.

Basic information

Category

Version Control

Runtime

node

Transports

stdio

Publisher

kurdin

Config

Add this server to your MCP-compatible client using the configuration below.

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

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is GitHub Repos Manager MCP Server?

A Model Context Protocol server that enables MCP clients (Claude Desktop, Roo Code, Cline, Cursor, Windsurf, etc.) to interact with GitHub repositories using a GitHub personal access token. It provides 89 tools for repository, issue, pull request, branch, commit, and collaboration management, with direct API integration and no Docker requirement.

How to use GitHub Repos Manager MCP Server?

Install Node.js 18+ and generate a GitHub Personal Access Token with repo and user:read scopes. Run via npx -y github-repos-manager-mcp or clone and run locally. Configure your MCP client with the server command and the GH_TOKEN environment variable. Optional environment variables include GH_DEFAULT_OWNER, GH_DEFAULT_REPO, GH_ALLOWED_REPOS, and GH_DISABLED_TOOLS.

Key features of GitHub Repos Manager MCP Server

  • 89 tools with direct GitHub API integration
  • Token-based authentication, no Docker needed
  • Restrict operations to specific repositories or owners
  • Enable/disable individual tools for fine‑grained control
  • Branch creation, commit history, and diff comparison
  • Upload and embed images directly in issues

Use cases of GitHub Repos Manager MCP Server

  • Automate issue creation, labeling, and assignment in a repository
  • Explore and compare commit history across branches or tags
  • Manage repository collaborators and their access permissions
  • Upload local images to GitHub and embed them in issues
  • Set a default repository to streamline repeated commands

FAQ from GitHub Repos Manager MCP Server

What are the prerequisites?

Node.js version 18 or higher and a GitHub Personal Access Token with repo, user:read, and optionally read:org scopes.

How does it compare to other GitHub MCP servers?

It uses token‑based access (no Docker), offers 89 tools with direct API integration, and provides flexible configuration like allowed repositories and tool enable/disable.

How do I restrict which repositories the server can access?

Set the GH_ALLOWED_REPOS environment variable with a comma‑separated list of full repo paths (owner/repo) or just owner names.

Can I disable specific tools?

Yes, use the GH_DISABLED_TOOLS environment variable or --disabled-tools command line argument to disable tools you don’t need.

How is rate limiting handled?

The server includes built‑in GitHub API rate limit management.

Comments

More Version Control MCP servers