$ loading_
Manage GitHub repositories, labels, topics, and files through API automation.
This is an open-source MIT-licensed third-party MCP server that claims to manage GitHub repositories via GitHub APIs and perform file-related operations. No keys or fixed remote endpoints are declared, but its stated functionality inherently implies repository data read/write and local execution capability; with no README and unknown maintenance, the overall posture is caution rather than high risk.
The materials state there are no required keys/environment variables, but the claimed functionality—managing repositories through GitHub REST/GraphQL APIs—would typically require GitHub credentials in practice. The docs do not explain authentication method, permission scope, or credential storage, creating normal credential configuration and over-scoping concerns.
The description explicitly says it works through GitHub REST and GraphQL APIs, implying outbound transmission of repository, file, label, and related operation data to GitHub endpoints. There is no evidence of unrelated third-party exfiltration or unknown endpoints, but the specific hosts are not listed, so network transparency is limited.
The system flags executes-code, meaning this MCP can execute code or processes locally. That is a common capability for this class of tools, but the materials do not define execution boundaries, allowed commands, or sandboxing limits, so the runtime environment should be constrained.
It claims to support repository CRUD and file operations, indicating the ability to read, modify, create, or delete repository contents and related metadata. There is no sign of requesting system-level data access beyond the stated purpose, but the write capability over GitHub resources is inherently powerful and should be limited to the minimum repository scope.
Positive signals include public source code and an MIT license, which make it auditable. However, it comes from a third-party registry, has 0 GitHub stars, unknown maintenance status, and no README, which reduce verifiability and maturity. No explicit malicious red flags are shown, so the proper rating is caution.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "github-repo-manager-mcp" yet — see the docs or source repo.
Connect to GitHub, inspect the existing labels in my repository org-name/project-alpha, and add the labels bug, enhancement, and help wanted; skip any that already exist and return a summary of changes.
A summary of label inspection and creation results, including existing, created, and failed items.
Create a private repository named ai-toolkit-demo under my GitHub account, add the topics ai, mcp, and demo, and create a README.md with a project overview, installation steps, and usage examples.
Confirmation of repository creation, topic configuration, and successful README file creation.
Open .github/ISSUE_TEMPLATE/bug_report.yml in the repository org-name/service-api. If it exists, change the title to Bug Report and add a reproduction steps field; if it does not exist, create it with a standard template.
A report showing whether the file existed, whether it was updated or created, and a summary of the final written content.
Manage GitHub repositories, pull requests, issues, and workflows with natural language.
Manage GitHub repositories, files, and user profiles through MCP actions.
Manage GitHub repos, issues, PRs, code search, and CI status in one place.
Manage GitHub repositories, branches, pull requests, and commits through an MCP server.
Use natural language to manage GitHub repos, issues, commits, and workflows.
Lets AI call the GitHub API to manage repos, issues, and pull requests.