github-repo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QDRANT_URL | No | Qdrant Cloud URL for vector storage, used by the 'ask_repo' tool. | |
| GITHUB_TOKEN | No | GitHub personal access token for higher API rate limits (optional, but recommended; no scopes needed for public repo data). | |
| QDRANT_API_KEY | No | Qdrant API key for vector storage, used by the 'ask_repo' tool. | |
| VOYAGE_API_KEY | No | Voyage AI API key for embeddings, used by the 'ask_repo' tool. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_repo_healthA | Computes a maintenance-health score (0-100) for a public GitHub repo from commit recency, issue-triage ratio, and contributor diversity. Use this before deciding whether to depend on or contribute to a repo. |
| summarize_recent_commitsB | Fetches commits from the last N days and groups them by type (feature/fix/docs/refactor/chore) so an agent can describe what changed without reading raw commit logs. |
| find_good_first_issuesA | Finds open issues labeled for beginners/first-time contributors, then scores each for genuine clarity of scope and flags ones that look mislabeled (e.g. touches core architecture despite the 'good first issue' label). |
| ask_repoA | Answers a free-text question about a repo via embeddings-based semantic search over its README, docs/*.md, and top issue threads. Use this for questions the other structured tools can't answer directly, e.g. 'does this support TypeScript?' or 'how do I configure X?' Requires VOYAGE_API_KEY and QDRANT_URL/QDRANT_API_KEY to be set. |
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 4 tools
Each tool targets a clearly distinct purpose: health scoring, commit summarization, beginner-issue discovery, and semantic Q&A. There is no meaningful overlap—ask_repo explicitly serves as a fallback for questions the structured tools cannot answer.
All tool names use lowercase snake_case and follow a predictable verb-first pattern: get_, summarize_, find_, ask_. The consistency makes it easy to infer each tool's action at a glance.
Four tools is a well-scoped count for a focused repository-analysis server. Each tool covers a distinct aspect of evaluating or exploring a repo, and none feel redundant or missing from the apparent purpose.
The server covers the core repo-evaluation workflow well: health, recent changes, contribution entry points, and open-ended questions. Minor gaps exist, such as structured access to license, stars, or PR activity, but ask_repo can work around many of these.