Universal GitHub MCP Server
Related Servers
Alternatives to Universal GitHub MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceA production-ready MCP server for GitHub operations, providing tools for repository management, issues, pull requests, and more via both MCP stdio and REST API.27MIT
- FlicenseNot gradedqualityDmaintenanceStandalone MCP server for GitHub that enables repository management, branch operations, pull request handling, and commit retrieval via tools listed in the README.1-
- FlicenseNot gradedqualityDmaintenanceMCP server for GitHub operations, providing tools for repository management, issues, pull requests, and code search.-
- AlicenseBqualityDmaintenanceA modular MCP server that provides a unified interface for interacting with GitHub and GitLab, including enterprise and self-hosted instances. It enables comprehensive management of repositories, issues, pull requests, and CI/CD pipelines through natural language.2329 npmMIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables Git repository operations and GitHub PR workflows, allowing users to manage repositories, create branches, commit changes, and create pull requests through natural language.2-
- AlicenseNot gradedqualityDmaintenanceMCP server for the GitHub API, enabling file operations, repository management, search functionality, issues, pull requests, and more.78 npmMIT
TDQS
Scored across 3 tools
The three tools are distinct in their domains: WordPress CLI, GitHub API, and documentation. There is no overlap between them, so an agent is unlikely to confuse one for another, though the GitHub tool is broadly scoped.
All tool names are lowercase single nouns, but they do not follow a verb-noun or consistent action-based pattern. 'wpcli' is a compound name, 'github' is a platform name, and 'docs' is an abbreviation, which feels ad hoc rather than systematic.
Three tools is within the acceptable range and not excessive. However, the server is named 'Universal GitHub MCP Server' yet includes a WordPress tool and a docs tool, making the count feel both under-scoped for GitHub and over-inclusive for the stated purpose.
For a GitHub-oriented server, there is only one vague 'github' tool with no explicit CRUD or workflow operations visible. The other two tools address unrelated domains, leaving major gaps in GitHub functionality that would likely cause agent failures.