Schema | GitHub Notifications MCP Server

GitHub Notifications MCP Server

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

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.

Server capabilities have not been inspected yet.

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

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mcollina/mcp-github-notifications'

If you have feedback or need assistance with the MCP directory API, please join our Discord server