We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 24 since January 2026, each linked to its source.
github-mcp-serverWhen removing a reaction from an issue, issue comment, or pull request review comment, call the matching granular reaction-removal tool with the repository identifiers and reaction ID (plus the issue number or comment ID).
remove_issue_reaction({"owner":"<owner>","repo":"<repo>","issue_number":<issue_number>,"reaction_id":<reaction_id>})When maintaining a repository issue, use `update_issue_comment` to replace an existing issue or pull request conversation comment’s content.
update_issue_comment({"owner":"<owner>","repo":"<repo>","comment_id":<comment_id>,"body":"<new comment content>"})When merging a pull request only if its head still matches a known commit, call `merge_pull_request` with that commit’s SHA in `expectedHeadSha`.
{"owner":"<owner>","repo":"<repo>","pullNumber":<pull_number>,"expectedHeadSha":"<expected_head_sha>"}When creating an issue as a sub-issue, call `issue_write` with `method: "create"` and `parent_issue_number`; the server creates and attaches it in the same operation. For a parent in another repository, also provide both `parent_owner` and `parent_repo`.
issue_write({"method":"create","owner":"<owner>","repo":"<repo>","title":"<sub-issue title>","parent_issue_number":<parent issue number>})When reviewing an issue, enable `duplicate_detection` and call `find_duplicate` with the repository owner, name, and issue number. The tool returns ranked duplicate candidates; optional threshold and pagination parameters are available.
find_duplicate({"owner":"<owner>","repo":"<repo>","issue_number":<issue_number>})When updating one field on a Project issue, call `projects_write` with `method: "update_project_item"` and a single `updated_field` using the field name and value. Identify the item by `item_id` or by its repository owner, repository name, and issue number.
{"method":"update_project_item","owner":"<project-owner>","project_number":<project-number>,"item_id":<item-id>,"updated_field":{"name":"<field-name>","value":"<value>"}}When multiple items in one project need the same field update, call `projects_write` with `method: "update_project_items"` and the item references and field value.
{"method":"update_project_items","owner":"<owner>","project_number":<project-number>,"items":[{"node_id":"<project-item-node-id>"}],"updated_field":{"name":"<field-name>","value":"<value>"}}When a supported GitHub MCP tool returns more data than you need, pass its optional `fields` array with the response fields to keep. The parameter is available by default in v1.8.0; only selected tools support it.
list_issues({"owner":"<owner>","repo":"<repo>","fields":["title","number","state"]})When Copilot is the intended assignee for an issue and the opt-in toolset is enabled, call `assign_copilot_to_issue_with_intent` with the repository, issue number, rationale, confidence, and an explicit `is_suggestion` choice.
assign_copilot_to_issue_with_intent({"owner":"<owner>","repo":"<repo>","issue_number":<issue_number>,"rationale":"<one concise sentence, 280 characters or less>","confidence":"<LOW|MEDIUM|HIGH>","is_suggestion":<true|false>})When reading or updating GitHub Projects item fields by name, use `field_names` for reads and `updated_field: {name, value}` for writes. For writes, resolve the item with `item_owner`, `item_repo`, and `issue_number` or pass `item_id`.
projects_list({"method":"list_project_items","owner":"<owner>","project_number":<project_number>,"field_names":["Status","Priority"]})