GitHub Enterprise MCP Server
Related Servers
Alternatives to GitHub Enterprise MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP (Model Context Protocol) server for GitHub API integration. This server provides comprehensive tools for interacting with GitHub repositories, issues, pull requests, branches, and code search through a unified interface.1512 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that wraps the GitHub CLI to provide comprehensive access to repository management, pull requests, issues, and workflows. It enables users to perform complex GitHub operations and interact with the GitHub API through a standardized interface.14 npm1ISC
- AlicenseNot gradedqualityDmaintenanceMCP server for the GitHub API, enabling file operations, repository management, search functionality, issues, pull requests, and more.64 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools for interacting with the GitHub API, enabling AI assistants to query repositories, pull requests, issues, commits, users, and more.379 npmISC
- AlicenseBqualityDmaintenanceAn MCP server that enables managing GitHub repositories, pull requests, issues, and more through natural language in Cursor or Claude Desktop.395 npm4MIT
- -licenseNot gradedqualityAmaintenanceMCP Server for the GitHub API, enabling file operations, repository management, search functionality, and more.88,163 npm90,629MIT
TDQS
Scored across 28 tools
Each tool targets a distinct resource-action combination, such as list-repositories vs get-repository vs create-repository. Even within the same resource, tools like get-issue, create-issue, and list-issues are clearly separated. No two tools appear to do the same thing.
All tool names follow a consistent kebab-case verb-noun pattern (e.g., list-issues, create-repository, suspend-user). The verbs are uniform and predictable, making the naming convention highly consistent across the entire set.
With 28 tools, the count is on the heavier side, but it covers a broad enterprise domain including repositories, issues, pull requests, workflows, users, and enterprise stats. Each tool seems justified for the scope, so the count is appropriate, though slightly above the typical well-scoped range.
The tool surface covers core CRUD for repositories and users, plus workflows and pull requests, but has notable gaps: no update-issue or delete-issue, no update/delete for pull requests, and no search capabilities. These missing operations will require agents to work around limitations in common workflows.