@sumirati/mcp-github
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | Alternative token variable name | |
| GITHUB_API_URL | No | Base API URL | https://api.github.com |
| GITHUB_READ_ONLY | No | Enable 3-tier read-only mode (true, 1, yes) | false |
| GITHUB_PERSONAL_ACCESS_TOKEN | No | GitHub Personal Access Token (classic or fine-grained) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| github_find_actionsA | Search and discover available GitHub actions in the 75-action catalog by keyword query or domain filter. Use this discovery tool first whenever you need to perform an action outside the 3 eager daily drivers (e.g. managing PRs, issues, releases, workflows, collaborators, webhooks, variables, security alerts). Returns matching action names, domain categories, mutating flags, descriptions, and complete parameter schemas so you can construct the call for github_execute_action. |
| github_execute_actionA | Execute any supported GitHub action from the 75-action catalog by action name with parameters. Requires the exact action name (discovered via github_find_actions) and its corresponding argument dictionary. Output is automatically compressed with strict token projection filters (stripping URLs, avatar links, empty hashes, node_ids) to guarantee 70%+ token savings. Mutating actions are blocked when running in read-only mode (GITHUB_READ_ONLY=true). |
| get_file_contentsA | Read current file contents or list directory entries from a repository at a specified git ref without cloning. Automatically decodes Base64 file contents into plain text UTF-8 in 'decoded_content'. Eager daily driver tool for inspecting source code, configuration files, and directory layouts. |
| get_repositoryA | Get comprehensive repository metadata, visibility, description, default branch, clone URLs, star count, and topics for an owner/repo. Eager daily driver tool for verifying repository configuration and existence. |
| get_commitA | Get detailed commit metadata, author information, message, and unified git diffs for a specific commit SHA or reference. Eager daily driver tool for reviewing code modifications, patches, or investigating regressions. Output diffs are token-optimized and automatically truncated to max_diff_lines (default: 400 lines). |
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 5 tools
The discover/execute pair is clearly distinct from each other, and the three get_* tools are distinct among themselves. However, github_execute_action can perform any of the 75 catalog actions, which likely includes the read operations covered by get_file_contents, get_repository, and get_commit, creating overlap. The 'eager daily driver' framing helps, but an agent must still decide between the direct tool and the generic executor.
All names use snake_case, but two conventions coexist: the meta tools use a github_ namespace prefix (github_find_actions, github_execute_action) while the direct tools use bare get_* verbs (get_file_contents, get_repository, get_commit). The get_* trio is internally consistent, but the mixed prefixing and differing verb styles make the set only partially predictable.
Five tools is a compact, well-scoped surface for what is effectively a 75-action GitHub catalog, avoiding the bloat of exposing every action individually. The three eager tools are somewhat redundant given execute_action, but they justify themselves as high-frequency shortcuts. The count is reasonable and no tool feels extraneous.
The catalog-plus-executor design claims coverage of PRs, issues, releases, workflows, collaborators, webhooks, variables, and security alerts, which is broad lifecycle coverage for a GitHub server. Discovery via github_find_actions fills the gap of not knowing action names. Minor gaps exist in that nothing is eager for write operations and catalog completeness depends entirely on the advertised 75 actions being real and correct.