Mcp Notify

Please install the `mcp-notify` MCP server into my current AI client (that's you).

Optional prerequisites:
- Messaging channel credentials — Depending on which channels you use, set env vars for WeCom, DingTalk, Telegram, Bark, Lark/Feishu, Home Assistant, Ntfy, or PushPlus

Canonical MCP server config (stdio transport):
- command: `uvx`
- args: ["mcp-notify"]
- optional environment variables:
  - `WEWORK_BOT_KEY`: WeCom bot key (example: `<your-bot-key>`)
  - `DINGTALK_BOT_KEY`: DingTalk bot access_token (example: `<your-token>`)
  - `FEISHU_BOT_KEY`: Feishu/Lark bot key (example: `<your-bot-key>`)
  - `TELEGRAM_BOT_TOKEN`: Telegram bot token (example: `<your-token>`)
  - `TELEGRAM_DEFAULT_CHAT`: Telegram default chat ID (example: `<chat-id>`)
  - `BARK_DEVICE_KEY`: Bark device key (example: `<your-device-key>`)
  - `HASS_BASE_URL`: Home Assistant base URL (example: `http://homeassistant.local:8123`)
  - `HASS_ACCESS_TOKEN`: Home Assistant long-lived access token (example: `<your-token>`)

Note: Message push MCP server for WeCom, DingTalk, Telegram, Bark, Lark/Feishu, Home Assistant, Ntfy, PushPlus. README mostly in Chinese.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.