Skip to main content
Glama
README.md
# oss-issues-mcp
<!-- mcp-name: io.github.AmrMohamed17/oss-issues-mcp -->
An MCP server exposing **derived, triage-oriented** GitHub issue tools — not a
passthrough of the GitHub API.

Where GitHub's own MCP server returns raw API responses, this server does
task-specific work: stripping issue-template scaffolding, resolving whether an
issue is already claimed from multiple signals, and filtering a watch-list of
repositories to what is new and open.

## Tools

| Tool | Purpose |
|---|---|
| `get_actionable_issue` | Fetch an issue, strip template furniture, return only triage-relevant fields |
| _(planned)_ `list_new_issues` | New open issues across a watch-list, pull requests excluded |
| _(planned)_ `get_claim_status` | Is this already being worked on? (assignees + linked PRs) |
| _(planned)_ `get_repo_context` | CONTRIBUTING.md and issue-template rules |

## Security

- **Repository allowlist** — the server refuses any repo not explicitly allowed.
- **Read-only** — no write tools exist until a human-approval gate governs them.
- Requires a fine-grained, read-only `GITHUB_TOKEN`.

## Run

```bash
export GITHUB_TOKEN=github_pat_...
uv sync
uv run oss-issues-mcp
```

## License

MIT

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation5/5

Each tool serves a distinct purpose: listing new issues, checking claim status, getting repo context, and fetching a single cleaned issue. No functional overlap.

Naming Consistency4/5

All names use snake_case and verb+noun pattern, but 'list' vs 'get' prefix is a minor inconsistency. Otherwise consistent.

Tool Count4/5

4 tools is small but focused on a specific triage workflow. Each tool earns its place; not too few for the domain.

Completeness4/5

Covers listing, claim checking, repo context, and fetching issues. Missing search or update capabilities, but adequate for read-only triage.

Maintenance

ActivityMaintained
ResponsivenessNo issues