github-updates
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | A GitHub token used to access the GitHub API. If not set, the token from the gh CLI (gh auth login) is used instead. A read-only fine-grained token with Issues: Read and Pull requests: Read permissions is recommended. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_issuesA | Busca issues y pull requests de un repo con la sintaxis de búsqueda de GitHub. repo: "owner/nombre".
query: filtros de GitHub tal cual. Ejemplos: "is:pr is:merged merged:2022-10-01..2022-10-31",
"is:issue is:open", "is:issue closed:>=2026-09-20", "label:bug", texto libre.
Incluye siempre is:issue o is:pr (GitHub lo exige con tokens fine-grained).
No admite repo:/org:/user:, OR/AND/NOT ni paréntesis: haz una búsqueda por cada consulta.
limit: máximo de resultados (tope 100).
Devuelve total_count (total real en GitHub) e items (como mucho |
| get_issueC | Detalle de un issue o pull request: cuerpo completo y comentarios. |
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 have clearly distinct roles: search_issues performs broad filtered queries and returns summaries, while get_issue fetches full detail (body + comments) for a single item. There is no realistic way to confuse them.
Both names follow a consistent snake_case verb_noun pattern (search_issues, get_issue), which matches well-known GitHub API conventions. Adding a read_ or fetch_ variant would be the only nitpick, but the set is fully consistent.
Only 2 tools is thin even for a read-only server; a list/get pair for a repo's issues (without resorting to search syntax) would be a natural third tool. It is defensible as a focused search-and-read helper, but it sits at the borderline of being under-scoped.
The surface covers search and single-item retrieval, but has notable gaps for a server named 'github-updates': no way to comment, create, edit, or close issues/PRs, and no straightforward list-issues-in-repo tool for users who don't know GitHub search qualifiers. It is usable as a read-only viewer but incomplete as a lifecycle surface.