GitHub Notifications MCP Server

@mcollina

リポジトリ

基本情報

カテゴリ

バージョン管理

ライセンス

MIT

トランスポート

stdio

作者

mcollina

GitHub Notifications MCP Server について

An MCP server for the github notifications API for the OSS maintainer

GitHub Notifications MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "github-notifications": {
      "command": "node",
      "args": [
        "/absolute/path/to/github-notifications-mcp-server/build/index.js"
      ],
      "env": {
        "GITHUB_TOKEN": "your_github_personal_access_token_here"
      }
    }
  }
}

GitHub Notifications MCP Server のツール

List all GitHub notifications for the authenticated user

Mark all notifications as read

Get information about a notification thread

Mark a specific thread as read

Mark a thread as done

Get subscription status for a thread

Subscribe to a thread

Unsubscribe from a thread

List notifications for a specific repository

Mark notifications for a repository as read

Manage repository subscriptions: all_activity, default (participating and @mentions), or ignore (mute)

概要

What is GitHub Notifications MCP Server?

An MCP (Model Context Protocol) server that provides tools for managing GitHub notifications. It allows AI assistants like Claude to help manage GitHub notifications through natural language commands.

How to use GitHub Notifications MCP Server?

Prerequisites: Node.js 18+, GitHub Personal Access Token (classic) with notifications or repo scope. Clone the repo, run npm install and npm run build, then either start directly with npm start or configure it in Claude Desktop’s claude_desktop_config.json using the node command pointing to the built index.js and passing the GITHUB_TOKEN environment variable.

Key features of GitHub Notifications MCP Server

List and filter GitHub notifications
Mark notifications as read
View notification thread details
Subscribe or unsubscribe from notification threads
Mark threads as done
Manage repository-specific notifications
Control repository notification settings (all activity, default, mute)

Use cases of GitHub Notifications MCP Server

Check and review unread GitHub notifications through a conversational AI
Mark all notifications or specific threads as read
Unsubscribe from unwanted notification threads
Manage repository notifications, e.g., watch all activity, set to default, or mute
Get thread details and subscription status

よくある質問

What does GitHub Notifications MCP Server do?

It provides tools for AI assistants to list, filter, read, mark, and manage GitHub notification subscriptions via natural language commands.

What are the prerequisites?

Node.js 18 or higher and a GitHub Personal Access Token (classic) with the `notifications` or `repo` scope.

Where are notifications stored?

Notifications are fetched directly from the GitHub API using the provided token; no local storage is described.

How do I authenticate?

Set the token as the `GITHUB_TOKEN` environment variable, either in a `.env` file or directly in the MCP server configuration when used with Claude Desktop.

What transport protocol does it use?

The server is configured for stdio transport, as shown in the Claude Desktop configuration where it is launched as a child process via `node`.

「バージョン管理」の他のコンテンツ

Atlassian Jira MCP Server

aashari

Node.js/TypeScript MCP server for Atlassian Jira. Equips AI systems (LLMs) with tools to list/get projects, search/get issues (using JQL/ID), and view dev info (commits, PRs). Connects AI capabilities directly into Jira project management and issue tracking workflows.