piyushgIITian github enterprice mcp

WHAT IT CONNECTS

piyushgIITian github enterprice mcp 为 AI Agent 提供什么

• **Automatic Branch Creation**: When creating/updating files or pushing changes, branches are automatically created if they don't exist
• **Comprehensive Error Handling**: Clear error messages for common issues
• **Git History Preservation**: Operations maintain proper Git history without force pushing
• **Batch Operations**: Support for both single-file and multi-file operations
• **Advanced Search**: Support for searching code, issues/PRs, and users
• Node.js installed on your system
• A GitHub Personal Access Token with appropriate permissions
• Cline installed on your system
• Go to [GitHub Personal Access Tokens](https://github.com/settings/tokens) (in GitHub Settings > Developer settings)
• Click "Generate new token"
• Select which repositories you'd like this token to have access to (Public, All, or Select)
• Create a token with the `repo` scope ("Full control of private repositories")
• Alternatively, if working only with public repositories, select only the `public_repo` scope
• Copy the generated token
• Open VS Code
• Locate the Cline MCP settings file at:
• Windows: `%APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json`
• macOS: `~/Library/Application Support/claude-code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`
• Linux: `~/.config/claude-code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`
• Add the GitHub Enterprise MCP server configuration to the `mcpServers` object:
• Locate the Claude Desktop configuration file at:
• Windows: `%APPDATA%\Claude\claude_desktop_config.json`
• macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
• Linux: `~/.config/Claude/claude_desktop_config.json`
• Add the GitHub Enterprise MCP server configuration to the `mcpServers` object:
• First, explain what the GitHub Enterprise MCP server is and what capabilities it will give you.
• Guide me through the installation process:
• Help me clone the repository (if I haven't already)
• Help me install dependencies and build the project
• Guide me through creating a GitHub Personal Access Token if I don't have one
• Help me configure the MCP settings in either VS Code or Claude Desktop
• Verify the installation is working
• Show me some examples of how I can use the GitHub Enterprise MCP server once it's installed.
• "Create a new repository called 'my-project'"
• "Search for repositories related to machine learning"
• "Create a pull request from my feature branch to main"
• "Get the contents of the README.md file in repository X"
• "List open issues in my repository"
• Check that the path to the index.js file is correct in your MCP settings
• Verify that your GitHub Personal Access Token has the necessary permissions
• Ensure that the GitHub API URL is correct for your GitHub instance
• Check the logs for any error messages
• `create_or_update_file`
• Create or update a single file in a repository
• Inputs:
• `owner` (string): Repository owner (username or organization)
• `repo` (string): Repository name
• `path` (string): Path where to create/update the file
• `content` (string): Content of the file
• `message` (string): Commit message
• `branch` (string): Branch to create/update the file in
• `sha` (optional string): SHA of file being replaced (for updates)
• Returns: File content and commit details
• `push_files`
• Push multiple files in a single commit
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `branch` (string): Branch to push to
• `files` (array): Files to push, each with `path` and `content`
• `message` (string): Commit message
• Returns: Updated branch reference
• `search_repositories`
• Search for GitHub repositories
• Inputs:
• `query` (string): Search query
• `page` (optional number): Page number for pagination
• `perPage` (optional number): Results per page (max 100)
• Returns: Repository search results
• `create_repository`
• Create a new GitHub repository
• Inputs:
• `name` (string): Repository name
• `description` (optional string): Repository description
• `private` (optional boolean): Whether repo should be private
• `autoInit` (optional boolean): Initialize with README
• Returns: Created repository details
• `get_file_contents`
• Get contents of a file or directory
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `path` (string): Path to file/directory
• `branch` (optional string): Branch to get contents from
• Returns: File/directory contents
• `create_issue`
• Create a new issue
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `title` (string): Issue title
• `body` (optional string): Issue description
• `assignees` (optional string[]): Usernames to assign
• `labels` (optional string[]): Labels to add
• `milestone` (optional number): Milestone number
• Returns: Created issue details
• `create_pull_request`
• Create a new pull request
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `title` (string): PR title
• `body` (optional string): PR description
• `head` (string): Branch containing changes
• `base` (string): Branch to merge into
• `draft` (optional boolean): Create as draft PR
• `maintainer_can_modify` (optional boolean): Allow maintainer edits
• Returns: Created pull request details
• `fork_repository`
• Fork a repository
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `organization` (optional string): Organization to fork to
• Returns: Forked repository details
• `create_branch`
• Create a new branch
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `branch` (string): Name for new branch
• `from_branch` (optional string): Source branch (defaults to repo default)
• Returns: Created branch reference
• `list_issues`
• List and filter repository issues
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `state` (optional string): Filter by state ('open', 'closed', 'all')
• `labels` (optional string[]): Filter by labels
• `sort` (optional string): Sort by ('created', 'updated', 'comments')
• `direction` (optional string): Sort direction ('asc', 'desc')
• `since` (optional string): Filter by date (ISO 8601 timestamp)
• `page` (optional number): Page number
• `per_page` (optional number): Results per page
• Returns: Array of issue details
• `update_issue`
• Update an existing issue
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `issue_number` (number): Issue number to update
• `title` (optional string): New title
• `body` (optional string): New description
• `state` (optional string): New state ('open' or 'closed')
• `labels` (optional string[]): New labels
• `assignees` (optional string[]): New assignees
• `milestone` (optional number): New milestone number
• Returns: Updated issue details
• `add_issue_comment`
• Add a comment to an issue
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `issue_number` (number): Issue number to comment on
• `body` (string): Comment text
• Returns: Created comment details
• `search_code`
• Search for code across GitHub repositories
• Inputs:
• `q` (string): Search query using GitHub code search syntax
• `sort` (optional string): Sort field ('indexed' only)
• `order` (optional string): Sort order ('asc' or 'desc')
• `per_page` (optional number): Results per page (max 100)
• `page` (optional number): Page number
• Returns: Code search results with repository context
• `search_issues`
• Search for issues and pull requests
• Inputs:
• `q` (string): Search query using GitHub issues search syntax
• `sort` (optional string): Sort field (comments, reactions, created, etc.)
• `order` (optional string): Sort order ('asc' or 'desc')
• `per_page` (optional number): Results per page (max 100)
• `page` (optional number): Page number
• Returns: Issue and pull request search results
• `search_users`
• Search for GitHub users
• Inputs:
• `q` (string): Search query using GitHub users search syntax
• `sort` (optional string): Sort field (followers, repositories, joined)
• `order` (optional string): Sort order ('asc' or 'desc')
• `per_page` (optional number): Results per page (max 100)
• `page` (optional number): Page number
• Returns: User search results
• `list_commits`
• Gets commits of a branch in a repository
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `page` (optional string): page number
• `per_page` (optional string): number of record per page
• `sha` (optional string): branch name
• Returns: List of commits
• `get_issue`
• Gets the contents of an issue within a repository
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `issue_number` (number): Issue number to retrieve
• Returns: Github Issue object & details
• `get_pull_request`
• Get details of a specific pull request
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `pull_number` (number): Pull request number
• Returns: Pull request details including diff and review status
• `list_pull_requests`
• List and filter repository pull requests
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `state` (optional string): Filter by state ('open', 'closed', 'all')
• `head` (optional string): Filter by head user/org and branch
• `base` (optional string): Filter by base branch
• `sort` (optional string): Sort by ('created', 'updated', 'popularity', 'long-running')
• `direction` (optional string): Sort direction ('asc', 'desc')
• `per_page` (optional number): Results per page (max 100)
• `page` (optional number): Page number
• Returns: Array of pull request details
• `create_pull_request_review`
• Create a review on a pull request
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `pull_number` (number): Pull request number
• `body` (string): Review comment text
• `event` (string): Review action ('APPROVE', 'REQUEST_CHANGES', 'COMMENT')
• `commit_id` (optional string): SHA of commit to review
• `comments` (optional array): Line-specific comments, each with:
• `path` (string): File path
• `position` (number): Line position in diff
• `body` (string): Comment text
• Returns: Created review details
• `merge_pull_request`
• Merge a pull request
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `pull_number` (number): Pull request number
• `commit_title` (optional string): Title for merge commit
• `commit_message` (optional string): Extra detail for merge commit
• `merge_method` (optional string): Merge method ('merge', 'squash', 'rebase')
• Returns: Merge result details
• `get_pull_request_files`
• Get the list of files changed in a pull request
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `pull_number` (number): Pull request number
• Returns: Array of changed files with patch and status details
• `get_pull_request_status`
• Get the combined status of all status checks for a pull request
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `pull_number` (number): Pull request number
• Returns: Combined status check results and individual check details
• `update_pull_request_branch`
• Update a pull request branch with the latest changes from the base branch (equivalent to GitHub's "Update branch" button)
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `pull_number` (number): Pull request number
• `expected_head_sha` (optional string): The expected SHA of the pull request's HEAD ref
• Returns: Success message when branch is updated
• `get_pull_request_comments`
• Get the review comments on a pull request
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `pull_number` (number): Pull request number
• Returns: Array of pull request review comments with details like the comment text, author, and location in the diff
• `get_pull_request_reviews`
• Get the reviews on a pull request
• Inputs:
• `owner` (string): Repository owner
• `repo` (string): Repository name
• `pull_number` (number): Pull request number
• Returns: Array of pull request reviews with details like the review state (APPROVED, CHANGES_REQUESTED, etc.), reviewer, and review body
• `language:javascript`: Search by programming language
• `repo:owner/name`: Search in specific repository
• `path:app/src`: Search in specific path
• `extension:js`: Search by file extension
• Example: `q: "import express" language:typescript path:src/`
• `is:issue` or `is:pr`: Filter by type
• `is:open` or `is:closed`: Filter by state
• `label:bug`: Search by label
• `author:username`: Search by author
• Example: `q: "memory leak" is:issue is:open label:bug`
• `type:user` or `type:org`: Filter by account type
• `followers:>1000`: Filter by followers
• `location:London`: Search by location
• Example: `q: "fullstack developer" location:London followers:>100`
• Go to [Personal access tokens](https://github.com/settings/tokens) (in GitHub Settings > Developer settings)
• Select which repositories you'd like this token to have access to (Public, All, or Select)
• Create a token with the `repo` scope ("Full control of private repositories")
• Alternatively, if working only with public repositories, select only the `public_repo` scope
• Copy the generated token