A
licenseB
qualityB
maintenanceEnables AI assistants to query GitHub repository insights such as health, commit activity, stale pull requests, contributor stats, releases, and issue backlogs through MCP tools.
6
MIT
github-repo-mcp-server
by technomad641
Related Servers
Alternatives to github-repo-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered GitHub interactions including repository analysis, code search, PR reviews, and more through the MCP protocol.4MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to discover and interact with GitHub repositories through standardized MCP tools, allowing exploration and retrieval of project information without direct API calls.-
- FlicenseNot gradedqualityCmaintenanceEnables large language models to explore, inspect, and analyze GitHub repositories through natural-language queries, using MCP tools to retrieve repository data, file structures, file contents, and code search results from the GitHub REST API.-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with GitHub repositories and issues through MCP tools, supporting listing repositories, listing and searching issues, and retrieving specific issues via the GitHub REST API.-
- FlicenseCqualityCmaintenanceExposes GitHub repository data via MCP tools, a resource, and a prompt, enabling repo summaries, issue/PR listing, keyword search, and repo health review.4-
TDQS
A3.8/5.0
Scored across 14 tools
Disambiguation5/5
Each tool has a clearly distinct purpose. Getter vs. list tools are separated by singular/plural semantics, and the two search tools differ by target (code within a repo vs. trending repos across GitHub). No two tools overlap in function.
Naming Consistency5/5
All tool names use lowercase with underscores and follow a consistent verb_noun pattern (get_, list_, search_, ping). The pattern is predictable and easy to infer from the resource being accessed.
Tool Count5/5
14 tools is well within the ideal range for a GitHub-focused server. Each tool covers a distinct resource or operation, and the count feels appropriate for the scope—not bloated, not too sparse.
Completeness3/5
The read-side surface is solid: repos, issues, PRs, branches, commits, files, workflows, notifications, and trending. However, there are no create/update/delete operations for any resource, which is a significant gap if the server is expected to support full issue/PR lifecycle management. Agents can work around this only if their tasks are read-only.
Maintenance
ActivityStale
ResponsivenessNo issues