MCP server that provides derived GitHub issue tools for normalized fetch, new-issue watching, and claim status checks. It is designed to expose GitHub issue–related functionality through an MCP interface, based on the repository name and description provided.

🛠️ Key Features

Normalized fetch for GitHub issues
New-issue watch capability
Claim status retrieval

🚀 Use Cases

Fetching GitHub issue data in a normalized format
Monitoring for newly created issues
Checking the status of an issue claim

⚡ Developer Benefits

Direct access to issue tools through MCP
Clear separation of operations: fetch, watch, and claim status

⚠️ Limitations

Limited tool scope as described: normalized fetch, new-issue watch, and claim status only

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

Install

Configuration

Environment variables

GITHUB_TOKENrequiredsecret

Fine-grained GitHub personal access token, read-only (public repos: Issues, Metadata, Contents).

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "oss-issues-mcp": {
      "command": "uvx",
      "args": [
        "oss-issues-mcp"
      ],
      "env": {
        "GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
      }
    }
  }
}

io.github.AmrMohamed17/oss-issues-mcp