Problem
The GitHub MCP server currently exposes label read operations (e.g. get_label) and issue labeling via issue_write, but it does not expose label management APIs. This blocks automation like bootstrapping repo-wide SDLC labels (stream/, p, state/, type/).
Why this should be supported
GitHub’s REST API supports labels management (create/update/delete labels) and organizations/maintainers commonly need to bootstrap consistent label taxonomies.
Requested MCP capabilities
- Create label (name, color, description)
- Update label (rename, recolor, description)
- Delete label
- List labels (already indirectly possible via search, but a first-class list would help)
Example use case
Repo needs to bootstrap these labels:
stream/core-loop, stream/bench-datasets, stream/ttmetal
p1, p2, p3, next
type/bug, type/feature, type/chore, type/docs, type/research
state/draft, state/to-research, state/spec-ready, state/ready, state/in-progress, state/blocked, state/in-review, state/done
Acceptance criteria
- A user can create/update/delete labels via MCP without needing
gh CLI or manual UI steps.
Problem
The GitHub MCP server currently exposes label read operations (e.g.
get_label) and issue labeling viaissue_write, but it does not expose label management APIs. This blocks automation like bootstrapping repo-wide SDLC labels (stream/, p, state/, type/).Why this should be supported
GitHub’s REST API supports labels management (create/update/delete labels) and organizations/maintainers commonly need to bootstrap consistent label taxonomies.
Requested MCP capabilities
Example use case
Repo needs to bootstrap these labels:
stream/core-loop,stream/bench-datasets,stream/ttmetalp1,p2,p3,nexttype/bug,type/feature,type/chore,type/docs,type/researchstate/draft,state/to-research,state/spec-ready,state/ready,state/in-progress,state/blocked,state/in-review,state/doneAcceptance criteria
ghCLI or manual UI steps.