F
licenseNot graded
qualityB
maintenanceEnables 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.
-
github-updates
by Soller211
Related Servers
Alternatives to github-updates
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to manage GitHub issues by listing, creating, searching, and commenting on them through MCP.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to list, search, and inspect issues on any public GitHub repository via natural language.MIT
- AlicenseAqualityBmaintenanceLets agents read a GitHub repository's live issues through read-only tools for listing, filtering, fetching details with comments and cross-references, searching, and exploring labels and milestones, with transparent pagination and provenance notes.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI clients such as Cursor to interact with GitHub repositories and perform issue listing, triage, health checks, prioritization, commenting, weekly digests, and release-note generation through purpose-built MCP tools.1 npmMIT
- 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.-
TDQS
A3.6/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct roles: search_issues performs broad filtered queries and returns summaries, while get_issue fetches full detail (body + comments) for a single item. There is no realistic way to confuse them.
Naming Consistency5/5
Both names follow a consistent snake_case verb_noun pattern (search_issues, get_issue), which matches well-known GitHub API conventions. Adding a read_ or fetch_ variant would be the only nitpick, but the set is fully consistent.
Tool Count3/5
Only 2 tools is thin even for a read-only server; a list/get pair for a repo's issues (without resorting to search syntax) would be a natural third tool. It is defensible as a focused search-and-read helper, but it sits at the borderline of being under-scoped.
Completeness3/5
The surface covers search and single-item retrieval, but has notable gaps for a server named 'github-updates': no way to comment, create, edit, or close issues/PRs, and no straightforward list-issues-in-repo tool for users who don't know GitHub search qualifiers. It is usable as a read-only viewer but incomplete as a lifecycle surface.
Maintenance
ActivityMaintained
ResponsivenessNo issues