Skip to main content
Glama
Sign In
GitHub Notifications MCP Server

GitHub Notifications MCP Server

by mcollina
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to GitHub Notifications MCP Server

No user-submitted related servers found.

    Related Servers

    • okffs

      neturely
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets Claude Code manage GitHub issues, branches, and pull requests through natural language, automating the full development workflow from planning to closing.
      433 npm
      2
      MIT

    • devscope-mcp

      peteroyce
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that gives Claude live access to your GitHub workspace — PR reviews, issue triaging, repo search, and weekly digest reports through natural language.
      7
      MIT

    • GitHub MCP Server

      amedmohmed925
      A
      license
      Not graded
      quality
      D
      maintenance
      A custom MCP server that lets AI assistants interact with GitHub accounts, offering tools for repository creation, file viewing, code search, and issue management.
      ISC

    • GitHub MCP Server

      ualUsham
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that enables Claude and other compatible LLMs to interact with the GitHub API, supporting features like creating issues, retrieving repository information, listing issues, and searching repositories.
      4
      ISC
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific notification actions like listing, marking, or managing subscriptions. The descriptions precisely differentiate operations by scope (e.g., list-notifications vs. list-repo-notifications) and action type, leaving no ambiguity for agent selection.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with hyphens, such as 'list-notifications' and 'mark-thread-read'. The naming is uniform across the set, making it predictable and easy for agents to parse and understand the intended operations.

    Tool Count5/5

    With 11 tools, the server is well-scoped for GitHub notifications, covering key operations like listing, marking, and managing subscriptions. Each tool serves a specific function without redundancy, making the count appropriate for the domain's complexity and user needs.

    Completeness5/5

    The tool set provides complete coverage for GitHub notification workflows, including CRUD-like operations (list, get, mark, delete) and lifecycle management (subscriptions, read/done status). There are no obvious gaps, ensuring agents can handle all typical notification tasks without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources