GitHub Repository Health MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROQ_MODEL | Yes | The Groq model to use, e.g., openai/gpt-oss-120b. | |
| GITHUB_REPO | Yes | The GitHub repository name. | |
| GITHUB_OWNER | Yes | The GitHub owner or organization. | |
| GITHUB_TOKEN | No | Optional GitHub personal access token for higher rate limits. | |
| GROQ_API_KEY | Yes | Your Groq API key. |
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 |
|---|---|
| get_repository_infoC | Get current metadata and activity counters for a GitHub repository. |
| get_open_issuesA | Get open issues, excluding pull requests, for a GitHub repository. |
| get_recent_commitsA | Get recent commits and their authors for a GitHub repository. |
| get_workflow_runsB | Get recent GitHub Actions workflow runs and their conclusions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| daily_health_report | Create a prompt for a current GitHub repository health report. |
| triage_open_issues | Create a prompt for prioritizing a repository's open issues. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct aspect of repository health: metadata, issues, commits, and workflow runs. There is no overlap or ambiguity between them.
All four tools follow a consistent get_<resource>_<detail> pattern with snake_case naming. The naming is predictable and easy to extend.
Four tools is well-scoped for a read-only repository health MCP. Each tool covers a meaningful health signal without unnecessary redundancy.
The core health indicators—repo stats, issues, commits, and CI status—are covered. Pull request activity and contributor trends are notable omissions, but the current surface is sufficient for basic health assessments.