Your AI team, working in GitHub MCP
GitHub MCP lets agents work with repositories, issues, pull requests, users, actions, projects, notifications, code security, and other authorized GitHub surfaces.
Start your companyWhat your team can do in GitHub MCP
44 tools to work with, connected with an API key.
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).
Add 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.
Add 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.
Create a new branch in a GitHub repository
Create 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.
Create a new pull request in a GitHub repository.
Create a new GitHub repository in your account or specified organization
Delete a file from a GitHub repository
Fork a GitHub repository to your account or specified organization
Get details for a commit from a GitHub repository
Get the contents of a file or directory from a GitHub repository
Get a specific label from a repository.
Get the latest release in a GitHub repository
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.
Get a specific release by its tag name in a GitHub repository
Get details about a specific git tag in a GitHub repository
Get member usernames of a specific team in an organization. Limited to organizations accessible with current credentials
Get details of the teams the user is a member of. Limited to organizations accessible with current credentials
Get information about a specific issue in a GitHub repository.
Create a new or update an existing issue in a GitHub repository.
List branches in a GitHub repository
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).
List 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.
List supported issue types for a repository or its owner organization. When repo is omitted, returns org-level issue types directly.
List issues in a GitHub repository. For pagination, use the 'endCursor' from the previous response's 'pageInfo' in the 'after' parameter.
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.
List releases in a GitHub repository
List 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.
List git tags in a GitHub repository
Merge a pull request in a GitHub repository.
Get information on a specific pull request in GitHub repository.
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. - 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.
Push multiple files to a GitHub repository in a single commit
Request a GitHub Copilot code review for a pull request. Use this for automated feedback on pull requests, usually before requesting a human reviewer.
Scan 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.
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.
Search 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.
Search issues using natural-language semantic matching. Best for conceptual or paraphrased queries (e.g. "login fails after password reset"). Already scoped to is:issue.
Search for pull requests in GitHub repositories using issues search syntax already scoped to is:pr
Find GitHub repositories by name, description, readme, topics, or other metadata. Perfect for discovering projects, finding examples, or locating specific repositories across GitHub.
Find GitHub users by username, real name, or other profile information. Useful for locating developers, contributors, or team members.
Add a sub-issue to a parent issue in a GitHub repository.
Update an existing pull request in a GitHub repository.
Update the branch of a pull request with the latest changes from the base branch.
Nothing matches that.
More in Model context protocol
See them all βOperate an Ambiguous workspace through its provider-hosted MCP server, including documents, spreadsheets, tasks, CRM, calendar, mail, chat, andβ¦
945 toolsβ BBigdata.com MCP gives agents grounded access to financial news, transcripts, filings, entity intelligence, and research workflows.
17 toolsβ CCheckvist beta PRO MCP lets AI assistants manage hierarchical lists, tasks, tags, due dates, and assignees, and read task notes.
16 toolsβ ccve.now by Sazabi provides a free public vulnerability feed, CVE/GHSA/OSV lookups, and exact package-version checks against its indexed catalog. Noβ¦
3 toolsβ DFree AI-powered access to public GitHub repository documentation and codebase analysis via DeepWiki. No authentication required.
3 toolsβ DAI-powered access to GitHub repository documentation and codebase analysis, including private repositories, via Devin.
23 toolsβ