GitHub Notifications

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

typescript

16

GitHub Stars

typescript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

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

This MCP Server helps you manage GitHub notifications through natural language commands. You can list, filter, mark as read, subscribe to threads, and adjust repository notification settings, all via a single, extensible MCP you can connect to with your preferred client.

How to use

Connect a compatible MCP client to the GitHub Notifications MCP Server, then issue natural language commands to manage your GitHub notifications. You can list current notifications, filter by criteria, mark items or threads as read, view thread details, subscribe or unsubscribe from threads, and adjust repository-wide notification settings. Use concise prompts like “Show my unread notifications,” “Mark thread 12345 as read,” or “Mute notifications for octocat/Hello-World.” The server translates your requests into GitHub API actions and returns results that you can act on further.

How to install

Prerequisites: You need Node.js 18 or higher.

Step 1: Install Node.js 18+ on your system. If you don’t have it yet, download and install it from the official Node.js website and verify with node -v.

Step 2: Install the MCP server’s dependencies in your project. Run:

npm install

Step 3: Build the project. Run:

npm run build

Step 4: Create a GitHub token for authentication. Generate a GitHub Personal Access Token (classic) with notifications or repo scope and store it securely. You will supply this token to the server when running.

Step 5: Create a configuration file and provide your GitHub token. You will reference this token when starting the server.

Additional setup and notes

The server can be run directly or connected to an MCP client via a local stdio process configuration. If you use a local process, you’ll start the server using a runtime command and pass the GitHub token via environment variables.

Configuration and environment variables

The server uses an environment variable for authentication. Set the following variable when starting the server: GITHUB_TOKEN with your GitHub Personal Access Token.

Available tools

list-notifications

List all GitHub notifications for the authenticated user.

mark-notifications-read

Mark all notifications as read.

get-thread

Get information about a notification thread.

mark-thread-read

Mark a specific thread as read.

mark-thread-done

Mark a thread as done.

get-thread-subscription

Get subscription status for a thread.

set-thread-subscription

Subscribe to a thread.

delete-thread-subscription

Unsubscribe from a thread.

list-repo-notifications

List notifications for a specific repository.

mark-repo-notifications-read

Mark notifications for a repository as read.

manage-repo-subscription

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