oss-issues-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | A fine-grained, read-only GitHub token |
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_actionable_issueA | Fetch one issue, normalised for triage: template scaffolding stripped, only the fields a readiness judge needs (title, cleaned body, labels, author association, comments, state, url). |
| list_new_issuesA | New OPEN issues across the watch-list, pull requests excluded. The single call that answers "what's new across everything I watch". Loops each repo, drops pull requests (the issues endpoint returns them too), and merges the results newest-first. |
| get_claim_statusA | Is this issue already being worked on? Combines two deterministic signals GitHub does not expose as one field: formal assignees, and pull requests linked to the issue. Returns a boolean plus the evidence behind it. (Comment-based "I'll take this" claims are not checked in this version.) |
| get_repo_contextA | The repo's contribution rules: CONTRIBUTING.md presence/excerpt and whether issue templates are configured. Fetched once per repo and cached, since these rarely change. |
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 4 tools
Each tool serves a distinct purpose: listing new issues, checking claim status, getting repo context, and fetching a single cleaned issue. No functional overlap.
All names use snake_case and verb+noun pattern, but 'list' vs 'get' prefix is a minor inconsistency. Otherwise consistent.
4 tools is small but focused on a specific triage workflow. Each tool earns its place; not too few for the domain.
Covers listing, claim checking, repo context, and fetching issues. Missing search or update capabilities, but adequate for read-only triage.