NotiBuddy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | Fixed destination alias for the MCP server (--to). Use either --to or one or more --allow-to, not both. | |
| sender | No | Optional free-form sender label for notifications (--sender), defaulting to the hostname. | |
| allow-to | No | Destination alias exposed by the MCP server (--allow-to). Repeat --allow-to to expose multiple destinations; use either --to or --allow-to, not both. | |
| NOTIBUDDY_HOME | No | Relocates the entire NotiBuddy local store for testing or a custom installation; it does not select a profile. | |
| NOTIBUDDY_NO_UPDATE_CHECK | No | Set to 1 to disable the npm update check. |
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 |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues