GitHub Discovery MCP Server
Related Servers
Alternatives to GitHub Discovery MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides read-only tools to search public GitHub repositories, retrieve repository details, READMEs, contributors, and commit activity, and compare up to 10 repositories side by side.MIT
- FlicenseNot gradedqualityDmaintenanceEnables natural language queries to search GitHub for trending repositories by topic, summarize project READMEs, and compare multiple repos to uncover ecosystem patterns.2-
- AlicenseAqualityDmaintenanceEnables querying GitHub repositories for pull requests, commits, and comparisons to understand code changes.59 npmApache 2.0
- FlicenseAqualityCmaintenanceEnables interaction with GitHub repositories, issues, pull requests, code search, branches, and GitHub Actions workflows.87 npm-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to analyze GitHub repositories, including fetching repository details, searching, and retrieving README content.379 npm2ISC
- FlicenseAqualityDmaintenanceEnables natural-language queries about public GitHub repositories, including issues, pull requests, repo metadata, and READMEs, via the GitHub API.5-
TDQS
Scored across 9 tools
Each tool targets a distinct stage: searching, topic filtering, trending, overview, structure, comparison, file content, commits, and branches. The two search tools are differentiated by free-text vs. curated topic tags, so an agent can choose without confusion.
Tool names consistently follow a snake_case verb_noun pattern: search_, get_, compare_, and list_. The small variation in search_github_repos vs. search_by_topic does not break the overall predictability.
Nine tools is well-scoped for a GitHub discovery server. Each tool earns its place in the workflow from finding repositories to inspecting their internals, without redundant or excessive surface area.
The tool set covers the full discovery lifecycle: find candidates via search/topic/trending, evaluate them via overview/compare, and explore details via structure/file/commits/branches. There are no obvious dead ends or missing operations for the server's stated purpose.