io.github.AmrMohamed17/oss-issues-mcp
MCP server with derived GitHub issue tools: normalized fetch, new-issue watch, claim status.
Open source Open in the app JSON README (API)
About
MCP server with derived GitHub issue tools: normalized fetch, new-issue watch, claim status.
Details
- Kind
- MCP servers
- Topic
- Version control
- Publisher
- amrmohamed17
- Origin
- official
- Category
- ferramentas
- Transport
- local
- Version
- 0.1.1
- Last push
- 2026-08-01T13:07:59Z
- Repository state
- ativo
- Language
- Python
- License
- MIT
- Added
- 2026-08-29 03:01:41
- Updated
- 2026-08-29 03:01:41
- Origin id
io.github.AmrMohamed17/oss-issues-mcp
README
# 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