MCP GitHub Issue Server
Related Servers
Alternatives to MCP GitHub Issue Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceIntegrates with GitHub REST API to allow LLM agents to list and create repository issues.2379 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables LLM agents to search, read, and create GitHub issues and pull requests via natural language, using the GitHub API.1MIT
- FlicenseAqualityDmaintenanceEnables LLMs to list, create, and comment on GitHub issues using your own GitHub identity via stdio transport.3-
- FlicenseNot gradedqualityCmaintenanceExposes GitHub issue operations as tools for LLM agents, enabling listing, creating, commenting on, closing, and searching issues via natural language.-
- FlicenseNot gradedqualityFmaintenanceEnables interaction with GitHub issues via the Model Context Protocol, allowing users to list and create issues with secure authentication.-
- FlicenseNot gradedqualityDmaintenanceEnables GitHub repository and issue management through the Model Context Protocol, supporting retrieval of repo details, issue listing, creation, and commenting.-
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it against. The tool's purpose is clearly defined as fetching GitHub issue details for task usage.
The single tool name 'get_issue_task' follows a consistent verb_noun pattern, using snake_case. Since there is only one tool, naming consistency is inherently perfect with no deviations to assess.
A single tool is too few for a server named 'MCP GitHub Issue Server', as this suggests a broader scope for managing GitHub issues. Typically, such a server would include multiple tools for operations like creating, updating, listing, or closing issues, making this set feel incomplete and thin.
The tool set is severely incomplete for the apparent domain of GitHub issue management. It only provides a 'get' operation, lacking essential CRUD/lifecycle coverage such as create, update, delete, list, or search, which will likely cause agent failures in handling issue-related tasks.