Skip to main content
GitHub MCP logo
  • Category: model context protocol
  • Auth: API_KEY
  • Composio-managed OAuth available? N/A
  • Tools: 44
  • Triggers: 0
  • Slug: GITHUB_MCP
  • Version: 20261018_00

Tools

Slug: GITHUB_MCP_ADD_COMMENT_TO_PENDING_REVIEWAdd 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).

Input Parameters

string
required
The text of the review comment
number
The line of the blob in the pull request diff that the comment applies to. For multi-line comments, the last line of the range
string
required
The relative path to the file that necessitates a comment
string
required
Repository name
string ("LEFT" | "RIGHT")
The side of the diff to comment on. LEFT indicates the previous state, RIGHT indicates the new state
string
required
Repository owner
number
For multi-line comments, the first line of the range that the comment applies to
string ("LEFT" | "RIGHT")
For multi-line comments, the starting side of the diff that the comment applies to. LEFT indicates the previous state, RIGHT indicates the new state
number
required
Pull request number
string ("FILE" | "LINE")
required
The level at which the comment is targeted
Slug: GITHUB_MCP_ADD_ISSUE_COMMENTAdd a comment and/or reaction to a specific issue or issue comment in a GitHub repository. Use this tool with pull requests as well (in this case pass pull request number as issue_number), but only if user is not asking specifically to add or react to review comments. At least one of body or reaction is required.

Input Parameters

string
Comment content. Required unless reaction is provided.
string
required
Repository name
string
required
Repository owner
string ("+1" | "-1" | "laugh" | "confused" | "heart" | "hooray" | "rocket" | "eyes")
Emoji reaction to add. Required unless body is provided.
integer
The numeric ID of the issue or pull request comment to react to. Use this for reactions to comments; omit it to react to the issue or pull request itself. Cannot be combined with body.
number
required
Issue or pull request number to comment on or react to.
Slug: GITHUB_MCP_ADD_REPLY_TO_PULL_REQUEST_COMMENTAdd a reply and/or reaction to an existing pull request comment. This can create a new comment linked as a reply to the specified comment, add an emoji reaction to the specified comment, or do both. At least one of body or reaction is required.

Input Parameters

string
The text of the reply. Required unless reaction is provided.
string
required
Repository name
string
required
Repository owner
string ("+1" | "-1" | "laugh" | "confused" | "heart" | "hooray" | "rocket" | "eyes")
Emoji reaction to add. Required unless body is provided.
number
required
The numeric ID of the pull request review comment to reply or react to. Use the number from a #discussion_r… anchor, not the GraphQL thread node ID (PRRT_…).
number
Pull request number. Required when body is provided.
Slug: GITHUB_MCP_CREATE_BRANCHCreate a new branch in a GitHub repository

Input Parameters

string
required
Repository name
string
required
Repository owner
string
required
Name for new branch
string
Source branch (defaults to repo default)
Slug: GITHUB_MCP_CREATE_OR_UPDATE_FILECreate or update a single file in a GitHub repository. If updating, you should 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.To obtain the current blob SHA before updating, call the get_file_contents tool with the same owner, repo, and path, and set its ref parameter to this tool’s branch value. The first text result reports the blob SHA for the requested path.SHA MUST be provided for existing file updates.

Input Parameters

string
The blob SHA of the file being replaced. Required if the file already exists. Retrieve it with get_file_contents using the same owner, repo, and path, with ref set to this tool’s branch value.
string
required
Path where to create/update the file
string
required
Repository name
string
required
Repository owner (username or organization)
string
required
Branch to create/update the file in
string
required
Content of the file, exactly as it should appear once written. Do not base64-encode it; this server does that before calling the REST API.
string
required
Commit message
Set true to update a symbolic link itself; content must be its new target path.
Slug: GITHUB_MCP_CREATE_PULL_REQUESTCreate a new pull request in a GitHub repository.

Input Parameters

string
required
Branch to merge into
string
PR description
string
required
Branch containing changes
string
required
Repository name
boolean
Create as draft PR
string
required
Repository owner
string
required
PR title
array
GitHub usernames or ORG/team-slug team reviewers to request reviews from
boolean
Allow maintainer edits
Slug: GITHUB_MCP_CREATE_REPOSITORYCreate a new GitHub repository in your account or specified organization

Input Parameters

string
required
Repository name
boolean
Whether the repository should be private. Defaults to true (private) when omitted.
boolean
Initialize with README
string
Repository description
string
Organization to create the repository in (omit to create in your personal account)
Slug: GITHUB_MCP_DELETE_FILEDelete a file from a GitHub repository

Input Parameters

string
required
Path to the file to delete
string
required
Repository name
string
required
Repository owner (username or organization)
string
required
Branch to delete the file from
string
required
Commit message
Slug: GITHUB_MCP_FORK_REPOSITORYFork a GitHub repository to your account or specified organization

Input Parameters

string
required
Repository name
string
required
Repository owner
string
Organization to fork to
Slug: GITHUB_MCP_GET_COMMITGet details for a commit from a GitHub repository

Input Parameters

string
required
Commit SHA, branch name, or tag name
number
Page number for pagination (min 1)
string
required
Repository name
string
required
Repository owner
string ("none" | "stats" | "full_patch")
Level of detail to include for changed files. “none” omits stats and files entirely. “stats” (default) includes per-file metadata: filename, status, and lines-of-code counts (additions, deletions, changes), with no patch content. “full_patch” additionally includes the unified diff content for each file and can be very large.
number
Results per page for pagination (min 1, max 100)
Slug: GITHUB_MCP_GET_FILE_CONTENTSGet the contents of a file or directory from a GitHub repository

Input Parameters

string
Accepts optional git refs such as refs/tags/{tag}, refs/heads/{branch} or refs/pull/{pr_number}/head
string
Accepts optional commit SHA. If specified, it will be used instead of ref
string
Path to file/directory
string
required
Repository name
string
required
Repository owner (username or organization)
array
Subset of fields to return for each entry when the path is a directory. If omitted, all fields are returned. Ignored when the path is a single file. Use this to reduce response size when listing directories and you only need specific fields, e.g. just ‘name’ and ‘type’.
Slug: GITHUB_MCP_GET_LABELGet a specific label from a repository.

Input Parameters

string
required
Label name.
string
required
Repository name
string
required
Repository owner (username or organization name)
Slug: GITHUB_MCP_GET_LATEST_RELEASEGet the latest release in a GitHub repository

Input Parameters

string
required
Repository name
string
required
Repository owner
Slug: GITHUB_MCP_GET_MEGet 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.
Slug: GITHUB_MCP_GET_RELEASE_BY_TAGGet a specific release by its tag name in a GitHub repository

Input Parameters

string
required
Tag name (e.g., ‘v1.0.0’)
string
required
Repository name
string
required
Repository owner
Slug: GITHUB_MCP_GET_TAGGet details about a specific git tag in a GitHub repository

Input Parameters

string
required
Tag name
string
required
Repository name
string
required
Repository owner
Slug: GITHUB_MCP_GET_TEAM_MEMBERSGet member usernames of a specific team in an organization. Limited to organizations accessible with current credentials

Input Parameters

string
required
Organization login (owner) that contains the team.
string
required
Team slug
Slug: GITHUB_MCP_GET_TEAMSGet details of the teams the user is a member of. Limited to organizations accessible with current credentials

Input Parameters

string
Username to get teams for. If not provided, uses the authenticated user.
Slug: GITHUB_MCP_ISSUE_READGet information about a specific issue in a GitHub repository.

Input Parameters

number
Page number for pagination (min 1)
string
required
The name of the repository
string
required
The owner of the repository
string ("get" | "get_comments" | "get_sub_issues" | "get_parent" | "get_labels")
required
The read operation to perform on a single issue. Options are: 1. get - Get issue details. Also returns best-effort hierarchy flags (has_parent, has_children); parent and sub_issues_summary are optional relationship summaries, and closed_by_pull_requests summarizes the pull requests configured to close the issue as total_count plus up to 5 references. 2. get_comments - Get issue comments. 3. get_sub_issues - Get sub-issues (children) of the issue. 4. get_parent - Get the parent issue, if this issue is a sub-issue of another. 5. get_labels - Get labels assigned to the issue.
number
Results per page for pagination (min 1, max 100)
number
required
The number of the issue
Slug: GITHUB_MCP_ISSUE_WRITECreate a new or update an existing issue in a GitHub repository.

Input Parameters

string
Issue body content
string
required
Repository name
string
Type of this issue. For updates, pass null to remove the current type. Only use if issue types are enabled for this repository. Use list_issue_types to get valid type values for this repository or its owner organization. If the repository doesn’t support issue types, omit this parameter.
string
required
Repository owner
string ("open" | "closed")
New state
string
Issue title
array
Labels to apply to this issue
string ("create" | "update")
required
Write operation to perform on a single issue. Options are: - ‘create’ - creates a new issue. - ‘update’ - updates an existing issue.
array
Usernames to assign to this issue
number
Milestone number
string
Repository name of the parent issue. Must be provided with parent_owner. Omit both to use owner and repo. Only used when method is ‘create’ and parent_issue_number is provided.
number
Issue number that this issue is a duplicate of. Required when state_reason is ‘duplicate’.
array
Issue field values to set or clear. Each item requires ‘field_name’ and exactly one of ‘value’, ‘field_option_name’, or ‘delete: true’.
number
Issue number to update
string
Repository owner of the parent issue. Must be provided with parent_repo. Omit both to use owner and repo. Only used when method is ‘create’ and parent_issue_number is provided.
string ("completed" | "not_planned" | "duplicate")
Reason for the state change. Ignored unless state is changed.
number
Issue number of the parent issue. Only used when method is ‘create’ and cannot be combined with issue_fields. The new issue is created and attached to this parent in the same operation.
Slug: GITHUB_MCP_LIST_BRANCHESList branches in a GitHub repository

Input Parameters

number
Page number for pagination (min 1)
string
required
Repository name
string
required
Repository owner
number
Results per page for pagination (min 1, max 100)
Slug: GITHUB_MCP_LIST_COMMITSGet 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).

Input Parameters

string
Commit SHA, branch or tag name to list commits of. If not provided, uses the default branch of the repository. If a commit SHA is provided, will list commits up to that SHA.
number
Page number for pagination (min 1)
string
Only commits containing this file path will be returned
string
required
Repository name
string
required
Repository owner
string
Only commits after this date will be returned (ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ or YYYY-MM-DD)
string
Only commits before this date will be returned (ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ or YYYY-MM-DD)
string
Author username or email address to filter commits by
array
Subset of fields to return for each commit. If omitted, all fields are returned. Use this to reduce response size when you only need specific fields, e.g. just ‘sha’ and ‘html_url’.
number
Results per page for pagination (min 1, max 100)
Slug: GITHUB_MCP_LIST_ISSUE_FIELDSList issue fields for a repository or organization. Returns field definitions including name, type (text, number, date, single_select), and for single_select fields the list of valid option names. When repo is omitted, returns org-level fields directly.

Input Parameters

string
The name of the repository. When provided, returns fields for this specific repository (inherited from its organization). When omitted, returns org-level fields directly.
string
required
The account owner of the repository or organization. The name is not case sensitive.
Slug: GITHUB_MCP_LIST_ISSUESList issues in a GitHub repository. For pagination, use the ‘endCursor’ from the previous response’s ‘pageInfo’ in the ‘after’ parameter.

Input Parameters

string
required
Repository name
string
Cursor for pagination. Use the cursor from the previous response.
string
required
Repository owner
string
Filter by date (ISO 8601 timestamp)
string ("OPEN" | "CLOSED")
Filter by state, by default both open and closed issues are returned when not provided
array
Subset of fields to return for each issue. If omitted, all fields are returned. Use this to reduce response size when you only need specific fields; omitting ‘body’ and ‘field_values’ in particular drops the largest per-result data.
array
Filter by labels
string ("CREATED_AT" | "UPDATED_AT" | "COMMENTS")
Order issues by field. If provided, the ‘direction’ also needs to be provided.
number
Results per page for pagination (min 1, max 100)
string ("ASC" | "DESC")
Order direction. If provided, the ‘orderBy’ also needs to be provided.
array
Filter by custom issue field values. Each entry takes a field_name and a value; the server looks up the field and coerces the value to its type (single-select option name, text, number, or YYYY-MM-DD date).
Slug: GITHUB_MCP_LIST_ISSUE_TYPESList supported issue types for a repository or its owner organization. When repo is omitted, returns org-level issue types directly.

Input Parameters

string
The name of the repository. When provided, returns issue types for this specific repository. When omitted, returns org-level issue types directly.
string
required
The account owner of the repository or organization.
Slug: GITHUB_MCP_LIST_PULL_REQUESTSList 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.

Input Parameters

string
Filter by base branch
string
Filter by head user/org and branch
number
Page number for pagination (min 1)
string
required
Repository name
string ("created" | "updated" | "popularity" | "long-running")
Sort by
string
required
Repository owner
string ("open" | "closed" | "all")
Filter by state
array
Subset of fields to return for each pull request. If omitted, all fields are returned. Use this to reduce response size when you only need specific fields; omitting ‘body’ in particular drops the largest per-result data.
number
Results per page for pagination (min 1, max 100)
string ("asc" | "desc")
Sort direction
Slug: GITHUB_MCP_LIST_RELEASESList releases in a GitHub repository

Input Parameters

number
Page number for pagination (min 1)
string
required
Repository name
string
required
Repository owner
array
Subset of fields to return for each release. If omitted, all fields are returned. Use this to reduce response size when you only need specific fields; omitting ‘body’ in particular drops the largest per-release data.
number
Results per page for pagination (min 1, max 100)
Slug: GITHUB_MCP_LIST_REPOSITORY_COLLABORATORSList collaborators of a GitHub repository. Results are paginated; the response includes nextPage, prevPage, firstPage, and lastPage fields. To get the next page, use the nextPage value as the page parameter.

Input Parameters

number
Page number for pagination (default 1, min 1)
string
required
Repository name
string
required
Repository owner
number
Results per page for pagination (default 30, min 1, max 100)
string ("outside" | "direct" | "all")
Filter by affiliation. Can be one of: ‘outside’ (outside collaborators), ‘direct’ (all with permissions regardless of org membership), ‘all’ (all collaborators). Default: ‘all’
Slug: GITHUB_MCP_LIST_TAGSList git tags in a GitHub repository

Input Parameters

number
Page number for pagination (min 1)
string
required
Repository name
string
required
Repository owner
number
Results per page for pagination (min 1, max 100)
Slug: GITHUB_MCP_MERGE_PULL_REQUESTMerge a pull request in a GitHub repository.

Input Parameters

string
required
Repository name
string
required
Repository owner
number
required
Pull request number
string
Title for merge commit
string ("merge" | "squash" | "rebase")
Merge method
string
Extra detail for merge commit
string
The expected SHA of the pull request’s HEAD ref
Slug: GITHUB_MCP_PULL_REQUEST_READGet information on a specific pull request in GitHub repository.

Input Parameters

number
Page number for pagination (min 1)
string
required
Repository name
string
Cursor for pagination, used only by the get_review_comments method. Pass the endCursor from the previous page’s PageInfo to fetch the next page.
string
required
Repository owner
string ("get" | "get_diff" | "get_status" | "get_files" | "get_commits" | "get_review_comments" | "get_reviews" | "get_comments" | "get_check_runs")
required
Action to specify what pull request data needs to be retrieved from GitHub. Possible options: 1. get - Get details of a specific pull request. 2. get_diff - Get the diff of a pull request. 3. get_status - Get combined commit status of a head commit in a pull request. 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_commits - Get the list of commits on a pull request. Use with pagination parameters to control the number of results returned. 6. get_review_comments - Get review threads on a pull request. Each thread contains logically grouped review comments made on the same code location during pull request reviews. Returns thread metadata and comments with nullable current and original line-range coordinates (line, start_line, original_line, original_start_line). Current coordinates are omitted when unavailable, such as for outdated comments. Use cursor-based pagination (perPage, after) to control results. 7. get_reviews - Get the reviews on a pull request. When asked for review comments, use get_review_comments method. Use with pagination parameters to control the number of results returned. 8. 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. 9. get_check_runs - Get check runs for the head commit of a pull request. Check runs are the individual CI/CD jobs and checks that run on the PR.
number
Results per page for pagination (min 1, max 100)
number
required
Pull request number
Slug: GITHUB_MCP_PULL_REQUEST_REVIEW_WRITECreate 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.
  • resolve_thread: Resolve a review thread. Requires only “threadId” parameter with the thread’s node ID (e.g., PRRT_kwDOxxx). The owner, repo, and pullNumber parameters are not used for this method. Resolving an already-resolved thread is a no-op.
  • unresolve_thread: Unresolve a previously resolved review thread. Requires only “threadId” parameter. The owner, repo, and pullNumber parameters are not used for this method. Unresolving an already-unresolved thread is a no-op.

Input Parameters

string
Review comment text
string
required
Repository name
string ("APPROVE" | "REQUEST_CHANGES" | "COMMENT")
Review action to perform.
string
required
Repository owner
string ("create" | "submit_pending" | "delete_pending" | "resolve_thread" | "unresolve_thread")
required
The write operation to perform on pull request review.
string
SHA of commit to review
string
The node ID of the review thread (e.g., PRRT_kwDOxxx). Required for resolve_thread and unresolve_thread methods. Get thread IDs from pull_request_read with method get_review_comments.
number
required
Pull request number
Slug: GITHUB_MCP_PUSH_FILESPush multiple files to a GitHub repository in a single commit

Input Parameters

string
required
Repository name
array
required
Array of file objects to push, each object with path (string) and content (string)
string
required
Repository owner
string
required
Branch to push to
string
required
Commit message
Slug: GITHUB_MCP_REQUEST_COPILOT_REVIEWRequest a GitHub Copilot code review for a pull request. Use this for automated feedback on pull requests, usually before requesting a human reviewer.

Input Parameters

string
required
Repository name
string
required
Repository owner
number
required
Pull request number
Slug: GITHUB_MCP_RUN_SECRET_SCANNINGScan files, content, or recent changes for secrets such as API keys, passwords, tokens, and credentials.This tool is intended for targeted scans of specific files, snippets, or diffs provided directly as content. The files parameter accepts either a single string or an array of strings containing raw file contents or diff hunks, and returns detected secrets with their locations and related secret scanning metadata. Content must not be empty. For full repository scanning, other mechanisms are available.Caveats:
  • Only files within the codebase should be scanned. Files outside of the codebase should not be sent.
  • Files listed in .gitignore should be skipped.

Input Parameters

string
required
Repository name
string
required
A single string or an array of strings containing file contents, snippets, or diff hunks to scan for secrets. These must be raw contents, not repository file paths.
string
required
Repository owner
Slug: GITHUB_MCP_SEARCH_CODEFast 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.

Input Parameters

number
Page number for pagination (min 1)
string
Sort field (‘indexed’ only)
string ("asc" | "desc")
Sort order for results
string
required
Search query (GitHub code search REST). Implicit AND between terms; supports OR, NOT, and "quoted phrase" for exact match. Qualifiers: repo:owner/repo, org:, user:, language:, path:dir (prefix match), filename:exact.ext, extension:, in:file, in:path, size:, is:archived, is:fork. Max 256 chars. Examples: WithContext language:go org:github; "package main" repo:o/r; func extension:go path:cmd repo:o/r; NOT TODO language:go repo:o/r.
array
Subset of fields to return for each code search result. If omitted, all fields are returned. Use this to reduce response size when you only need specific fields; omitting ‘repository’ and ‘text_matches’ in particular drops the largest per-result data.
number
Results per page for pagination (min 1, max 100)
Slug: GITHUB_MCP_SEARCH_COMMITSSearch for commits across GitHub repositories using GitHub’s commit search syntax. Useful for finding specific changes, authors, or messages across one or many repositories. Searches the default branch only.

Input Parameters

number
Page number for pagination (min 1)
string ("author-date" | "committer-date")
Sort by author or committer date (defaults to best match)
string ("asc" | "desc")
Sort order
string
required
Commit search query (GitHub commit search REST). Searches commit messages on the default branch only. Scope the search with repo:owner/repo, org:, or user: (queries without a scope qualifier match across all of GitHub and are usually not what you want). Other qualifiers: author:, committer:, author-name:, committer-name:, author-email:, committer-email:, author-date:, committer-date: (supports >, <, >=, <=, and YYYY-MM-DD..YYYY-MM-DD ranges), merge:true&#124;false, hash:, tree:, parent:, is:public. Examples: repo:owner/repo fix panic; org:github author:defunkt committer-date:>=2024-01-01; "refactor cache" repo:o/r; hash:abc1234 repo:o/r.
number
Results per page for pagination (min 1, max 100)
Slug: GITHUB_MCP_SEARCH_ISSUESSearch issues using natural-language semantic matching. Best for conceptual or paraphrased queries (e.g. “login fails after password reset”). Already scoped to is:issue.

Input Parameters

number
Page number for pagination (min 1)
string
Optional repository name. If provided with owner, only issues for this repository are listed.
string ("comments" | "reactions" | "reactions-+1" | "reactions--1" | "reactions-smile" | "reactions-thinking_face" | "reactions-heart" | "reactions-tada" | "interactions" | "created" | "updated")
Sort field by number of matches of categories, defaults to best match
string ("asc" | "desc")
Sort order
string
Optional repository owner. If provided with repo, only issues for this repository are listed.
string
required
The search query, as natural language. When the user gives alternative wordings, include them as plain words rather than joining them with OR.
array
Subset of fields to return for each issue result. If omitted, all fields are returned. Use this to reduce response size when you only need specific fields; omitting ‘body’, ‘reactions’, and ‘labels’ in particular drops the largest per-result data.
number
Results per page for pagination (min 1, max 100)
Slug: GITHUB_MCP_SEARCH_PULL_REQUESTSSearch for pull requests in GitHub repositories using issues search syntax already scoped to is:pr

Input Parameters

number
Page number for pagination (min 1)
string
Optional repository name. If provided with owner, only pull requests for this repository are listed.
string ("comments" | "reactions" | "reactions-+1" | "reactions--1" | "reactions-smile" | "reactions-thinking_face" | "reactions-heart" | "reactions-tada" | "interactions" | "created" | "updated")
Sort field by number of matches of categories, defaults to best match
string ("asc" | "desc")
Sort order
string
Optional repository owner. If provided with repo, only pull requests for this repository are listed.
string
required
Search query using GitHub pull request search syntax
array
Subset of fields to return for each pull request result. If omitted, all fields are returned. Use this to reduce response size when you only need specific fields; omitting ‘body’, ‘reactions’, and ‘labels’ in particular drops the largest per-result data.
number
Results per page for pagination (min 1, max 100)
Slug: GITHUB_MCP_SEARCH_REPOSITORIESFind GitHub repositories by name, description, readme, topics, or other metadata. Perfect for discovering projects, finding examples, or locating specific repositories across GitHub.

Input Parameters

number
Page number for pagination (min 1)
string ("stars" | "forks" | "help-wanted-issues" | "updated")
Sort repositories by field, defaults to best match
string ("asc" | "desc")
Sort order
string
required
Repository search query. Examples: ‘machine learning in:name stars:>1000 language:python’, ‘topic:react’, ‘user:facebook’. Supports advanced search syntax for precise filtering.
number
Results per page for pagination (min 1, max 100)
boolean
Return minimal repository information (default: true). When false, returns full GitHub API repository objects.
Slug: GITHUB_MCP_SEARCH_USERSFind GitHub users by username, real name, or other profile information. Useful for locating developers, contributors, or team members.

Input Parameters

number
Page number for pagination (min 1)
string ("followers" | "repositories" | "joined")
Sort users by number of followers or repositories, or when the person joined GitHub.
string ("asc" | "desc")
Sort order
string
required
User search query. Examples: ‘john smith’, ‘location:seattle’, ‘followers:>100’. Search is automatically scoped to type:user.
number
Results per page for pagination (min 1, max 100)
Slug: GITHUB_MCP_SUB_ISSUE_WRITEAdd a sub-issue to a parent issue in a GitHub repository.

Input Parameters

string
required
Repository name
string
required
Repository owner
string
required
The action to perform on a single sub-issue Options are: - ‘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. Writes issue hierarchy. To move a sub-issue to a new parent, use add with replace_parent=true; there is no writable parent field.
number
The ID of the sub-issue to be prioritized after (either after_id OR before_id should be specified)
number
The ID of the sub-issue to be prioritized before (either after_id OR before_id should be specified)
number
required
The number of the parent issue
number
required
The ID of the sub-issue to add. ID is not the same as issue number
boolean
When true, replaces the sub-issue’s current parent issue. Use with ‘add’ method only.
Slug: GITHUB_MCP_UPDATE_PULL_REQUESTUpdate an existing pull request in a GitHub repository.

Input Parameters

string
New base branch name
string
New description
string
required
Repository name
boolean
Mark pull request as draft (true) or ready for review (false)
string
required
Repository owner
string ("open" | "closed")
New state
string
New title
array
GitHub usernames or ORG/team-slug team reviewers to request reviews from
number
required
Pull request number to update
boolean
Allow maintainer edits
Slug: GITHUB_MCP_UPDATE_PULL_REQUEST_BRANCHUpdate the branch of a pull request with the latest changes from the base branch.

Input Parameters

string
required
Repository name
string
required
Repository owner
number
required
Pull request number
string
The expected SHA of the pull request’s HEAD ref