@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 83-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 parameter signatures so you can construct the call for github_execute_action. |
| github_execute_actionA | Execute any supported GitHub action from the 83-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 hypermedia URL templates, avatar links, empty fields, node_ids) and formatted as compact Markdown by default. Mutating actions are blocked when running in read-only mode (GITHUB_READ_ONLY=true). |
| get_file_contentsA | Read current file contents, extract symbol outlines, slice line ranges, or list directory entries from a repository at a specified git ref without cloning. Automatically decodes Base64 file contents into plain text UTF-8. Eager daily driver tool for inspecting source code, configuration files, and directory layouts. |
| get_repositoryA | Get comprehensive repository metadata, visibility, description, default branch, HTML URL, star count, fork count, and open issues count 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 three eager tools (get_repository, get_file_contents, get_commit) each target a distinct resource, and the find/execute pair has a clear discover-then-run relationship. Minor overlap exists because repo/file/commit reads are also reachable through github_execute_action, but the descriptions clearly frame the get_ tools as fast-path shortcuts.
Two coherent families exist: snake_case get_noun for the eager daily drivers and github_verb_noun for the catalog tools, each internally consistent. The split prefix conventions are a minor deviation but deliberate and readable.
Five visible tools is lean, but the find/execute meta-tools compress an 83-action surface into two entries, which is efficient rather than thin. The design is well-scoped, though direct-operation coverage is intentionally minimal.
The 83-action catalog spans PRs, issues, releases, workflows, collaborators, webhooks, variables, and security alerts, giving broad lifecycle coverage through github_execute_action. The eager tools alone lack full CRUD, but agents can work around this via the catalog.