add_issue_comment
Add a comment to an existing issue
LABSCO SUMMARY
A pull request can be opened, reviewed, brought up to date and merged without leaving the conversation.
The pull request surface is the deep part: changed files, combined status checks, review comments and reviews are four separate reads, so a failing check is distinguishable from an unanswered review comment. push_files puts a whole change into one commit rather than one commit per file, which is what keeps history legible when an edit spans a directory. Updating a branch from base takes an expected head SHA, so the update refuses instead of racing somebody else's push.
What it is
A GitHub client covering repository contents, branches, issues, pull requests with reviews and merges, and search across code, issues and users.
What you get
- Repositories created and forked, branches created from a base, file contents read, a single file created or updated against its SHA, and several files pushed in one commit.
- Commits listed for a branch with paging.
- Issues created with assignees, labels and a milestone, listed with filters and sorting, fetched, updated including their state, and commented on.
- Pull requests created with a base, a head and a draft flag, listed and filtered, fetched, and read for their changed files, combined status checks, review comments and reviews.
- A review submitted with a body, inline comments and an event; the branch updated from base against an expected head SHA; and a merge with the method, title and message you choose.
- Search across repositories, code, issues and pull requests, and users.
Requirements
A GitHub personal access token in GITHUB_PERSONAL_ACCESS_TOKEN, scoped for what you intend to do — creating repositories, pushing files, reviewing and merging included.
Setup effort
One command plus a key — npx -y @missionsquad/mcp-github, then supply credentials
USE CASES
01
Shipping a change that touches several files at once
One commit for the whole change keeps the history readable, and the branch is created from a base you name.
02
Reviewing a pull request you did not write
The changed files, the combined check status and the existing comments are three different reads, and a review needs all three.
03
Finishing a pull request that has gone stale
Updating from base against an expected head SHA refuses rather than racing another push, and the checks are re-read before the merge.
04
Filing and triaging issues
Labels, assignees and state are the fields triage actually moves, and all of them are settable after creation.
05
Finding out where something is implemented across GitHub
Code search finds the call site, repository search finds the project, and the file read confirms what is actually there.
06
Starting from somebody else's repository
Forking puts a writable copy under your account or organisation, and a single file edit is enough to begin.
26 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_branch
Create a new branch in a GitHub repository
create_issue
Create a new issue in a GitHub repository
create_or_update_file
Create or update a single file in a GitHub repository
create_pull_request
Create a new pull request in a GitHub repository
create_pull_request_review
Create a review on a pull request
create_repository
Create a new GitHub repository in your account
fork_repository
Fork a GitHub repository to your account or specified organization
get_file_contents
Get the contents of a file or directory from a GitHub repository
get_issue
Get details of a specific issue in a GitHub repository.
get_pull_request
Get details of a specific pull request
get_pull_request_comments
Get the review comments on a pull request
get_pull_request_files
Get the list of files changed in a pull request
get_pull_request_reviews
Get the reviews on a pull request
get_pull_request_status
Get the combined status of all status checks for a pull request
list_commits
Get list of commits of a branch in a GitHub repository
list_issues
List issues in a GitHub repository with filtering options
list_pull_requests
List and filter repository pull requests
merge_pull_request
Merge a pull request
push_files
Push multiple files to a GitHub repository in a single commit
search_code
Search for code across GitHub repositories
search_issues
Search for issues and pull requests across GitHub repositories
search_repositories
Search for GitHub repositories
search_users
Search for users on GitHub
update_issue
Update an existing issue in a GitHub repository
update_pull_request_branch
Update a pull request branch with the latest changes from the base branch
BEFORE YOU INSTALL
What to know first
Tools you get
26 tools when we connected; the project documents 48. The missing 22 are the repository and organization webhook tools, this fork's main addition. They need a token with admin:repo_hook or admin:org_hook.
Requires
- npx on PATH
- GITHUB_PERSONAL_ACCESS_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @missionsquad/mcp-githubMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"github": {
"command": "npx",
"args": [
"-y",
"@missionsquad/mcp-github"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
}
}
}
}<YOUR_TOKEN> is a GitHub personal access token from github.com/settings/tokens, with repo (or public_repo) scope, plus admin:repo_hook or admin:org_hook if you want the webhook tools. The server also accepts the token as GITHUB_PAT.
