GitHub Issues MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the HTTP server (only used when running with `npm run start:http`). | 3001 |
| GITHUB_REPO | No | The repository name. | |
| GITHUB_OWNER | No | The owner or organization of the repository. | |
| GITHUB_TOKEN | No | GitHub personal access token with Issues: Read and write on the repository. | |
| MCP_AUTH_TOKEN | No | Authentication token required to start the HTTP server. Should be a long random value. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_issuesA | List issues in the GitHub repository, most recently updated first. Returns issue number, title, state, author, and labels. |
| create_issueB | Create a new issue in the GitHub repository. |
| add_commentB | Add a comment to an existing issue. |
| search_issuesA | Search for issues in this repository using GitHub search syntax (for example label:bug is:open). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| repository-readme | The repository README file |
| recent-issues | The 10 most recently updated open issues |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: listing, creating, commenting, and searching. There is no meaningful overlap between list_issues (broad browsing) and search_issues (query-based filtering), and the descriptions make this distinction explicit.
All four tool names follow a consistent verb_noun snake_case pattern: list_issues, create_issue, add_comment, search_issues. The naming is predictable and immediately communicates the action and target.
With only 4 tools, the server is quite focused but still covers core issue interaction. The count is on the low end but not unreasonably thin for a single-purpose GitHub issues server, so it earns a borderline score.
The server covers listing, creating, commenting, and searching issues, which handles the most common workflows. However, it lacks obvious lifecycle operations like updating, closing, or fetching a single issue, leaving notable gaps that agents cannot work around without external tools.