github-ops-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub personal access token for higher rate limits and write operations. If not provided, the client works unauthenticated for public repos (60 req/hr). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| triage_issuesB | Find issues missing labels, assignees, or milestones. Use this to identify untriaged work. |
| bulk_label_issuesC | Apply a label to all issues matching a text filter. Defaults to dry-run mode. |
| stale_issue_reportB | Find issues with no activity in N days, grouped by label and assignee. |
| close_resolved_issuesB | Bulk-close issues with a specific label that are older than N days. Defaults to dry-run mode. |
| pr_review_dashboardA | Show open PRs grouped by review status (awaiting, changes requested, approved) with wait times. |
| stale_pr_reportB | Find pull requests with no activity in N days. |
| pr_check_statusA | Aggregate CI/check status across all open PRs — quick 'is anything red' overview. |
| repo_health_auditA | Audit a repo for operational hygiene: branch protection, CODEOWNERS, CI, license, security policy. |
| repo_compareC | Compare health audit results across multiple repos to find inconsistencies. |
| team_access_reviewB | List users and their permission levels for a repo or org. Shows who has admin, write, or read access. |
| permission_auditC | Audit an org for permission issues: outside collaborators, direct access bypassing teams. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a distinct operational task on GitHub, such as labeling, closing, auditing, or reviewing. Even similar tools like stale_issue_report and triage_issues address different aspects (activity vs. metadata gaps), so there is no risk of confusion.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., bulk_label_issues, repo_health_audit, team_access_review). The naming is predictable and clear.
Eleven tools is an ideal size for a focused operations server, covering a range of common GitHub management tasks without being overwhelming or underdeveloped.
The tool set covers essential ops workflows: bulk actions, audits, stale management, and triage. Minor gaps exist (e.g., no tool for bulk commenting or branch management), but the core ops surface is well-covered.