GitHub Notifications MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub Personal Access Token (classic) with 'notifications' or 'repo' scope |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-notificationsC | List GitHub notifications for the authenticated user |
| mark-notifications-readC | Mark GitHub notifications as read |
| get-threadC | Get information about a GitHub notification thread |
| mark-thread-readC | Mark a GitHub notification thread as read |
| mark-thread-doneC | Mark a GitHub notification thread as done |
| get-thread-subscriptionA | Get subscription status for a GitHub notification thread |
| set-thread-subscriptionC | Subscribe to a GitHub notification thread |
| delete-thread-subscriptionA | Unsubscribe from a GitHub notification thread |
| list-repo-notificationsC | List GitHub notifications for a specific repository |
| mark-repo-notifications-readC | Mark GitHub notifications for a specific repository as read |
| manage-repo-subscriptionC | Manage repository subscription settings including fine-grained notification preferences |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
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.
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.
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.
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.