Gotify RMCP runs on your own machine — the client starts it, so there is no endpoint to ping. 60 installs a week from npm. Last commit 25 Aug 2026.
Gotify notifications and app, client, and message management over MCP and CLI.
We read the source, 10 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
postinstall: node scripts/install.js
const install = spawnSync(process.execPath, [installer], { stdio: "inherit" });
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
if std::path::Path::new("/.dockerenv").exists() || std::env::var("RUNNING_IN_CONTAINER").is_ok()
credentials_file="$HOME/.aws/credentials"
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add rgotify -- npx -y @dinglebear/rgotify
{
"mcpServers": {
"rgotify": {
"args": [
"-y",
"@dinglebear/rgotify"
],
"command": "npx"
}
}
}
[mcp_servers.rgotify]
command = "npx"
args = ["-y", "@dinglebear/rgotify"]
{
"mcpServers": {
"rgotify": {
"args": [
"-y",
"@dinglebear/rgotify"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"rgotify": {
"args": [
"-y",
"@dinglebear/rgotify"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
GOTIFY_URL (Gotify server base URL.), GOTIFY_CLIENT_TOKEN (Gotify client token for read and management actions.), GOTIFY_APP_TOKEN (Gotify app token for sending notifications.), GOTIFY_RMCP_VERSION (Optional GitHub release tag override for the downloaded Gotify RMCP binary.), GOTIFY_RMCP_REPO (Optional GitHub owner/repo override for release asset downloads.), GOTIFY_RMCP_RELEASE_BASE_URL (Optional release download base URL override.), RUST_LOG (Tracing filter for Gotify RMCP logs.).
The author declared them in the registry entry; get the values from the project itself.
Rust MCP server and CLI for Gotify push notifications and message management.
MCP server for Gotify push notifications - send messages and manage apps/clients.
MCP server for self-hosted Gotify push notifications and message management.
Send, manage, and replay ntfy push notifications via MCP.
Apprise notifications over MCP and CLI with authenticated stdio and HTTP transports.
Read Remind classes, chats and messages, and manage notification settings.
Publish ntfy notifications, read the message cache, and manage users and topic access
Sling CLI MCP server for data pipeline and replication management
Answers built from our own checks of this server.