Xiaoman Message Center
Enables sending messages to the Xiaoman notification relay via Gmail using predefined subject formats, with Gmail message IDs used as idempotency keys.
Provides a Google Apps Script integration that relays Gmail messages to Xiaoman, storing credentials in Script Properties and using Gmail message IDs for deduplication.
Allows delivering notification messages to Telegram chats through a bot, including automatic splitting of long messages and retries for failed deliveries.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Xiaoman Message CenterSend the daily report to my QQ and Telegram groups"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Xiaoman Message Center
A self-hosted notification relay for scheduled AI workflows. Your task generates the final content; Xiaoman authenticates, routes, delivers, retries, and audits it across QQ and Telegram.
The relay does not call a paid LLM API. Your ChatGPT, Cloudflare, Gmail, QQ, and Telegram accounts may still have their own plans, quotas, and limits.
Why Xiaoman
One stable route can deliver to one or many destinations.
Send through REST, MCP, or Gmail plus Google Apps Script.
Split long messages for QQ and Telegram automatically.
Prevent duplicate delivery with optional idempotency keys.
Retry only destinations that did not succeed.
Review routes, destinations, and recent delivery status in the dashboard.
Keep channel credentials in the runtime environment—not in the database or repository.
Related MCP server: notify-hub
Architecture
Scheduled task / Gmail / MCP / REST
│
▼
authentication + validation
│
▼
route resolution
│ │
▼ ▼
QQ bot Telegram bot
│
▼
D1 delivery audit + retryFive-minute local setup
Prerequisite: Node.js 22.13 or newer.
npm ci
cp .env.example .env.local
npm run build
npm run db:local:init
npm run devFor local or standalone use, set AUTH_MODE=basic, choose a strong ADMIN_BASIC_USER and ADMIN_BASIC_PASSWORD, and generate independent random values for NOTIFICATION_API_TOKEN and MCP_BEARER_TOKEN. Then add at least one QQ or Telegram adapter credential.
See the English quickstart or 中文快速开始 before sending a real message.
Two safe examples
Daily Commute Plan: a sanitized weather and travel briefing using placeholders for all locations.
Daily Health Report: a fictional wellness summary; it is not medical advice.
Both examples include REST, MCP, and Gmail subject patterns. No production route, destination, email address, personal location, or health record is included.
Gmail relay
The copy-paste Google Apps Script integration lives in integrations/google-apps-script. It stores credentials in Script Properties, uses Gmail message IDs as idempotency keys, and supports both subject formats:
小慢消息中心 每日通勤计划|2026-09-16
Xiaoman Message Center Daily Commute Plan | 2026-09-16Deployment paths
OpenAI Sites: keeps Sign in with ChatGPT and managed D1 deployment. The official product overview is available in the OpenAI Sites documentation.
Standalone Cloudflare: uses the included HTTP Basic authentication mode and your own D1 database.
Sites deployment URLs are production URLs. Review the source and configuration before deploying or changing access.
Documentation
Topic | English | 简体中文 |
Quickstart | ||
Architecture | ||
Configuration | ||
Sites deployment | ||
Cloudflare deployment | ||
QQ and Telegram | ||
REST and MCP | ||
Privacy and security |
Development
npm run lint
npm run verifyTests mock the message workflow and never send to a real QQ group or Telegram chat. Read CONTRIBUTING.md before opening a pull request.
License
MIT. The name and bundled mascot assets may be used with this repository under the same license; they do not imply endorsement of a modified deployment.
This server cannot be deployed
Maintenance
Related MCP Connectors
Build and send email, SMS, and push straight from your AI agent.
Let your AI agent notify you by email, Slack, Discord, or webhook. One tool: send_notification.
Connect any AI agent to 11+ social platforms: schedule, publish & track posts via hosted MCP.
Push notifications for AI agents - send instant iPhone notifications from any MCP client.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables sending messages and scheduling reminders through multiple platforms including Telegram and Feishu. Supports real-time messaging and cron-based scheduled notifications with comprehensive logging and error handling.MIT
- AlicenseNot gradedqualityCmaintenanceUnified notification MCP server with 36 tools to send messages across 23 channels — Email, SMS, Slack, Telegram, Discord, Teams, WhatsApp, Firebase Push, and more.5MIT
- FlicenseNot gradedqualityCmaintenanceEnables creating and managing automated workflows with triggers, actions, webhooks, and pre-built templates, integrating with notification services like DingTalk, WeChat, Slack, and email.-
- AlicenseNot gradedqualityCmaintenanceEnables sending real-time and webhook notifications when AI agents complete tasks, with support for Discord, Slack, Teams, Feishu, Ntfy, and custom webhooks.6MIT