[FEATURE] Support GitHub Projects v2 (add items, set fields/Status) in Claude Code web + Claude GitHub App

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Agents in hosted Claude Code web sessions can create GitHub issues but cannot place them on a
Projects v2 board or set fields like Status — board placement is fully manual. We run an
issue-driven workflow where every new issue must land on our org Project board with
Status: Ready to be pickable, so today every agent-filed issue needs a manual UI follow-up.

Two confirmed gaps:

1. MCP toolset not exposed — the github MCP server in hosted sessions exposes no Projects v2

tools (no list_projects, add_project_item, update_project_item_field, etc.); the projects
toolset appears disabled. Projects v2 is GraphQL-only (no REST fallback), so there is no
workaround from the available tool surface.

1. App permission not requested — the Claude GitHub App's installation does not include

organization "Projects: Read and write". Because a GitHub App's permission set is declared by
the developer, an org owner cannot grant it from installation settings (there's no toggle). So
even with tools enabled, the credential would lack scope.

Proposed Solution

• Enable the github MCP projects toolset in hosted sessions.
• Add org "Projects: Read and write" to the Claude GitHub App's requested permissions.

Together these would let an agent add an item to a Projects v2 board and set its fields
(e.g. move it to Status: Ready) without a human following up in the UI.

Alternative Solutions

• Track workflow state via issue labels/milestones instead of the board — works, but duplicates

data that already exists correctly on the board.

• Manual UI follow-up after every agent-created issue — the current workaround, but defeats the

point of an agent-driven issue queue.

Priority

Medium - Would be very helpful

Feature Category

MCP server integration

Use Case Example

An agent in a hosted Claude Code web session, working an issue-driven pipeline, discovers new
scope and needs to file it as a GitHub issue. Today it can create the issue, but cannot add it to
the org's Projects v2 board or set Status: Ready, so the issue is invisible to the board-driven
queue until a human manually adds it. With this feature, the agent could add the item and set its
Status directly, making the issue immediately pickable.

Additional Context

Related to #77971, which reported the missing MCP toolset for Claude Routines specifically and
was auto-closed as stale (not planned) rather than resolved — its own closing comment invites a
new issue if still relevant. This report adds the second, separate gap (the GitHub App's missing
org Projects permission) that blocks the same capability even if the toolset were enabled.

Environment: Claude Code on the web; Claude GitHub App installed org-wide (All repositories); org
Project board used as the work queue.