github-mcp-server set_issue_fields updates granular issue field values
Introduced 2026-04-16 · 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.
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 THIS HELPS
Set or update an organization-level custom field value on an issue.
REQUIREMENTS AND LIMITATIONS
- 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.
FIRST-PARTY EVIDENCE
- 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
Check the installed version and the source before using it. Entry JSON