io.github.DJeswar/github-issues
Related Servers
Alternatives to io.github.DJeswar/github-issues
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to discover, filter, and triage GitHub issues across repositories, with tools for fetching issue details, listing issues by state/labels, and finding related pull requests.1MIT
- FlicenseNot gradedqualityCmaintenanceExposes GitHub issue operations as tools for LLM agents, enabling listing, creating, commenting on, closing, and searching issues via natural language.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to list, search, and inspect issues on any public GitHub repository via natural language.MIT
- AlicenseNot gradedqualityCmaintenanceEnables LLM agents to search, read, and create GitHub issues and pull requests via natural language, using the GitHub API.1MIT
- FlicenseNot gradedqualityCmaintenanceConnects an LLM to a GitHub repository's issues, allowing it to list, fetch, and search issues freely while gating new issues, comments, and closures behind a two-step, single-use confirmation token that cannot be bypassed. It provides least-privilege, token-authenticated access to the GitHub REST API through a small typed tool surface.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with GitHub repositories, issues, pull requests, code, and more through a comprehensive set of tools.-
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: structural listing, single-issue retrieval, free-text search, label metadata, and milestone metadata. List_issues and search_issues are the only potentially overlapping pair, but their descriptions explicitly separate structural filtering from text search.
Every tool follows a consistent lower_snake_case verb_noun pattern: list_*, get_*, and search_*. There are no mixed conventions, vague verbs, or inconsistent phrasing.
Five tools is a well-scoped count for a read-only GitHub issue exploration server. Each tool earns its place and the set feels compact rather than redundant.
For the clearly read-only domain, coverage is complete: list/get/search handle issue discovery and retrieval, get_issue optionally includes comments, and labels/milestones cover the metadata needed for filtering and release planning. Mutation tools are intentionally absent rather than missing.