Connect Claude & ChatGPT to GitHub

30 tools for GitHub

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

• add_issue_assigneesVisible to othersAssign people to an issue. Required: owner, repo, issue_number and assignees (list of GitHub logins).
• add_issue_labelsVisible to othersAdd labels to an issue without removing its existing labels. Required: owner, repo, issue_number and the label names.
• create_issueChanges dataCreate a new issue in a repository. Required: owner, repo and title; optional body, labels, assignees and milestone.
• create_issue_commentVisible to othersPost a comment on an issue or pull request. Required: owner, repo, issue_number and body. The comment is visible to everyone with access to the repository.
• create_pull_requestChanges dataOpen a pull request from a head branch into a base branch. Required: owner, repo, head and base; optional title, body and draft.
• create_pull_request_reviewChanges dataReview a pull request: approve, request changes or comment. Required: owner, repo and pull_number; set event (APPROVE, REQUEST_CHANGES, COMMENT) and body.
• create_releaseChanges dataPublish a release for a tag. Required: owner, repo and tag_name; optional name, body, draft, prerelease and generate_release_notes.
• get_current_userGet the GitHub user you are signed in as (login, name, profile). Use it first to know whose repositories and issues 'mine' refers to.
• get_file_contentsRead a file or list a directory in a repository. Required: owner, repo and path; optional ref for a branch, tag or commit.
• get_issueGet one issue with its title, body, state, labels and assignees. Required: owner, repo and ticket_number (the issue number).
• get_pull_requestGet one pull request with its description, branches, merge status and review state. Required: owner, repo and pull_number.
• get_repositoryGet details of one repository (description, default branch, visibility, open issue count). Required: owner and repo.
• list_branchesList the branches of a repository. Required: owner and repo; optional protected to show only protected branches.
• list_commitsList commits in a repository, newest first. Required: owner and repo; filter by sha (branch), path, author, since or until.
• list_issue_commentsList the comments on an issue or pull request. Required: owner, repo and issue_number.
• list_issuesList issues in one repository. Required: owner and repo; filter by state, labels, assignee, creator, mentioned or milestone. Note: this also returns pull requests.
• list_labelsList the labels defined in a repository. Required: owner and repo. Use it to find valid label names before labelling issues.
• list_my_issuesList issues assigned to you across all your repositories. Use filter (assigned, created, mentioned, subscribed, all), state and labels to narrow the list.
• list_my_repositoriesList repositories you own or can access. Filter with visibility, affiliation or type, and sort by created, updated, pushed or full_name.
• list_notificationsList your unread GitHub notifications (mentions, review requests, assignments). Set all=true to include read ones, or participating=true for direct involvement only.
• list_organization_repositoriesList the repositories of an organization. Required: org (the organization login); optional type, sort and direction.
• list_pull_request_filesList the files changed in a pull request, with additions, deletions and patch. Required: owner, repo and pull_number.
• list_pull_request_reviewsList the reviews submitted on a pull request (approved, changes requested, commented). Required: owner, repo and pull_number.
• list_pull_requestsList pull requests in a repository. Required: owner and repo; filter by state (open, closed, all), base or head branch.
• list_releasesList the releases of a repository, newest first. Required: owner and repo.
• merge_pull_requestVisible to othersMerge a pull request into its base branch. Required: owner, repo and pull_number; optional merge_method (merge, squash, rebase) and commit_title. This changes the repository and cannot simply be undone.
• search_issuesSearch issues and pull requests across GitHub with a query string q (e.g. 'repo:acme/app is:open label:bug'). Use this to find issues or pull requests by text, state, label or author.
• search_repositoriesSearch GitHub repositories with a query string q (GitHub search syntax, e.g. 'invoice user:acme'). Returns matching repositories.
• update_issueVisible to othersUpdate an issue: change title, body, labels, assignees or milestone, or close/reopen it with state. Required: owner, repo and ticket_number (the issue number).
• update_pull_requestChanges dataUpdate a pull request's title, body or base branch, or close/reopen it with state. Required: owner, repo and pull_number.

Questions