Developer · Remote MCP server
notifyd
Operate a self-hosted notifyd instance: digest, jobs, retries, suppressions, projects, test sends.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.rmzlb/notifyd- Version
- 0.4.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Package
- OCI image (Docker)
- Published
- 2026-09-15
- Updated
- 2026-09-15
- Publisher
- rmzlb (GitHub)
- Website
- github.com/rmzlb/notifyd
- Repository
- github.com/rmzlb/notifyd
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://{notifyd_host}/mcp | Authorization (required, secret) |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker) | ghcr.io/rmzlb/notifyd:0.4.0 | — | HTTP |
How to connect notifyd
notifyd is a remote MCP server: there is nothing to install. Its endpoint is https://{notifyd_host}/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The URL contains placeholders to fill in before connecting: {notifyd_host}.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/rmzlb/notifyd:0.4.0. The package starts a local server that speaks MCP over Streamable HTTP; the client then connects to it by URL. It reads these environment variables: DATABASE_URL (required, secret), JWT_SECRET (required, secret), ADMIN_API_KEY (required, secret), EMAIL_PROVIDER and EMAIL_FROM; set them in the client's configuration for this server.
Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Nostr Ops MCPNostr publishing, queries, and DMs for AI agents, with allowlists, rate limits, and an audit log. | Local · stdio |
| Noteit MCPMCP server for AI agent profiles and notes. 60+ coding prompt packs with expert personas. | Remote · HTTP |
| Notepatra MCPNotepatra editor MCP server — 35 tools; every write human-approved in the editor; local-only. | Local · stdio |
| Notify MCP ServerMCP Server for notify to Weixin, Telegram, Bark, Lark, Feishu, DingTalk. | Local · stdio |
| NotifyHub — Unified Notification MCP ServerSend notifications across 23 channels with 36 AI-ready tools. One API, zero boilerplate. | Local · stdio |
| Noun MCPProduction MCP server for The Noun Project — search & download icons in Cursor/Claude with OAuth… | Local · stdio |
| Novacal MCP ServerManage Novacal event types, availability, and bookings. | Remote · HTTP |
| Novai MCP ServerRead-only MCP server for querying the live NOVAI blockchain over its public JSON-RPC endpoint. | Local · stdio |