GitHub Enterprise MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_API_URL | No | GitHub API URL (defaults to https://api.github.com for GitHub.com, use your instance URL for GitHub Enterprise) | https://api.github.com |
| GITHUB_API_VERSION | No | GitHub API version to use (e.g. 2022-11-28) | |
| GITHUB_PERSONAL_ACCESS_TOKEN | Yes | GitHub Personal Access Token with appropriate permissions (repo scope for private repos, public_repo for public repos only) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-repositoriesC | Search for GitHub repositories |
| create-repositoryC | Create a new GitHub repository in your account |
| update-repositoryC | Update an existing GitHub repository |
| delete-repositoryC | Delete a GitHub repository |
| create-branchC | Create a new branch in a GitHub repository |
| list-commitsC | Get list of commits of a branch in a GitHub repository |
| list-workflowsC | List workflows in a GitHub repository |
| list-workflow-runsC | List workflow runs in a GitHub repository |
| trigger-workflowC | Trigger a workflow run in a GitHub repository |
| create-or-update-fileC | Create or update a single file in a GitHub repository |
| push-filesC | Push multiple files to a GitHub repository in a single commit |
| get-file-contentsC | Get the contents of a file or directory from a GitHub repository |
| fork-repositoryB | Fork a GitHub repository to your account or specified organization |
| list-issuesC | List and filter repository issues |
| get-issueB | Get details of a specific issue in a GitHub repository. |
| create-issueC | Create a new issue in a GitHub repository |
| update-issueC | Update an existing issue in a GitHub repository |
| add-issue-commentC | Add a comment to an existing issue |
| list-pull-requestsC | List and filter repository pull requests |
| get-pull-requestC | Get details of a specific pull request |
| create-pull-requestC | Create a new pull request in a GitHub repository |
| create-pull-request-reviewC | Create a review on a pull request |
| merge-pull-requestC | Merge a pull request |
| get-pull-request-filesB | Get the list of files changed in a pull request |
| get-pull-request-statusB | Get the combined status of all status checks for a pull request |
| update-pull-request-branchC | Update a pull request branch with the latest changes from the base branch |
| get-pull-request-commentsC | Get the review comments on a pull request |
| get-pull-request-reviewsC | Get the reviews on a pull request |
| search-codeC | Search for code across GitHub repositories |
| search-issuesC | Search for issues and pull requests across GitHub repositories |
| search-usersC | Search for users on GitHub |
| get-license-infoB | Get information about commonly used licenses on GitHub |
| get-enterprise-statsB | Get GitHub Enterprise statistics (only available for GitHub Enterprise) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 33 tools
Every tool has a clearly distinct purpose targeting specific GitHub resources and actions. There is no overlap or ambiguity—tools like 'get-pull-request-comments' and 'get-pull-request-reviews' are clearly differentiated, and operations like 'create-issue' vs 'update-issue' are well-separated.
All tools follow a consistent verb_noun pattern with hyphens (e.g., 'create-branch', 'list-issues', 'get-file-contents'). The naming is predictable and uniform across all 33 tools, making them easily readable and parsable.
With 33 tools, the count is borderline high for a typical MCP server scope, which often ranges from 3-15 tools. While GitHub Enterprise is a broad domain, this many tools might feel heavy and could overwhelm agents, though it's not extreme.
The toolset provides comprehensive CRUD and lifecycle coverage for GitHub operations, including repositories, issues, pull requests, files, workflows, and searches. There are no obvious gaps—core workflows are fully supported with no dead ends.