GitHub Issue Manager
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_PERSONAL_ACCESS_TOKEN | Yes | Your GitHub Personal Access Token for authentication. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_issuesC | List open or closed issues in a GitHub repository. |
| create_issueB | Create a new issue in a GitHub repository. |
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 2 tools
The two tools have clearly distinct purposes: one creates issues, the other lists them. No overlap or ambiguity.
Both tools follow a consistent verb_noun pattern (create_issue, list_issues) with proper snake_case naming.
Only 2 tools for an issue manager is too few to be useful. A typical issue server would need at least 5-10 tools for basic operations.
Severely incomplete: missing update, delete, get single issue, comment, label, and search operations. The surface cannot handle basic issue lifecycle workflows.