ntfy-me-mcp 📤

Created By
Dieg0skia year ago
An ntfy MCP server for sending ntfy notifications to your self-hosted ntfy server 📤 (supports secure token auth - use with npx or docker!)
Overview

What is ntfy-me-mcp?

ntfy-me-mcp is a server designed to send notifications to your self-hosted ntfy server, utilizing secure token authentication and supporting both npx and Docker for easy deployment.

How to use ntfy-me-mcp?

To use ntfy-me-mcp, you can either run it using npx by executing npx ntfy-me-mcp in your terminal or deploy it using Docker with the command docker run -d dieg0ski/ntfy-me-mcp.

Key features of ntfy-me-mcp?

  • Secure token authentication for enhanced security.
  • Easy setup with minimal configuration required.
  • Docker support for containerized deployment.
  • Cross-platform compatibility with Linux and Windows.
  • Lightweight design for efficient resource usage.

Use cases of ntfy-me-mcp?

  1. Sending notifications from applications to a self-hosted ntfy server.
  2. Integrating notification management into development workflows.
  3. Utilizing secure token authentication for sensitive notifications.

FAQ from ntfy-me-mcp?

  • Can I run ntfy-me-mcp without Docker?

Yes, you can run it using npx without Docker.

  • Is ntfy-me-mcp secure?

Yes, it supports secure token authentication to protect your notifications.

  • What platforms does ntfy-me-mcp support?

It is compatible with both Linux and Windows systems.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Dieg0ski
Star
0
Language
JavaScript
License
View license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago