GitHub Official

GitHub Official MCP Server

Official GitHub MCP Server, by GitHub. Provides seamless integration with GitHub APIs, enabling advanced automation and interaction capabilities for developers and tools.

What is an MCP Server?⁠

MCP Info

Image Building Info

Available Tools (40)

Tools Details

Tool: add_comment_to_pending_review

Add review comment to the requester's latest pending pull request review. A pending review needs to already exist to call this (check with the user if not sure).

Tool: add_issue_comment

Add a comment to a specific issue in a GitHub repository. Use this tool to add comments to pull requests as well (in this case pass pull request number as issue_number), but only if user is not asking specifically to add review comments.

Tool: assign_copilot_to_issue

Assign Copilot to a specific issue in a GitHub repository.

This tool can help with the following outcomes:

• a Pull Request created with source code changes to resolve the issue

More information can be found at:

• https://docs.github.com/en/copilot/using-github-copilot/using-copilot-coding-agent-to-work-on-tasks/about-assigning-tasks-to-copilot⁠ Parameters|Type|Description -|-|- issueNumber|number|Issue number owner|string|Repository owner repo|string|Repository name

Tool: create_branch

Create a new branch in a GitHub repository

Tool: create_or_update_file

Create or update a single file in a GitHub repository. If updating, you must provide the SHA of the file you want to update. Use this tool to create or update a file in a GitHub repository remotely; do not use it for local file operations.

Tool: create_pull_request

Create a new pull request in a GitHub repository.

Tool: create_repository

Create a new GitHub repository in your account or specified organization

Tool: delete_file

Delete a file from a GitHub repository

This tool may perform destructive updates.

Tool: fork_repository

Fork a GitHub repository to your account or specified organization

Tool: get_commit

Get details for a commit from a GitHub repository

This tool is read-only. It does not modify its environment.

Tool: get_file_contents

Get the contents of a file or directory from a GitHub repository

This tool is read-only. It does not modify its environment.

Tool: get_label

Get a specific label from a repository.

This tool is read-only. It does not modify its environment.

Tool: get_latest_release

Get the latest release in a GitHub repository

This tool is read-only. It does not modify its environment.

Tool: get_me

Get details of the authenticated GitHub user. Use this when a request is about the user's own profile for GitHub. Or when information is missing to build other tool calls.

Tool: get_release_by_tag

Get a specific release by its tag name in a GitHub repository

This tool is read-only. It does not modify its environment.

Tool: get_tag

Get details about a specific git tag in a GitHub repository

This tool is read-only. It does not modify its environment.

Tool: get_team_members

Get member usernames of a specific team in an organization. Limited to organizations accessible with current credentials

This tool is read-only. It does not modify its environment.

Tool: get_teams

Get details of the teams the user is a member of. Limited to organizations accessible with current credentials

This tool is read-only. It does not modify its environment.

Tool: issue_read

Get information about a specific issue in a GitHub repository.

1. get - Get details of a specific issue.
2. get_comments - Get issue comments.
3. get_sub_issues - Get sub-issues of the issue.
4. get_labels - Get labels assigned to the issue.

owner|string|The owner of the repository repo|string|The name of the repository page|numberoptional|Page number for pagination (min 1) perPage|numberoptional|Results per page for pagination (min 1, max 100)

This tool is read-only. It does not modify its environment.

Tool: issue_write

Create a new or update an existing issue in a GitHub repository.

• 'create' - creates a new issue.
• 'update' - updates an existing issue.

owner|string|Repository owner repo|string|Repository name assignees|arrayoptional|Usernames to assign to this issue body|stringoptional|Issue body content duplicate_of|numberoptional|Issue number that this issue is a duplicate of. Only used when state_reason is 'duplicate'. issue_number|numberoptional|Issue number to update labels|arrayoptional|Labels to apply to this issue milestone|numberoptional|Milestone number state|stringoptional|New state state_reason|stringoptional|Reason for the state change. Ignored unless state is changed. title|stringoptional|Issue title type|stringoptional|Type of this issue. Only use if the repository has issue types configured. Use list_issue_types tool to get valid type values for the organization. If the repository doesn't support issue types, omit this parameter.

Tool: list_branches

List branches in a GitHub repository

This tool is read-only. It does not modify its environment.

Tool: list_commits

Get list of commits of a branch in a GitHub repository. Returns at least 30 results per page by default, but can return more if specified using the perPage parameter (up to 100).

This tool is read-only. It does not modify its environment.

Tool: list_issue_types

List supported issue types for repository owner (organization).

This tool is read-only. It does not modify its environment.

Tool: list_issues

List issues in a GitHub repository. For pagination, use the 'endCursor' from the previous response's 'pageInfo' in the 'after' parameter.

This tool is read-only. It does not modify its environment.

Tool: list_pull_requests

List pull requests in a GitHub repository. If the user specifies an author, then DO NOT use this tool and use the search_pull_requests tool instead.

This tool is read-only. It does not modify its environment.

Tool: list_releases

List releases in a GitHub repository

This tool is read-only. It does not modify its environment.

Tool: list_tags

List git tags in a GitHub repository

This tool is read-only. It does not modify its environment.

Tool: merge_pull_request

Merge a pull request in a GitHub repository.

Tool: pull_request_read

Get information on a specific pull request in GitHub repository.

1. get - Get details of a specific pull request.
2. get_diff - Get the diff of a pull request.
3. get_status - Get status of a head commit in a pull request. This reflects status of builds and checks.
4. get_files - Get the list of files changed in a pull request. Use with pagination parameters to control the number of results returned.
5. get_review_comments - Get the review comments on a pull request. They are comments made on a portion of the unified diff during a pull request review. Use with pagination parameters to control the number of results returned.
6. get_reviews - Get the reviews on a pull request. When asked for review comments, use get_review_comments method.
7. get_comments - Get comments on a pull request. Use this if user doesn't specifically want review comments. Use with pagination parameters to control the number of results returned.

owner|string|Repository owner pullNumber|number|Pull request number repo|string|Repository name page|numberoptional|Page number for pagination (min 1) perPage|numberoptional|Results per page for pagination (min 1, max 100)

This tool is read-only. It does not modify its environment.

Tool: pull_request_review_write

Create and/or submit, delete review of a pull request.

Available methods:

• create: Create a new review of a pull request. If "event" parameter is provided, the review is submitted. If "event" is omitted, a pending review is created.
• submit_pending: Submit an existing pending review of a pull request. This requires that a pending review exists for the current user on the specified pull request. The "body" and "event" parameters are used when submitting the review.
• delete_pending: Delete an existing pending review of a pull request. This requires that a pending review exists for the current user on the specified pull request. Parameters|Type|Description -|-|- method|string|The write operation to perform on pull request review. owner|string|Repository owner pullNumber|number|Pull request number repo|string|Repository name body|stringoptional|Review comment text commitID|stringoptional|SHA of commit to review event|stringoptional|Review action to perform.

Tool: push_files

Push multiple files to a GitHub repository in a single commit

Tool: request_copilot_review

Request a GitHub Copilot code review for a pull request. Use this for automated feedback on pull requests, usually before requesting a human reviewer.

Tool: search_code

Fast and precise code search across ALL GitHub repositories using GitHub's native search engine. Best for finding exact symbols, functions, classes, or specific code patterns.

This tool is read-only. It does not modify its environment.

Tool: search_issues

Search for issues in GitHub repositories using issues search syntax already scoped to is:issue

This tool is read-only. It does not modify its environment.

Tool: search_pull_requests

Search for pull requests in GitHub repositories using issues search syntax already scoped to is:pr

This tool is read-only. It does not modify its environment.

Tool: search_repositories

Find GitHub repositories by name, description, readme, topics, or other metadata. Perfect for discovering projects, finding examples, or locating specific repositories across GitHub.

This tool is read-only. It does not modify its environment.

Tool: search_users

Find GitHub users by username, real name, or other profile information. Useful for locating developers, contributors, or team members.

This tool is read-only. It does not modify its environment.

Tool: sub_issue_write

Add a sub-issue to a parent issue in a GitHub repository.

• 'add' - add a sub-issue to a parent issue in a GitHub repository.
• 'remove' - remove a sub-issue from a parent issue in a GitHub repository.
• 'reprioritize' - change the order of sub-issues within a parent issue in a GitHub repository. Use either 'after_id' or 'before_id' to specify the new position.

owner|string|Repository owner repo|string|Repository name sub_issue_id|number|The ID of the sub-issue to add. ID is not the same as issue number after_id|numberoptional|The ID of the sub-issue to be prioritized after (either after_id OR before_id should be specified) before_id|numberoptional|The ID of the sub-issue to be prioritized before (either after_id OR before_id should be specified) replace_parent|booleanoptional|When true, replaces the sub-issue's current parent issue. Use with 'add' method only.

Tool: update_pull_request

Update an existing pull request in a GitHub repository.

Tool: update_pull_request_branch

Update the branch of a pull request with the latest changes from the base branch.

Use this MCP Server

{
  "mcpServers": {
    "github-official": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "GITHUB_PERSONAL_ACCESS_TOKEN",
        "ghcr.io/github/github-mcp-server"
      ],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

Why is it safer to run MCP Servers with Docker?⁠