github-issue-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enables debug behavior/logging | false |
| GITHUB_REPO | Yes | GitHub repository name | |
| GEMINI_MODEL | No | Gemini model used by the AI client | gemini-3.6-flash |
| GITHUB_OWNER | Yes | GitHub repository owner or organization | |
| GITHUB_TOKEN | Yes | GitHub API authentication token | |
| GEMINI_API_KEY | Yes | Google Gemini API key | |
| GEMINI_MAX_RETRIES | No | Maximum number of Gemini retries | 3 |
| GEMINI_RETRY_BASE_DELAY | No | Base retry delay in milliseconds | 1000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_issueC | Generate a structured GitHub issue using the issue description, issue details, and repository labels. |
| create_github_issueB | Create a new issue in a GitHub repository |
| list_github_issuesA | List open issues in a GitHub repository |
| list_github_labelsA | List labels available in a GitHub repository |
| check_duplicate_issueA | Find the most likely existing open GitHub issues that could be related to a proposed issue. This tool retrieves open issues and performs cheap lexical candidate ranking. Treat the returned issues as candidates only; semantic duplicate determination must be done by the AI. Do not call list_github_issues separately for duplicate checking. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Most tools have clear purposes, but generate_issue and create_github_issue could be mistaken for each other. check_duplicate_issue overlaps with list_github_issues, though the description explicitly warns against calling list separately, which helps. Overall, some ambiguity remains.
Tool names mix conventions: check_duplicate_issue and generate_issue lack the 'github_' prefix, while create_github_issue, list_github_issues, and list_github_labels include it. This inconsistency makes the set feel less predictable, though the verb-noun structure is somewhat consistent.
With exactly 5 tools, the server is well-scoped for GitHub issue management. Neither too sparse nor overloaded; each tool serves a clear functional role.
The server covers issue creation, listing, labels, and duplicate detection, but lacks essential operations like updating, closing, or fetching a single issue. This creates significant gaps in the issue lifecycle that agents will need to work around.