GitHub Repos Manager MCP Server

What it is

A server that talks to the GitHub API directly — no container, no command-line GitHub client — and exposes a broad tool surface across repositories, issues, pull requests, files, settings, search and organizations.

What you get

• Repositories — list_repos with filtering and sorting, get_repo_info, search_repos, get_repo_contents at any branch or commit, and set_default_repo so you stop repeating owner and repo
• Issues — list_issues, create_issue with images, labels and assignees, plus comment, label, assignee, lock and state management
• Pull requests — create_pull_request, edit_pull_request, get_pr_details, list_pr_files, list_pr_reviews and create_pr_review
• Files — create_file, update_file, upload_file for binaries and delete_file, each with its own commit message
• Repository settings — deploy keys, webhooks and Actions secrets listed, created, edited and removed
• Insights — get_repo_stats, get_repo_languages, list_stargazers, list_watchers, list_forks, repository topics, and traffic data where your access allows it
• Search across GitHub — search_issues, search_commits, search_code, search_users and search_topics
• Organizations — list_org_repos, list_org_members, get_org_info, list_org_teams, get_team_members and manage_team_repos
• Scoping — restrict the server to named repositories or whole owners, and enable or disable individual tools

Requirements

A GitHub personal access token carrying the scopes your work needs: repository access, permission to read profile data, and organization read if you touch organizations. Runs under Node with nothing else to install.

Setup effort

One command plus a key — npx -y github-repos-manager-mcp, then supply credentials

Tools you get

84 tools named in the project's documentation.

Requires

• npx on PATH
• GH_TOKEN in your environment