github-repo-mcp
Related Servers
Alternatives to github-repo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to perform GitHub analytics and management tasks, including repository analysis, PR summarization, issue triage, release notes generation, and contributor statistics.44 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables Large Language Models to analyze GitHub repositories in real-time, providing tools for retrieving repository information, analyzing issues, accessing documentation, and visualizing activity.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with GitHub repositories, issues, pull requests, code, and more through a comprehensive set of tools.-
- AlicenseNot gradedqualityDmaintenanceEnables Claude to analyze GitHub repositories with tools for health scoring, contributor analysis, issue tracking, code search, and more.MIT
- AlicenseAqualityCmaintenanceConnects LLMs and AI agents directly to GitHub repositories, enabling repository inspection, file and tree exploration, code search, commit history, issues, pull requests, and releases for both public and private repos.13MIT
- FlicenseNot gradedqualityCmaintenanceEnables autonomous coding agents to inspect Git commits, create pull requests, parse issue threads, and post reviews on GitHub repositories.-
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.