GitHub Projects fields resolve by name
Introduced 2026-07-15 · score 0.92
HOW TO USE IT
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"]})projects_get({"method":"get_project_item","owner":"<owner>","project_number":<project_number>,"item_id":<item_id>,"field_names":["Status","Priority"]})projects_write({"method":"update_project_item","owner":"<owner>","project_number":<project_number>,"item_owner":"<item_owner>","item_repo":"<item_repo>","issue_number":<issue_number>,"updated_field":{"name":"Status","value":"In Progress"}})WHY THIS HELPS
Work with GitHub Projects fields through github-mcp-server when field names are used for resolution.
BEFORE THIS CHANGE
The PR states that updates previously required field and item IDs and did not resolve option names; reading item field values required listing project fields first.
REQUIREMENTS AND LIMITATIONS
- Version: v1.6.0
- projects_list.method (required): Use `list_project_items` to list items.
- projects_list.owner (required): Project owner login.
- projects_list.project_number (required): Project number for `list_project_items`.
- projects_list.field_names: Field names to include; mutually exclusive with `fields`.
- projects_get.method (required): Use `get_project_item` to get an item.
- projects_get.item_id (required): Project item ID for `get_project_item`.
- projects_get.field_names: Field names to include; mutually exclusive with `fields`. Without either, only title is included.
- projects_write.method (required): Use `update_project_item` to update an item.
- projects_write.owner (required): Project owner login.
- projects_write.project_number (required): Project number; required for methods other than `create_project`.
- projects_write.updated_field (required): Field and new value; accepts `{name, value}` or `{id, value}`. For single-select fields, name form resolves option names; set value to null to clear.
- updated_field.name: Field name; use instead of `id`. The `name` and `id` forms are mutually exclusive.
- updated_field.value (required): New field value; null clears the field.
- projects_write.item_id: Project item ID; provide this or the `item_owner` + `item_repo` + `issue_number` reference to resolve an item for update.
- projects_write.item_owner: Issue or pull request repository owner when resolving the item by issue number.
- projects_write.item_repo: Issue or pull request repository name when resolving the item by issue number.
- projects_write.issue_number: Issue number used with `item_owner` and `item_repo` to resolve the item.
- Prerequisite: Project reads require `read:project` scope (the docs also accept `project`); updates require `project` scope.
FIRST-PARTY EVIDENCE
- https://github.com/github/github-mcp-server/releases/tag/v1.6.0
- https://github.com/github/github-mcp-server/blob/v1.6.0/README.md
- https://github.com/github/github-mcp-server/pull/2760
Check the installed version and the source before using it. Entry JSON