github-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | Fine-grained personal access token for authenticated requests. Required for write tools; read works without it (with lower rate limits). | |
| GITHUB_MCP_LIVE | No | Set to '1' to run real-network smoke tests. | |
| GITHUB_MCP_ENABLE_WRITE | No | Set to '1' to enable the write tool group (off by default). |
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 |
|---|---|
| get_repo | Get metadata for a repository: description, language, stars, forks, open issues, default branch, archived flag, license, last-push time. |
| list_issues | List issues for a repository (pull requests filtered out), most-recently-updated first. |
| get_issue | Fetch a single issue's full detail: title, body, state, labels, comment count. |
| list_pull_requests | List pull requests for a repository, most-recently-updated first. |
| get_pull_request | Fetch a single pull request's full detail, including merge state. |
| get_file_content | Read a UTF-8 text file from a repo at a given path (base64-decoded). Reports binary files rather than decoding them. |
| search_repos | Search public repositories by keyword/qualifiers, sorted by best match. |
| get_user | Get a public profile for a GitHub user or organization. |
| list_commitsA | List commits on a repo's default branch (or a given ref), newest first. |
| create_issue | Open a new issue on a repository. Requires GITHUB_MCP_ENABLE_WRITE=1 and GITHUB_TOKEN. |
| comment_on_issue | Post a comment on an issue or pull request. Requires GITHUB_MCP_ENABLE_WRITE=1 and GITHUB_TOKEN. |
| update_issue_state | Set an issue's state to 'open' or 'closed'. Requires GITHUB_MCP_ENABLE_WRITE=1 and GITHUB_TOKEN. |
| add_labels | Add one or more labels to an issue or pull request. Requires GITHUB_MCP_ENABLE_WRITE=1 and GITHUB_TOKEN. |
| create_pr_review_commentB | Create a review comment on a specific line of a pull request's diff. Requires GITHUB_MCP_ENABLE_WRITE=1 and GITHUB_TOKEN. |
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 target entirely different actions: listing commits vs. creating PR review comments. No overlap exists, and an agent can clearly distinguish them.
Both tools follow a consistent verb_noun pattern in snake_case (list_commits, create_pr_review_comment), showing good naming discipline.
With only 2 tools, the server is severely under-scoped for a GitHub MCP server, which typically requires at least a dozen tools to cover basic operations like issues, PRs, and repos.
The tool surface has major gaps: no tools for issues, repositories, pull requests (beyond a review comment), or search. An agent would often fail to accomplish common GitHub tasks.