Skip to main content
Glama
Sign In
oss-issues-mcp

oss-issues-mcp

by AmrMohamed17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to oss-issues-mcp

No user-submitted related servers found.

    Related Servers

    • claimcheck

      CloudCorpRecords
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents and developers to check, before they comment or write code, which issue claims have gone stale and which finished fork branches never became a pull request. It ranks abandoned claims oldest-first, flags parked branches with compare data, and reports every claimant and linked PR for a single issue.
      332 npm
      MIT

    • github-triage-agent

      Hemamannam
      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

    • triage-mcp

      Yash06B
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to search and retrieve GitHub issues and labels, validate duplicate references, and optionally add labels or post comments with writes disabled, dry-run, or live.
      MIT

    • GitHub Issues MCP Server

      C-you-know
      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

    • Greenlight

      CloudCorpRecords
      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.
      1,032 npm
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    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
    ResponsivenessSyncing

    Resources