mcp-github-issues
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub personal access token with appropriate scopes (e.g., public_repo or repo) |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_issuesA | List issues in a GitHub repository. Use when the user wants to see open, closed, or all issues in a repo. Returns issue number, state, title, and author for each. Pull requests are filtered out so the result is true issues only. |
| create_issueA | Create a new issue in a GitHub repository. Use when the user wants to file a bug, request a feature, or track a task. Requires repo write permission on the authenticated user's token. The created issue is attributed to that user in the GitHub audit log. |
| add_commentA | Add a comment to an existing GitHub issue. Use when the user wants to reply to an issue thread. The comment is attributed to the authenticated user in the GitHub audit log. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ygerfal/mcp-github-issues'
If you have feedback or need assistance with the MCP directory API, please join our Discord server