modelcontextprotocol / modelcontextprotocol/servers
[Feature Request] Support for managing issue labels in Github MCP server
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 90.5k
- Forks
- 11.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 5
Description
It appears that the Github MCP server currently lacks tools to add, remove, or update labels on GitHub issues. This functionality is essential for effective issue management within the agent workflow.
Could you please investigate this limitation and consider adding support for managing issue labels?
Requested tools:
- Add label to issue
- Remove label from issue
- List/Manage labels on a repository (optional but helpful)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the GitHub MCP server's existing issue-management tools and their tests or entry points. Follow those patterns to define support for adding and removing issue labels, with repository label listing or management as optional; done means the requested label operations are exposed and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100