Loading...

An MCP server providing access to GitHub Enterprise resources like repositories, issues, and pull requests, enabling automation and integration with AI tools.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
An MCP server providing access to GitHub Enterprise resources like repositories, issues, and pull requests, enabling automation and integration with AI tools.
This MCP server offers a range of tools, from safe read-only operations to potentially destructive actions like repository deletion. It is safe to use for information retrieval and monitoring when configured with appropriate PAT scopes. However, caution is advised when using tools that modify or delete resources, as there are limited safeguards against unintended consequences.
Performance depends on the size of the repository and the complexity of the queries. Consider optimizing queries and caching results to improve performance.
Cost is primarily related to GitHub Enterprise API usage. Be mindful of API rate limits and potential charges for exceeding usage quotas.
npx @ddukbg/github-enterprise-mcp --token=your_github_token --github-enterprise-url=https://github.your-company.com/api/v3{
"mcpServers": {
"github-enterprise": {
"command": "npx",
"args": ["-y", "@ddukbg/github-enterprise-mcp", "--token=YOUR_GITHUB_TOKEN", "--github-enterprise-url=YOUR_GITHUB_ENTERPRISE_URL"]
}
}
}GITHUB_TOKENGITHUB_ENTERPRISE_URLlist-repositoriesRetrieves a list of repositories for a given user or organization.
Read-only operation, no modifications.
get-repositoryGets detailed information about a specific repository.
Read-only operation, no modifications.
list-branchesLists the branches of a specified repository.
Read-only operation, no modifications.
get-contentRetrieves the content of a file or directory within a repository.
Read-only operation, no modifications.
list-pull-requestsLists pull requests in a repository based on specified criteria.
Read-only operation, no modifications.
get-pull-requestGets details for a specific pull request.
Read-only operation, no modifications.
create-pull-requestCreates a new pull request in a repository.
Creates a new pull request, but doesn't directly modify existing code.
merge-pull-requestMerges a pull request into the base branch.
Modifies the repository's code by merging a pull request.
list-issuesLists issues in a repository based on specified criteria.
Read-only operation, no modifications.
get-issueGets details for a specific issue.
Read-only operation, no modifications.
list-issue-commentsLists comments on a specific issue or pull request.
Read-only operation, no modifications.
create-issueCreates a new issue in a repository.
Creates a new issue, but doesn't directly modify existing code.
create-repositoryCreates a new repository on GitHub Enterprise.
Creates a new repository, which can have significant impact.
update-repositoryUpdates the settings of an existing repository.
Modifies repository settings, potentially impacting access and functionality.
delete-repositoryDeletes a repository from GitHub Enterprise.
Deletes a repository, resulting in permanent data loss.
list-workflowsLists GitHub Actions workflows in a repository.
Read-only operation, no modifications.
list-workflow-runsLists workflow runs for a specific workflow.
Read-only operation, no modifications.
Token
cloud
repodelete_repoactions:readThis MCP server offers a range of tools, from safe read-only operations to potentially destructive actions like repository deletion. It is safe to use for information retrieval and monitoring when configured with appropriate PAT scopes. However, caution is advised when using tools that modify or delete resources, as there are limited safeguards against unintended consequences.
The level of autonomy depends on the tool being used and the permissions granted to the PAT. Exercise caution when using tools that modify or delete resources.
Production Tip
Monitor API usage to avoid rate limiting and implement robust error handling to gracefully handle failures.
The required permissions depend on the tools being used. Refer to the table in the documentation for details.
You can configure the language using the LANGUAGE environment variable or the --language command-line argument.
Set the DEBUG environment variable to true or use the --debug command-line argument.
The recommended approach is to use URL mode, as it is the most stable and reliable.
Yes, but some enterprise-specific features will not work.
Monitor API usage and implement retry logic with exponential backoff.
The server will likely default to GitHub.com, but it's best to explicitly set the URL for clarity.