github-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub Personal Access Token. 없으면 공개 저장소만 조회 가능하며 API 요청 제한이 낮아짐 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_open_prsA | 저장소의 열린 Pull Request 목록을 최대 20개 반환합니다. |
| get_latest_releaseB | 저장소의 최신 릴리즈 정보를 반환합니다. |
| get_repo_infoC | GitHub 저장소의 기본 정보를 반환합니다. |
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 3 tools
Each tool targets a distinct resource: release, repo info, and pull requests. There is no overlap in functionality.
All tools follow a consistent snake_case pattern with verbs 'get' and 'list', maintaining clear and predictable naming.
Only 3 tools for a server named 'github-mcp-server' is far too few. A typical GitHub integration would have many more tools covering various operations.
The tool surface only covers read operations on releases, repo info, and open PRs, missing critical write operations and other common resources like issues, commits, and branches.