github-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TRANSPORT | No | Transport type. Set to 'streamableHttp' to enable HTTP/SSE transport (e.g., MCP_TRANSPORT=streamableHttp). | |
| GITHUB_ACCESS_TOKEN | No | GitHub Personal Access Token. Required for API calls, but server can start without it. | |
| STREAMABLE_HTTP_PORT | No | Port for the Streamable HTTP server when using streamableHttp transport (e.g., STREAMABLE_HTTP_PORT=3001). |
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 |
|---|---|
| addC | Add two numbers |
| list_issuesC | List issues 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 are completely unrelated in purpose: one is arithmetic, the other is GitHub issue listing. There is no ambiguity between them.
The tool names are inconsistent: 'add' is a generic verb while 'list_issues' follows a verb_noun pattern. There is no uniform naming convention.
With only 2 tools, the tool count is too low for a server named 'github-mcp'. The arithmetic tool seems out of place, and the server lacks depth.
The server is named for GitHub but provides only one GitHub-related tool. There are no tools for creating, updating, or closing issues, and the arithmetic tool is unrelated.