Oss Issues Mcp

io.github.AmrMohamed17Published by GitHub account AmrMohamed17v0.1.1Updated Oct 24, 2026

MCP server with derived GitHub issue tools: normalized fetch, new-issue watch, claim status.

Overview

AI-generated overview

Local MCP server that gives an assistant triage-oriented GitHub issue tools: normalized issue fetch, new-issue watch and claim status.

What you can do
  • Fetch a single issue with template scaffolding stripped, returning only triage-relevant fields
  • Check whether an issue is already claimed, based on assignees and linked pull requests
  • Watch a list of repositories for new open issues, excluding pull requests
  • Retrieve repository contribution context such as CONTRIBUTING.md and issue-template rules (planned)
  • Restrict all access to an explicit repository allowlist
When to use it
Useful when you want an assistant to triage open-source issues for contribution: reading a clean issue, judging whether someone is already working on it, and spotting new issues in repositories you follow. It is not a general GitHub API passthrough.
Requirements
Runs locally as a Python package (uv sync, uv run oss-issues-mcp) over stdio. Requires a fine-grained, read-only GitHub personal access token supplied in the GITHUB_TOKEN environment variable, with Issues, Metadata and Contents permissions. Repositories must be explicitly allowlisted.
Before you install
A GitHub personal access token is required; keep it read-only and scoped to the repositories you allowlist. The server is read-only by design and states that no write tools exist until a human-approval gate governs them. Several listed tools are marked as planned, so capabilities may be incomplete.

Installation

In SourceWeft

  1. Open Oss Issues Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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

ToolPurpose
get_actionable_issueFetch an issue, strip template furniture, return only triage-relevant fields
(planned) list_new_issuesNew open issues across a watch-list, pull requests excluded
(planned) get_claim_statusIs this already being worked on? (assignees + linked PRs)
(planned) get_repo_contextCONTRIBUTING.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 syncuv run oss-issues-mcp

License

MIT

Source: README.md at commit a6fa50a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts