Skip to main content
Glama

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

Related MCP server: contribscout

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

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

License

MIT

Available Tools

4 tools
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).

Inputs: repo (required), number (required). Returns: object

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.)

Inputs: repo (required), number (required). Returns: object

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.

Inputs: repo (required). Returns: object

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.

Inputs: days, repos. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to discover, filter, and triage GitHub issues across repositories, with tools for fetching issue details, listing issues by state/labels, and finding related pull requests.
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Exposes GitHub issue and pull-request triage capabilities to any MCP client: fetching repository context, classifying and prioritizing requests, finding duplicates, and applying labels, comments, assignments, closures, or reopenings. All writes are policy-gated, dry-run by default, and destructive actions require explicit two-step human confirmation.
      10
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to vet a GitHub issue before committing time to it, returning a landability verdict (GO, RISKY, TAKEN, GATED, STALE) plus repo friction scores, gate evidence, and ranked scans of a repository's starter issues. Also exposes contribution automation tools that draft claim comments, prep a fork and branch with a repo-specific checklist, and open a pull request once basics like DCO sign-off pass, with all writes dry-run by default.
      431 npm
      MIT