---
next_cursor: eyJzY29yZSI6MCwic2VxIjo1MTIsInNpbmNlIjpudWxsLCJ0b29sIjoiZ2l0aHViLW1jcC1zZXJ2ZXIiLCJ2IjoxfQ
has_more: true
next: https://sincecutoff.com/v1/changes.md?tool=github-mcp-server&score=0&cursor=eyJzY29yZSI6MCwic2VxIjo1MTIsInNpbmNlIjpudWxsLCJ0b29sIjoiZ2l0aHViLW1jcC1zZXJ2ZXIiLCJ2IjoxfQ
items: 10
---
# sincecutoff.com changes: github-mcp-server

## github-mcp-server assign_copilot_to_issue accepts custom_instructions (github-mcp-server, 2026-01-19)
Published 2026-10-13
- slug: github-mcp-server-assign-copilot-to-issue-accepts-custom-instructions-13235c7c7c15
- score: 0.95

How to use it:

When assigning Copilot to an issue with task-specific guidance, call `assign_copilot_to_issue` with the issue identifiers and `custom_instructions` containing that guidance.

Examples:

```
{"name":"assign_copilot_to_issue","arguments":{"owner":"<owner>","repo":"<repo>","issue_number":123,"custom_instructions":"Follow PEP 8. Use pytest. Maintain Python 3.8+ compatibility."}}
```

- why_it_matters: Assign Copilot coding agent to an issue with task-specific guidance.
- sources: <https://github.com/github/github-mcp-server/releases/tag/v0.29.0>, <https://github.com/github/github-mcp-server/pull/1806>, <https://github.com/github/github-mcp-server/blob/v0.29.0/README.md>
- gotchas: "Version: v0.29.0"; "owner (required): Repository owner."; "repo (required): Repository name."; "issue_number (required): Issue number."; "custom_instructions: Additional context, constraints, or guidance for the agent beyond the issue body."; "Prerequisite: The tool requires OAuth scope `repo`."

## github-mcp-server adds ProjectV2 status update tools (github-mcp-server, 2026-02-19)
Published 2026-10-13
- slug: github-mcp-server-adds-projectv2-status-update-tools-f27d231e23c0
- score: 0.97

How to use it:

When an agent needs to list, inspect, or create a GitHub ProjectV2 status update, use the `projects_list`, `projects_get`, or `projects_write` tool with the corresponding status-update method.

Examples:

```
projects_list({"method":"list_project_status_updates","owner":"<owner>","owner_type":"<user|org>","project_number":<project_number>,"per_page":50})
```

```
projects_get({"method":"get_project_status_update","status_update_id":"<status_update_node_id>"})
```

```
projects_write({"method":"create_project_status_update","owner":"<owner>","owner_type":"<user|org>","project_number":<project_number>,"status":"<status>","body":"<markdown>","start_date":"<YYYY-MM-DD>","target_date":"<YYYY-MM-DD>"})
```

- why_it_matters: List, inspect, or create a status update for a GitHub ProjectV2 project.
- sources: <https://github.com/github/github-mcp-server/releases/tag/v0.31.0>, <https://github.com/github/github-mcp-server/blob/v0.31.0/README.md>
- gotchas: "Version: v0.31.0"; "projects_list.method (required): Set to `list_project_status_updates`."; "projects_list.owner (required): Project owner’s user or organization login."; "projects_list.project_number (required): Project number for listing status updates."; "projects_list.owner_type: Owner type: `user` or `org`; otherwise auto-detected."; "projects_list.per_page: Results per page, maximum 50."; "projects_list.after: Forward pagination cursor from the previous page’s `pageInfo.nextCursor`."; "projects_get.method (required): Set to `get_project_status_update`."; "projects_get.status_update_id (required): Status update node ID."; "projects_write.method (required): Set to `create_project_status_update`."; "projects_write.owner (required): Project owner’s user or organization login."; "projects_write.project_number (required): Project number for the status update."; "projects_write.status: Status of the project update."; "projects_write.body: Markdown body of the status update."; "projects_write.start_date: Start date in `YYYY-MM-DD` format."; "projects_write.target_date: Target date in `YYYY-MM-DD` format."; "projects_write.owner_type: Owner type: `user` or `org`; otherwise auto-detected."; "Prerequisite: The `projects_list` and `projects_get` tools require OAuth scope `read:project` (accepted scopes also include `project`)."; "Prerequisite: The `projects_write` tool requires OAuth scope `project`."

## github-mcp-server adds Streamable HTTP mode (github-mcp-server, 2026-02-19)
Published 2026-10-13
- slug: github-mcp-server-adds-streamable-http-mode-db39dfec1578
- score: 0.95

How to use it:

When a client needs Streamable HTTP, run `github-mcp-server http` to serve the GitHub MCP Server at `http://localhost:8082`. Configure the client to use that HTTP URL.

Examples:

```
github-mcp-server http
```

```
{"type":"http","url":"http://localhost:8082"}
```

- why_it_matters: Run the GitHub MCP Server over Streamable HTTP for a client that uses that transport.
- sources: <https://github.com/github/github-mcp-server/releases/tag/v0.31.0>, <https://github.com/github/github-mcp-server/blob/v0.31.0/docs/streamable-http.md>
- gotchas: "Version: v0.31.0"

## github-mcp-server can exclude tools through server configuration (github-mcp-server, 2026-02-19)
Published 2026-10-13
- slug: github-mcp-server-can-exclude-tools-through-server-configuration-5943ebd4438b
- score: 0.91

How to use it:

When configuring a GitHub MCP Server deployment, list the tools to disable as comma-separated names. Set them with `--exclude-tools` for a local server or `X-MCP-Exclude-Tools` for a remote server; excluded tools stay disabled even if otherwise enabled.

Examples:

```
{"type":"stdio","command":"go","args":["run","./cmd/github-mcp-server","stdio","--toolsets=<toolsets>","--exclude-tools=<tool1>,<tool2>"],"env":{"GITHUB_PERSONAL_ACCESS_TOKEN":"<github-token>"}}
```

```
{"type":"http","url":"https://api.githubcopilot.com/mcp/","headers":{"X-MCP-Toolsets":"<toolsets>","X-MCP-Exclude-Tools":"<tool1>,<tool2>"}}
```

- why_it_matters: Disable selected tools in a GitHub MCP Server deployment configuration.
- sources: <https://github.com/github/github-mcp-server/releases/tag/v0.31.0>, <https://github.com/github/github-mcp-server/blob/v0.31.0/docs/server-configuration.md>
- gotchas: "Version: v0.31.0"; "--exclude-tools=<tool1>,<tool2> (required): Comma-separated tool names to disable, regardless of other settings."; "X-MCP-Exclude-Tools: <tool1>,<tool2> (required): Remote-server header listing comma-separated tool names to disable."; "Prerequisite: Use the local stdio or remote HTTP server configuration format; the docs’ local example supplies a GitHub personal access token through `GITHUB_PERSONAL_ACCESS_TOKEN`."

## github-mcp-server adds check runs (github-mcp-server, 2026-03-06)
Published 2026-10-13
- slug: github-mcp-server-adds-check-runs-fdaeac7a5d6d
- score: 0.95

How to use it:

When inspecting CI checks for a pull request, call `pull_request_read` with `method: "get_check_runs"` and the repository owner, name, and PR number. It returns check runs for the PR head commit; use optional pagination to retrieve more results.

Examples:

```
pull_request_read({"method":"get_check_runs","owner":"<owner>","repo":"<repo>","pullNumber":<pull-number>})
```

- why_it_matters: Inspect check runs while working on a repository through github-mcp-server.
- sources: <https://github.com/github/github-mcp-server/releases/tag/v0.32.0>, <https://github.com/github/github-mcp-server/blob/v0.32.0/pkg/github/pullrequests.go>
- gotchas: "Version: v0.32.0"; "method (required): Set to `get_check_runs`."; "owner (required): Repository owner."; "repo (required): Repository name."; "pullNumber (required): Pull request number."; "page: Page number for pagination; minimum 1."; "perPage: Results per page; minimum 1, maximum 100."; "Prerequisite: The `pull_request_read` tool requires the `Repo` scope."

## github-mcp-server set_issue_fields updates granular issue field values (github-mcp-server, 2026-04-16)
Published 2026-10-13
- slug: github-mcp-server-set-issue-fields-updates-granular-issue-field-values-ad5da4b719e8
- score: 0.91

How to use it:

When setting, updating, or deleting an organization-level custom field value on an issue, enable `issues_granular` and call `set_issue_fields` with the repository, issue number, and field value. The v1.0.0 release documents the flag; its tool schema is in the tagged source snapshot.

Examples:

```
set_issue_fields({"owner":"<owner>","repo":"<repo>","issue_number":<issue-number>,"fields":[{"field_id":"<field-node-id>","text_value":"<value>"}]})
```

```
set_issue_fields({"owner":"<owner>","repo":"<repo>","issue_number":<issue-number>,"fields":[{"field_id":"<field-node-id>","delete":true}]})
```

- why_it_matters: Set or update an organization-level custom field value on an issue.
- sources: <https://github.com/github/github-mcp-server/releases/tag/v1.0.0>, <https://github.com/github/github-mcp-server/blob/v1.0.0/pkg/github/__toolsnaps__/set_issue_fields.snap>
- gotchas: "Version: 1.0.0"; "Availability: Feature flagged under `issues_granular`."; "issues_granular (required): Feature flag for the granular Issues toolset containing `set_issue_fields`."; "owner (required): Repository owner username or organization."; "repo (required): Repository name."; "issue_number (required): Issue number to update; minimum 1."; "fields (required): Nonempty array of field values. Each item requires `field_id` and takes the value key matching the field type, or `delete: true` to remove the value."; "field_id (required): GraphQL node ID of the issue field."; "text_value: Value for a text field."; "number_value: Value for a number field."; "date_value: ISO 8601 date string for a date field."; "single_select_option_id: GraphQL node ID of the option for a single-select field."; "delete: Set true to remove the field value."; "Prerequisite: Enable the `issues_granular` feature flag."; "Applies to organization-level custom field values on issues."

## github-mcp-server issue fields support (github-mcp-server, 2026-05-28)
Published 2026-10-13
- slug: github-mcp-server-issue-fields-support-372c253ae98b
- score: 0.92

How to use it:

When `remote_mcp_issue_fields` is enabled, list fields with `list_issue_fields`, filter issues with `list_issues.field_filters`, and read or write field values with `issues.read` and `issues.write`. To suggest a type change, use the documented suggestion flag if available; the current tool reference calls it `is_suggestion`.

Examples:

```
list_issue_fields({"owner":"<owner>","repo":"<repo>"})
```

```
list_issues({"owner":"<owner>","repo":"<repo>","field_filters":[{"field_name":"<field name>","value":"<value>"}]})
```

```
issue_write({"owner":"<owner>","repo":"<repo>","issue_number":<number>,"issue_fields":[{"field_name":"<field name>","value":"<value>"}]})
```

- why_it_matters: Inspect and update issues using custom issue fields, or filter an issue search by their values.
- sources: <https://github.com/github/github-mcp-server/releases/tag/v1.1.0>, <https://github.com/github/github-mcp-server?locale=en-US>, <https://github.com/github/github-mcp-server/blob/main/docs/feature-flags.md>
- gotchas: "Version: v1.1.0"; "Availability: Issue field support is behind the `remote_mcp_issue_fields` feature flag and enabled automatically in Insiders Mode."; "list_issue_fields.owner (required): Repository or organization owner."; "list_issue_fields.repo: Repository; when omitted, returns organization-level fields."; "list_issues.owner (required): Repository owner."; "list_issues.repo (required): Repository name."; "list_issues.field_filters: Array of field_name/value filters; the server coerces values to the field type."; "issue_fields: Array of field updates; each item needs field_name and exactly one of value, field_option_name, or delete:true."; "issue_fields.field_name (required): Name of the issue field to set or clear."; "issue_fields.value: Value for the field; mutually exclusive with field_option_name and delete:true."; "issue_fields.field_option_name: Single-select option name; mutually exclusive with value and delete:true."; "issue_fields.delete: Set true to clear the field; mutually exclusive with value and field_option_name."; "issue_write.is_suggestion: Current reference flag for recording an issue type change as a suggestion rather than applying it."; "Prerequisite: Issue field features are gated by `remote_mcp_issue_fields`; the release note says they are enabled automatically in Insiders Mode."; "Prerequisite: `list_issue_fields` requires OAuth scope `repo` or `read:org`; `list_issues` and issue writing require `repo`."; "Docs conflict: The release note names a `suggest` bool flag for type changes; current official feature documentation names the flag `is_suggestion`. Confirm the server version's tool schema before using it."

## github-mcp-server paginate GHAS alert listings (github-mcp-server, 2026-05-28)
Published 2026-10-13
- slug: github-mcp-server-paginate-ghas-alert-listings-3b4598b7462b
- score: 0.97

How to use it:

When reviewing a repository’s GHAS alerts, call the relevant listing tool with `owner`, `repo`, `page: 2`, and `perPage: 100`; continue with later page numbers to retrieve beyond the first page.

Examples:

```
{"tool":"list_code_scanning_alerts","arguments":{"owner":"<owner>","repo":"<repo>","page":2,"perPage":100}}
```

```
{"tool":"list_dependabot_alerts","arguments":{"owner":"<owner>","repo":"<repo>","page":2,"perPage":100}}
```

```
{"tool":"list_secret_scanning_alerts","arguments":{"owner":"<owner>","repo":"<repo>","page":2,"perPage":100}}
```

- why_it_matters: Review all code scanning, Dependabot, or secret scanning alerts for a repository with a large backlog.
- before: The tools previously returned only the first page; v1.1.0 added pagination to retrieve beyond it.
- sources: <https://github.com/github/github-mcp-server/releases/tag/v1.1.0>, <https://github.com/github/github-mcp-server/blob/v1.1.0/README.md>
- gotchas: "Version: v1.1.0"; "owner (required): Repository owner."; "repo (required): Repository name."; "page: Page number for pagination; minimum 1."; "perPage: Results per page; minimum 1, maximum 100."; "Prerequisite: The listing tools require the `security_events` OAuth scope; `repo` is also accepted."

## github-mcp-server search_commits (github-mcp-server, 2026-05-28)
Published 2026-10-13
- slug: github-mcp-server-search-commits-597a0158ff0f
- score: 0.97

How to use it:

When debugging, auditing, or investigating a release, search commits with `search_commits` using GitHub commit search syntax. Include a scope qualifier such as `repo:<owner>/<repo>` in the required `query`.

Examples:

```
search_commits({"query":"repo:<owner>/<repo> fix panic","page":1,"perPage":30})
```

- why_it_matters: Find commits relevant to debugging, auditing, or investigating a release.
- before: List repository commits and use that listing to find specific commits.
- sources: <https://github.com/github/github-mcp-server/releases/tag/v1.1.0>, <https://github.com/github/github-mcp-server/blob/v1.1.0/README.md>
- gotchas: "Version: v1.1.0"; "query (required): Commit search REST query. Use `repo:owner/repo`, `org:`, or `user:` to scope; supports author, committer, date, merge, hash, tree, parent, and `is:public` qualifiers. Searches commit messages on the default branch only."; "page: Page number, minimum 1."; "perPage: Results per page, from 1 to 100."; "order: Sort order."; "sort: Sort by author or committer date; defaults to best match."; "Prerequisite: The tool requires OAuth scope `repo`."; "Search uses GitHub search syntax."

## github-mcp-server get_commit adds include_patch parameter (github-mcp-server, 2026-06-08)
Published 2026-10-13
- slug: github-mcp-server-get-commit-adds-include-patch-parameter-7ed4f0d355e0
- score: 0.95

How to use it:

When reviewing a repository change and you need the patch, call `get_commit` with the repository owner, name, commit SHA, and `detail: "full_patch"`.

Examples:

```
get_commit(owner: "<owner>", repo: "<repo>", sha: "<commit-sha>", detail: "full_patch")
```

- why_it_matters: Retrieve commit details while reviewing a repository change where the patch is needed.
- sources: <https://github.com/github/github-mcp-server/releases/tag/v1.2.0>, <https://github.com/github/github-mcp-server/blob/v1.2.0/README.md>
- gotchas: "Version: v1.2.0"; "owner (required): Repository owner."; "repo (required): Repository name."; "sha (required): Commit SHA, branch name, or tag name."; "detail: Use `full_patch` to include unified diff content for each changed file; it can be very large. Default is `stats`."; "Prerequisite: The tool requires the `repo` OAuth scope."; "Docs conflict: The v1.2.0 README documents optional `detail` (`none`, `stats`, `full_patch`) and does not document `include_patch`; this differs from the release note's named parameter. Use the documented `detail: \"full_patch\"` form for v1.2.0."

Next: https://sincecutoff.com/v1/changes.md?tool=github-mcp-server&score=0&cursor=eyJzY29yZSI6MCwic2VxIjo1MTIsInNpbmNlIjpudWxsLCJ0b29sIjoiZ2l0aHViLW1jcC1zZXJ2ZXIiLCJ2IjoxfQ
Save `next_cursor`; next visit, pass it to get only what was published since.
<!-- end of page -->