Add ProjectV2 status update tools (list, get, create) #1987

e-straight · 2026-02-10T02:59:13Z

Summary

Add three new tools for managing GitHub ProjectV2 status updates (list, get, create), wired into both individual and consolidated project tools.

Why

Fixes #1963

What changed

Add list_project_status_updates tool (+ projects_list method): list status updates with pagination, ordered by creation date descending
Add get_project_status_update tool (+ projects_get method): fetch a single status update by node ID
Add create_project_status_update tool (+ projects_write method): create a status update with optional body, status, start_date, and target_date
Add GraphQL types/queries (statusUpdateNode, statusUpdatesUserQuery, statusUpdatesOrgQuery, statusUpdateNodeQuery) supporting both user-owned and org-owned projects
Add CreateProjectV2StatusUpdateInput locally (not in shurcooL/githubv4 library)
Add MinimalProjectStatusUpdate response type in minimal_types.go
Add deprecated tool aliases for all three new individual tools
Extract resolveProjectNodeID helper to deduplicate ~70 lines of project ID resolution logic shared between addProjectItem and createProjectStatusUpdate
Add client-side YYYY-MM-DD date format validation for start_date and target_date
Fix brittle node type check in getProjectStatusUpdate (was stringifying githubv4.ID and comparing to "<nil>")
Refactor createProjectStatusUpdate to accept typed parameters instead of raw args map[string]any
Add ProjectResolveIDFailedError constant for consistent error reporting
Add toolset instructions for the new status update tools
21 new test subtests covering user/org paths, pagination, error handling, input validation, field verification, and consolidated tool dispatch

MCP impact

New tool added — three new individual tools (list_project_status_updates, get_project_status_update, create_project_status_update) and three new methods on the consolidated tools (projects_list, projects_get, projects_write)

Prompts tested (tool changes only)

"List the recent status updates for project number 5 in octo-org"
"Get the status update with ID PVTSU_abc123"
"Create a status update for project 2 owned by octocat with status ON_TRACK and body 'Sprint 3 is going well'"
"Post an AT_RISK status update for the org project with start date 2026-01-01 and target date 2026-06-30"

Security / limits

Data exposure, filtering, or token/size limits considered — per_page is capped to MaxProjectsPerPage (50). Date inputs are validated client-side before hitting the API. Status values are validated against an allowlist.

Tool renaming

I am renaming tools as part of this PR (e.g. a part of a consolidation effort)
- I have added the new tool aliases in deprecated_tool_aliases.go

Lint & tests

Linted locally with ./script/lint
Tested locally with ./script/test

Docs

Updated (README / docs / examples) — script/generate-docs run, README.md and docs/tool-renaming.md updated

Closes github#1963 Add three new individual tools and wire them into the consolidated project tools for managing GitHub ProjectV2 status updates: - list_project_status_updates / projects_list: List status updates for a project with pagination, ordered by creation date descending - get_project_status_update / projects_get: Fetch a single status update by node ID - create_project_status_update / projects_write: Create a status update with optional body, status, start_date, and target_date New GraphQL types and queries (statusUpdateNode, statusUpdatesUserQuery, statusUpdatesOrgQuery, statusUpdateNodeQuery) support both user-owned and org-owned projects. The CreateProjectV2StatusUpdateInput type is defined locally since the shurcooL/githubv4 library does not include it. Also includes quality improvements discovered during implementation: - Extract resolveProjectNodeID helper to deduplicate ~70 lines of project ID resolution logic shared between addProjectItem and createProjectStatusUpdate - Add client-side YYYY-MM-DD date format validation for start_date and target_date fields before sending to the API - Fix brittle node type check in getProjectStatusUpdate that relied on stringifying a githubv4.ID and comparing to "<nil>" - Refactor createProjectStatusUpdate to accept typed parameters instead of raw args map - Add deprecated tool aliases for all three new individual tools - Add ProjectResolveIDFailedError constant for consistent error reporting Test coverage includes 21 subtests covering both user and org paths, pagination, error handling, input validation, field verification, and consolidated tool dispatch.

Copilot

Pull request overview

Adds ProjectV2 status update support to the GitHub MCP Server by introducing dedicated tools and integrating them into the consolidated projects_* tools, enabling listing, fetching, and creating ProjectV2 status updates via GraphQL.

Changes:

Added three new tools: list_project_status_updates, get_project_status_update, and create_project_status_update, plus consolidated-tool dispatch support.
Introduced new minimal response type(s) and GraphQL query/mutation structs (including a locally-defined CreateProjectV2StatusUpdateInput).
Added extensive unit test coverage and updated docs/toolsnaps/tool aliases accordingly.

Reviewed changes

Copilot reviewed 14 out of 14 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
pkg/github/projects.go	Implements GraphQL types/queries/mutation + new tools and consolidated dispatch wiring.
pkg/github/minimal_types.go	Adds `MinimalProjectStatusUpdate` response type.
pkg/github/tools.go	Registers the new tools in the tool inventory.
pkg/github/toolset_instructions.go	Updates projects toolset instructions to mention status update workflows.
pkg/github/deprecated_tool_aliases.go	Adds deprecated aliases mapping new individual tools to consolidated tools.
pkg/github/projects_test.go	Adds comprehensive tests for new tools + consolidated dispatch paths.
pkg/github/toolsnaps/*.snap	Updates/creates tool schema snapshots for new/updated tools.
docs/tool-renaming.md	Documents the new deprecated aliases.
README.md	Updates generated docs sections for consolidated tool schema changes.

Comments suppressed due to low confidence (1)

pkg/github/projects.go:2450

getProjectStatusUpdate checks q.Node.StatusUpdate.ID == nil, but githubv4.ID cannot be compared to nil (it’s a string alias), which will not compile. Use an empty-string/zero-value check (or make the field a pointer type if you truly need nil semantics) to detect a missing inline-fragment match.

	if q.Node.StatusUpdate.ID == nil || q.Node.StatusUpdate.ID == "" {
		return utils.NewToolResultError(fmt.Sprintf("%s: node is not a ProjectV2StatusUpdate or was not found", ProjectStatusUpdateGetFailedError)), nil, nil
	}

pkg/github/projects.go

Copilot · 2026-02-10T03:02:58Z

pkg/github/projects.go

+type statusUpdateNode struct {
+	ID         githubv4.ID
+	Body       githubv4.String
+	Status     githubv4.String
+	CreatedAt  githubv4.DateTime
+	StartDate  githubv4.String
+	TargetDate githubv4.String
+	Creator    struct {
+		Login githubv4.String
+	}
+}


statusUpdateNode uses non-pointer githubv4.String fields for values that are optional in the API (e.g., body/status/startDate/targetDate are optional in the mutation, so they can come back as null). If the GraphQL response contains null, JSON unmarshalling into a non-pointer string type will fail at runtime. Use pointer fields for nullable values (e.g., *githubv4.String) and update convertToMinimalStatusUpdate to handle nils safely.

This is a good feedback but I have another question: can we use a struct ProjectV2StatusUpdate from go-github? It contains a few more fields but we won't be duplicating structs in github-mcp-server.

In response to copilot's feeback:
Fixed in cc7d9a8: Body, Status, StartDate, and TargetDate are now *githubv4.String, and convertToMinimalStatusUpdate uses a derefString helper to handle nils safely.

@JoannaaKL to your point:
Looking it over, ProjectV2StatusUpdate does exist in go-github, but it was introduced after v79, which I think we are on here (https://github.com/github/github-mcp-server/blob/main/go.mod#L6). ProjectV2StatusUpdate is available starting in v81 (introduced in google/go-github#3888). Let me know how you want me to proceed.

Update: I dug into this further. The latest version of go-github is actually v82, but even at v82 the ProjectV2StatusUpdate struct only exists as a type definition. There are no service methods for listing, getting, or creating status updates. It only surfaces as a nested field on ProjectV2.LatestStatusUpdate when fetching a project. You can see the full ProjectsService on master here: https://github.com/google/go-github/blob/master/github/projects.go. So even with a bump to v81/v82, we'd still need the GraphQL approach via githubv4 for list/get/create operations.

Hey - I just bumped google/go-github so we have this struct now. And yes, we can just use the struct from it and functions you created. :)

pkg/github/projects.go

Loosen projects_get schema to only require "method", since get_project_status_update only needs status_update_id and never uses owner or project_number. Also use pointer types for optional statusUpdateNode fields, add owner_type validation for list/create status updates, clamp negative per_page values, and fix resolveProjectNodeID to return "" instead of nil on error.

e-straight requested a review from a team as a code owner February 10, 2026 02:59

Copilot AI review requested due to automatic review settings February 10, 2026 02:59

Copilot started reviewing on behalf of e-straight February 10, 2026 02:59 View session

Copilot AI reviewed Feb 10, 2026

View reviewed changes

e-straight force-pushed the add-project-status-updates branch from 8196111 to ad3fcf5 Compare February 10, 2026 03:03

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add ProjectV2 status update tools (list, get, create) #1987

Add ProjectV2 status update tools (list, get, create) #1987

e-straight commented Feb 10, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Copilot AI Feb 10, 2026

Uh oh!

JoannaaKL Feb 11, 2026

Uh oh!

e-straight Feb 11, 2026

Uh oh!

e-straight Feb 11, 2026

Uh oh!

e-straight Feb 12, 2026

Uh oh!

JoannaaKL Feb 12, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Add ProjectV2 status update tools (list, get, create) #1987

Are you sure you want to change the base?

Add ProjectV2 status update tools (list, get, create) #1987

Conversation

e-straight commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Why

What changed

MCP impact

Prompts tested (tool changes only)

Security / limits

Tool renaming

Lint & tests

Docs

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Copilot AI Feb 10, 2026

Choose a reason for hiding this comment

Uh oh!

JoannaaKL Feb 11, 2026

Choose a reason for hiding this comment

Uh oh!

e-straight Feb 11, 2026

Choose a reason for hiding this comment

Uh oh!

e-straight Feb 11, 2026

Choose a reason for hiding this comment

Uh oh!

e-straight Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

JoannaaKL Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

e-straight commented Feb 10, 2026 •

edited

Loading