git-issuer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALLOWED_REPOS | Yes | Comma-separated list of owner/repo entries the agent may target | |
| GITHUB_APP_ID | Yes | App ID from your GitHub App settings page | |
| GITHUB_PRIVATE_KEY | Yes | Path to the .pem file or the key as a base64-encoded string | |
| RATE_LIMIT_PER_MINUTE | No | Max issue creations per minute (default: 10) | 10 |
| GITHUB_INSTALLATION_ID | Yes | Installation ID from the app installation URL |
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 |
|---|---|
| create_issueA | Create a GitHub issue on an allowed 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 1 tool
Only one tool exists, so there is no possibility of overlap or confusion. The tool's purpose is clearly stated.
The single tool name 'create_issue' follows a clear verb_noun convention, so there is no inconsistency.
With only one tool, the server is severely under-scoped for a GitHub issue workflow. A typical issue lifecycle requires at least create, read, and update operations.
The tool only supports issue creation and offers no way to list, read, update, or delete issues. This leaves agents unable to track or manage issues after creation, creating a dead end.