A
licenseB
qualityF
maintenanceEnables LLMs to interact with GitHub issues by providing details as tasks, allowing for seamless integration and task management through GitHub's platform.
1
35 npm
14
MIT
mcp-github-issues
by ygerfal
Related Servers
Alternatives to mcp-github-issues
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables LLM agents to search, read, and create GitHub issues and pull requests via natural language, using the GitHub API.1MIT
- FlicenseNot gradedqualityCmaintenanceExposes GitHub issue operations as tools for LLM agents, enabling listing, creating, commenting on, closing, and searching issues via natural language.-
- FlicenseNot gradedqualityBmaintenanceEnables MCP-compatible LLM clients to query GitHub repository data—commits, issues, contributor stats, and code search—as typed callable tools over stdio.-
- FlicenseNot gradedqualityBmaintenanceEnables automated GitHub issue querying and repository tool actions through natural language, powered by Groq Llama-3 and the GitHub REST API.-
- 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.-
TDQS
A4/5.0
Scored across 3 tools
Disambiguation5/5
Each tool serves a clear, distinct purpose: listing issues, creating issues, and adding comments. No overlap exists between them.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case: list_issues, create_issue, add_comment.
Tool Count4/5
With only 3 tools, the server is minimal but appropriate for its narrow focus on issues; it could be expanded but is not unreasonable.
Completeness2/5
The surface lacks essential operations like updating, closing, or deleting issues, and does not support retrieving individual issue details. This creates significant gaps for typical issue management workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues