Notify MCP Server

How to use

You connect to the Notify MCP Server from your MCP client by configuring one or more MCP server endpoints. You can use a remote HTTP endpoint or run the server locally with a standard I/O (stdio) workflow. Once connected, you can send notifications to your chosen channels like WeChat Work, DingTalk, Telegram, Bark, Lark, Feishu, and Home Assistant by selecting the appropriate tool or endpoint in your MCP client. The server supports streaming delivery over HTTP and can be run with different deployment methods to suit your environment.

Explore the available environment variables to tailor authentication, API endpoints, and base URLs for each messaging provider. You can set default targets, tokens, and base API URLs to simplify usage across your MCP projects.

How to install

Prerequisites: you should have a container or process runner available, plus a valid MCP client setup. You will choose one of the installation methods below.

{
  "mcpServers": {
    "mcp-notify": {
      "command": "uvx",
      "args": ["mcp-notify"],
      "env": {
        "WEWORK_BOT_KEY": "your-wework-bot-key"
      }
    }
  }
}

Alternative 2: Smithery (requires OAuth authorization or Smithery key). Use the streaming HTTP URL to connect.

{
  "mcpServers": {
    "mcp-aktools": {
      "url": "https://server.smithery.ai/@aahl/mcp-notify/mcp" # 流式传输HTTP
    }
  }
}

Alternative 3: Docker. Create a directory for the server, pull the Compose file, and run it. Then connect using the HTTP streaming URL.

mkdir /opt/mcp-notify
cd /opt/mcp-notify
wget https://raw.githubusercontent.com/aahl/mcp-notify/refs/heads/main/docker-compose.yml
docker-compose up -d
```
```yaml
{
  "mcpServers": {
    "mcp-notify": {
      "url": "http://0.0.0.0:8809/mcp" # 流式传输HTTP
    }
  }
}

Additional setup notes

If you run via Docker or Smithery, ensure network access to the specified endpoints and provide any required OAuth credentials or keys as environment values or in your Smithery configuration.

Environment variables

Configure credentials and API endpoints for each provider you plan to use. The setup supports a range of providers with the following environment variables.

Provider environment variables

WeChat Work services - WEWORK_BOT_KEY: WeChat Work bot key (default) or provided via prompt WeChat Work Application - WEWORK_APP_CORPID: Corporate ID - WEWORK_APP_SECRET: App secret key - WEWORK_APP_AGENTID: App agent ID, default: 1000002 - WEWORK_APP_TOUSER: Default recipient user, default: @all - WEWORK_BASE_URL: API proxy base URL, default: https://qyapi.weixin.qq.com DingTalk groups - DINGTALK_BOT_KEY: DingTalk group bot access_token - DINGTALK_BASE_URL: API base URL, default: https://oapi.dingtalk.com Feishu / Lark groups - FEISHU_BOT_KEY: Feishu bot key - FEISHU_BASE_URL: Feishu API base URL, default: https://open.feishu.cn - LARK_BOT_KEY: Lark bot key - LARK_BASE_URL: Lark API base URL, default: https://open.larksuite.com Telegram - TELEGRAM_DEFAULT_CHAT: Default chat ID - TELEGRAM_BOT_TOKEN: Telegram bot token - TELEGRAM_BASE_URL: Telegram API base URL, default: https://api.telegram.org Home Assistant - HASS_BASE_URL: Home Assistant URL, default: http://homeassistant.local:8123 - HASS_ACCESS_TOKEN: Long-lived access token - HASS_MOBILE_KEY: Mobile device key (e.g., mobile_app_your_device) Other providers - BARK_DEVICE_KEY: Bark device key - BARK_BASE_URL: Bark API base URL, default: https://api.day.app - NTFY_DEFAULT_TOPIC: Default Ntfy topic - NTFY_BASE_URL: Ntfy API base URL, default: https://ntfy.sh - PUSH_PLUS_TOKEN: PushPlus token - PUSH_PLUS_BASE_URL: PushPlus API base URL, default: http://www.pushplus.plus

Available tools

This MCP server exposes a collection of tools to send messages via different providers. Each tool handles a specific channel or action.

Troubleshooting and tips

If you encounter connection issues, verify that the selected HTTP endpoint is reachable and that required credentials are correctly set. For local stdio usage, ensure the command and arguments exactly match the deployment method you chose.

Notes and tips

You can mix multiple endpoints to broadcast to different providers from a single MCP client. Keep credentials secure and rotate tokens as needed. For streaming HTTP, monitor any latency or timeouts and adjust provider base URLs if you deploy behind proxies.

wework_send_text

Send a text or Markdown message to WeChat Work

wework_send_image

Send an image message to WeChat Work

wework_send_news

Send a news/linked content message to WeChat Work

wework_app_send_text

Send a text or Markdown message using WeChat Work app channel

wework_app_send_image

Send an image message using WeChat Work app channel

wework_app_send_video

Send a video message using WeChat Work app channel

wework_app_send_voice

Send a voice message using WeChat Work app channel

wework_app_send_file

Send a file message using WeChat Work app channel

wework_app_send_news

Send a news/linked content message using WeChat Work app channel

tg_send_message

Send a text or Markdown message via Telegram Bot

tg_send_photo

Send a photo via Telegram Bot

tg_send_video

Send a video via Telegram Bot

tg_send_audio

Send an audio message via Telegram Bot

tg_send_file

Send a file via Telegram Bot

ding_send_text

Send text or Markdown message via DingTalk group bot

lark_send_text

Send text or Markdown via Feishu/Lark bot

bark_send_notify

Send a notification via Bark

ntfy_send_notify

Send a notification via Ntfy

pushplus_send_msg

Send a message via PushPlus

ha_send_mobile

Send a notification to Home Assistant mobile app

text_to_sound

Convert text to MP3 audio link