github-issue-tracker-aroy
This MCP server connects to GitHub repositories to manage issues programmatically. It supports listing open issues, creating new ones with titles and labels, updating statuses, and closing resolved issues via API calls. Developers and repository maintainers use it for automating triage, bug reporting from CI/CD pipelines, and workflow integrations.
Overview
The github-issue-tracker-aroy MCP server provides direct API access to GitHub's issue tracking features. It allows MCP clients to perform read and write operations on issues within specified repositories, using GitHub's REST API under the hood. This enables scripted management without needing full GitHub CLI or SDK setups.
Key Capabilities
- list_issues: Fetches issues for a repository, filtered by state (open/closed), labels, or assignee.
- create_issue: Creates a new issue with title, body, labels, and assignees.
- get_issue: Retrieves full details of a specific issue by number.
- update_issue: Modifies issue title, body, state, labels, or assignees.
- close_issue: Marks an issue as closed with optional comment.
These functions handle authentication via GitHub tokens and support pagination for large repositories.
Use Cases
- CI/CD Bug Filing: In a failed build pipeline, use create_issue to automatically open a bug issue with logs attached to the body.
- Daily Issue Reports: Run list_issues nightly to generate summaries of open issues and email teams.
- Triage Automation: Query list_issues with label filters, then use update_issue to reassign high-priority bugs.
- Migration Scripts: Bulk close_issue on resolved issues during repo cleanups.
Who This Is For
Repository maintainers, DevOps engineers, and automation scripters who need to integrate GitHub issue management into custom tools, bots, or pipelines. Suited for teams handling multiple repos where manual GitHub UI access is inefficient.