github-mcp-server issue fields support
Introduced 2026-05-28 · 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`.
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 THIS HELPS
Inspect and update issues using custom issue fields, or filter an issue search by their values.
REQUIREMENTS AND LIMITATIONS
- 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.
FIRST-PARTY EVIDENCE
- 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
Check the installed version and the source before using it. Entry JSON