GitHub MCP server for Claude, ChatGPT, Claude Code and Cursor

This action allows the authenticated user to add new email addresses to their GitHub account. It handles unverified emails, ensuring that duplicates and verified emails from other accounts are managed correctly.

This action adds a specified user as a collaborator to a given GitHub repository. If the user is already a collaborator, their permissions can be updated accordingly.

Adds one or more GitHub users as assignees to an issue. This action adds to the existing assignees (does not replace them). You need push access to the repository to modify assignees. Use 'remove_assignees_from_an_issue' to remove assignees.

This action allows users to add specified labels to an existing issue in a repository. If the labels do not exist, they will be created automatically.

Approves a workflow run that originates from a pull request in a forked repository. This action requires manual approval when the run is subject to specific workflow rules.

This action compares two specific commits, branches, or tags in a repository. It provides detailed information on the differences between these two commit points, including the number of commits ahead or behind, and details about changed files.

This action creates a new Git blob in a specified repository. Users must provide the necessary content and encoding type for the blob being created. Note: You must have write access to the repository's Contents. A 404 error typically indicates the repository doesn't exist or you lack write permissions.

This action creates a new commit for the specified repository on GitHub. It takes the commit message, tree SHA, author and committer information, and optional parent commits and creates the commit in the repository.

This action creates a new issue in a specified GitHub repository. It requires the repository to exist and have issues enabled, and certain fields may require appropriate permissions.

This action allows users to submit comments on existing GitHub issues or pull requests. It requires specifying the owner, repository, issue number, and the content of the comment.

This action allows you to create a new repository in a specified GitHub organization. You can configure various options such as visibility, features, and templates for the repository.

This action creates a pull request in a specified repository. It requires the base and head branches to exist and necessitates either a title or an issue to be provided.

This action creates a new Git reference such as a branch or tag within a specified repository. It requires the owner and repository name, along with a reference and the SHA of the commit it points to. IMPORTANT: This action can only create NEW references. If the reference already exists, the API will return a 422 error with 'Reference already exists'. To modify an existing branch or tag, use the 'Update a reference' action (GITHUB_UPDATE_A_REFERENCE) instead. To check if a reference exists before creating it, use 'Get a reference' (GITHUB_GET_A_REFERENCE) or 'List matching references' (GITHUB_LIST_MATCHING_REFERENCES).

This action creates a new release in a specified GitHub repository by using the provided tag name. The release can include additional metadata such as title and description, and can be specified as a draft or pre-release.

Creates a new Git tree object in a repository by defining the structure of files and directories. This action allows users to specify tree entries, optionally building on a provided base tree SHA for more complex tree structures.

This action allows the user to create a new file or update an existing file in a GitHub repository. By providing the necessary parameters, the user can specify the file's content, commit message, and other metadata.

This action allows users to permanently delete a specified repository on the platform. It requires proper permissions and is irreversible once completed.

This action allows users to search and filter pull requests based on various criteria like repository, author, state, labels, and more. It returns a structured response that includes essential information about the pull requests found.

This action allows users to search for GitHub repositories based on various criteria such as keywords, programming language, and star ratings. It provides a filtered, optimized set of results to help users find relevant repositories quickly.

This action retrieves a specific pull request from a GitHub repository. You need to provide the repository owner's username, the repository name, and the pull request number to get the details of that pull request.

This action retrieves a specific Git reference from a GitHub repository. It allows users to access information about branches, tags, or other references in the specified repository. IMPORTANT: The reference must actually exist in the repository. If you receive a 404 error, the branch or tag does not exist. Consider using 'list_matching_references' action first to discover available references if you're unsure. Note that repositories may use 'main' instead of 'master' as the default branch.

This action fetches the content of a specific file in a GitHub repository or lists the contents of a directory. For files, it returns the content in Base64 format. For directories, it returns an array of items within that directory.

This action fetches the branches of a specified GitHub repository and allows filtering by whether the branches are protected or not.

This action retrieves a list of deployments associated with a specified repository. It allows users to filter deployments based on various criteria such as commit SHA, ref name, task name, and more.

This action retrieves a list of public organizations associated with a specified GitHub user. By using the unique GitHub username, it queries the GitHub API and returns the relevant organization details.

This action retrieves a paginated list of organizations that the authenticated GitHub user belongs to. It allows users to easily access information about their associated organizations.

Lists pull requests for a GitHub repository. **REQUIRED PARAMETERS (MUST BE PROVIDED):** - owner: The GitHub username or organization (e.g., 'octocat', 'microsoft') - repo: The repository name (e.g., 'hello-world', 'vscode') Both 'owner' and 'repo' are MANDATORY. The action will fail if either is missing. OPTIONAL filters: state (open/closed/all), head branch, base branch, and sorting options. NOTE: This action does NOT support 'assignee' or 'since' parameters. To search for pull requests by assignee, author, or across multiple repositories, use GITHUB_FIND_PULL_REQUESTS instead.

This action retrieves all files related to a specified pull request in a GitHub repository. It provides detailed information on each file, including status and changes made.

Retrieves a list of repositories that the authenticated user has access to. This can include public, private, and repositories owned by the user or explicitly shared with them.

This action retrieves the repositories that the authenticated user has starred on GitHub. Users can specify the sort order and pagination options to manage the results returned.

This action retrieves the list of contributors for a designated GitHub repository. The contributors are sorted in descending order based on their contributions to the repository.

Retrieves issues from a GitHub repository. IMPORTANT: You must specify BOTH the 'owner' (account/organization) AND 'repo' (repository name). For example, for the repository 'https://github.com/microsoft/vscode', use owner='microsoft' and repo='vscode'. Supports filtering by state, assignee, labels, and more.

This action retrieves a list of users who have starred a specific GitHub repository, allowing you to see who showed interest in the project. It supports pagination to manage large sets of results.

This action enables users to search for issues and pull requests on GitHub using specific keywords and qualifiers. It allows filtering results based on various parameters like repository, state, and labels to narrow down search outcomes.

This action stars a specific repository for the authenticated user. You must provide both the repository owner (username or organization) and repository name to identify which repository to star. Starring indicates interest in the repository and may provide updates about it.

This action updates an existing Git reference to point to a given commit SHA. By default, only fast-forward updates are allowed to prevent accidental history rewriting. Use `force=true` when you need to move a branch backward or rewrite history. The reference must already exist - use the 'Create a reference' action to create new refs.

This action creates a new check run for a specific commit in a repository. It allows external services to report their status, provide detailed feedback, and attach annotations and images directly within the GitHub interface. **IMPORTANT: Authentication Requirement** This endpoint requires GitHub App authentication with 'checks:write' permission. OAuth tokens and personal access tokens (PAT) cannot create check runs. If you need to report status using a PAT, consider using the 'Create a commit status' action instead.

Creates a check suite for a specific commit in a repository. IMPORTANT: This action requires a GitHub App installation access token with 'checks:write' permission. OAuth tokens and classic personal access tokens CANNOT use this endpoint (will return 404). By default, check suites are automatically created when check runs are created - only use this to manually create check suites when automatic creation has been disabled.

This action allows users to create a GitHub Codespace seamlessly. Users can provide either a repository ID along with a reference to a branch or commit or specify a pull request to base the codespace on.

This action creates a new GitHub Codespace associated with a specified pull request, allowing users to start coding in an environment configured from their repository. The action provides options for setting geographic location, machine type, and other parameters to customize the codespace experience.

This action creates a new GitHub Codespace for the user in a designated repository. It sets up a development environment based on specified configurations and provides options for machine type, idle timeout, and display name.

This action allows the user to create a comment on a specific commit in a repository. The user can specify a comment for the entire commit or target a specific line in a file if desired.

This action creates a deployment in a GitHub repository. It targets a specific reference such as a branch or tag and handles various deployment options.

This action creates a new repository for the authenticated user. The repository can be public or private and can include various features like issues, projects, and a README file upon creation.

This action creates a webhook for a specified repository. It allows the repository owner to receive event notifications at a designated URL whenever specified events occur.

This action creates a review comment on a specified pull request. It allows users to provide feedback on specific lines or files, enhancing collaboration during the review process.

This action creates a review for a specified pull request. Users can approve the request, request changes, or add comments to the code.

This action creates a new team within a specified GitHub organization. It allows for the inclusion of maintainers, repositories, and privacy settings, aiding in the organization of team collaboration.

This action allows you to manually trigger a specific GitHub Actions workflow. You can specify the workflow by its ID or filename and provide any necessary inputs defined for the workflow.

Deletes a specific commit comment from a repository using its unique identifier. This action ensures that the specified comment is removed if it exists, providing a cleaner commit history.

This action deletes an inactive deployment from a specified repository. It requires the owner's username, repository name, and the deployment ID to identify the specific deployment to delete.

This action allows you to permanently delete a specified GitHub gist using its unique identifier. Once the gist is deleted, the action cannot be undone, and the gist will no longer be accessible.

This action permanently deletes a specified label from a GitHub repository. REQUIRED: You must provide all three parameters - 'owner' (repository owner/org), 'repo' (repository name), and 'name' (label name). GitHub repositories are identified by the owner/repo combination (e.g., 'octocat/Hello-World').

This action removes a specific milestone from a repository. It ensures that the milestone is deleted only if it exists, providing a safe and idempotent operation.

This action permanently deletes a specified GitHub project using its GraphQL node ID. The project cannot be recovered after deletion. You must have admin permissions for the project to delete it.

This action removes a specified project card from a GitHub project (classic). NOTE: GitHub Classic Projects was deprecated on April 1, 2025. This action only works with existing classic project cards. For new projects, use GitHub Projects V2.

This action removes a specific project field (column) from a GitHub Projects V2 project. It is a permanent change to the project structure on GitHub. Note: Built-in fields like Status cannot be deleted.

This action allows users to permanently delete a specified release from their repository, which removes not just the release itself, but also any associated assets and possibly the Git tag tied to it.

This action deletes a specified webhook associated with a repository. It ensures that the webhook is removed and no longer sends events to the defined endpoint.

This action allows you to delete a specific team from your organization. Once executed, the team and any associated child teams will be permanently removed.

This action deletes a specific workflow run from a given repository on GitHub. It requires the repository's owner, the repository name, and the unique workflow run ID to perform the deletion.

This action retrieves the raw content of a specified file from a GitHub repository based on the file's SHA hash. If the repository and SHA exist, the content is typically returned in Base64 encoding.

This action retrieves detailed information about a specific branch in a GitHub repository. It provides insights such as the branch name, latest commit SHA, and protection status of the branch.

This action retrieves detailed information about a specific check run within a given GitHub repository, including its status and conclusions. It is useful for understanding the result of automated checks applied to code changes.

This action retrieves a specific check suite by its ID from the designated repository. It provides details about various check runs associated with that suite, which can be useful for monitoring the status of checks in the repository.

This action retrieves a specific commit from a designated repository. It allows users to access details of the commit based on various reference types, including SHA, branch, or tag.

This action fetches a specific comment from a GitHub commit using its unique identifier. It provides detailed information about the comment, including attributes such as the author, content, and creation date.

This action retrieves a specific deployment based on the owner and repository provided. It requires the deployment ID to fetch the corresponding deployment details.

This action retrieves the status of a specific deployment within a GitHub repository. It requires the IDs for both the deployment and its status to provide the relevant details.

This action retrieves the details of a specific discussion within a designated team in an organization, identified by its unique number. It allows users to access full discussion information easily.

This action retrieves a specific comment from a discussion within a specified team and organization. It allows users to see details about the comment based on provided identifiers.

This action retrieves a specific GitHub gist using its unique identifier. If the gist exists, it will return detailed information about it, including its contents and metadata.

This action retrieves a specific label from a specified GitHub repository. It requires the repository owner's name, the repository name, and the label name to fetch the label details.

This action fetches detailed information about a specific milestone from a GitHub repository using its unique identifier. It provides comprehensive data, including the title, description, and current state of the milestone.

Retrieves details of a GitHub project (V2) by its project number and owner. Returns the project's title, description, state (open/closed), visibility, timestamps, and owner information. If no username or org is provided, defaults to the authenticated user's projects.

This action retrieves detailed information about a specific project card using its unique identifier. It allows users to access essential attributes and metadata associated with the project card. NOTE: GitHub Classic Projects REST API was deprecated. This action only works with existing classic project cards. For new projects, use GitHub Projects V2.

Retrieves details for a specific project column by its ID. Returns the column name, URLs, timestamps, and other metadata. Note: This uses the deprecated Classic Projects API which was sunset on April 1, 2025.

This action retrieves a specific release from a GitHub repository. It requires the repository owner, repository name, and release ID to successfully fetch the release details.

This action fetches detailed data about a specific GitHub repository based on the provided owner and repository name. It allows users to retrieve essential information about the repository, such as its description, owner, and other relevant details.

This action retrieves the configuration details of a specific webhook associated with a particular repository. It allows users to see the settings and attributes of an existing webhook to manage their repository integrations effectively.

This action fetches detailed information about a specific Git tag from a given GitHub repository, based on the SHA of the requested tag. It is useful for retrieving metadata associated with the tag, such as its message, date, and commit reference.

This action allows you to retrieve the public profile information of a specific GitHub user by their username. It provides details such as the user's login, avatar, and repository count.

This action retrieves the detailed information of a specified GitHub Actions workflow within a repository. You can identify the workflow using either its numeric ID or the workflow file name.

This action retrieves a specific workflow run from a GitHub repository using its unique ID. It provides details such as the run's status and other attributes, allowing users to monitor the workflow execution.

This action retrieves detailed information about a specified GitHub Pages build for a given repository. It provides insights into the build's status, associated commit, duration, and any errors encountered during the build process.

This action checks if a user is a member of a specific team in a GitHub organization. If they are a member, it returns their role (member or maintainer) and membership state (active or pending). If not a member, it clearly indicates that with is_member=False.

This action retrieves all comments made on a specific commit in a given repository. It allows users to access information such as the comment text, author, and timestamps related to the comments.

Lists commits from a GitHub repository. REQUIRED: You must provide 'owner' (the GitHub username or organization that owns the repository) and 'repo' (the repository name). Optional filters include author, date range (since/until), file path, or branch/SHA.

This action retrieves a list of commits associated with a specific pull request. Users can view the details of each commit, such as the author and commit message, while utilizing pagination to navigate through results if needed.

This action retrieves a list of forks for a given repository on GitHub. It allows sorting of results based on criteria such as star count, and supports pagination to manage result sets.

This action retrieves a list of global security advisories from GitHub. Users can filter results based on various criteria including IDs, types, ecosystems, severities, and date ranges.

This action retrieves comments for a specific issue in a GitHub repository. It allows users to view all the comments made on the issue over time.

This action retrieves all labels associated with a specified GitHub repository. It supports pagination to manage large sets of label data effectively.

This action retrieves pull requests associated with a specific commit in a GitHub repository. It returns information about merged pull requests if the commit belongs to the default branch, or includes open pull requests that mention the commit in other branches.

This action retrieves a list of codespaces available in a specified repository for the authenticated user. It provides details such as the total count and information about each codespace.

This action retrieves a list of public repositories for a specified GitHub user. You can filter the repositories by type and sort them based on various criteria.

This action retrieves a list of collaborators who have access to a specific repository. Users can filter the results based on their affiliation and permission level.

This action retrieves a list of events for a specified GitHub repository. It provides information on activities like code pushes, issues, and pull requests in chronological order.

Retrieves a list of invitations for users who have been invited to collaborate on a specified repository. This action allows you to specify the repository owner and pagination settings to manage the data returned.

This action retrieves a list of webhooks associated with a specified repository. It provides details about each webhook's configuration and status, enabling users to manage their repository integrations effectively.