An MCP server that lets AI agents (Claude, Cursor, etc.) reach you on any channel — desktop, Telegram, SMS, email — with two-way ask/reply, real-time
An MCP server that lets AI agents (Claude, Cursor, etc.) reach you on any channel — desktop, Telegram, SMS, email — with two-way ask/reply, real-time inbox push, Do Not Disturb, idle gating, multi-session routing, and a one-page web UI for. Exposed over MCP by the omni mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Reach me on any channel. Ask me anything. Get out of my way when I'm busy.
Everything the assistant can do here goes through one of these:
Desktop — native node-notifier (macOS/Windows/Linux). Per-channel system-sound toggle and optional text-to-speech with a voice picker covering 30+Telegram — bidirectional. The bot replies in-thread to user messages and acknowledges every inbound message so the user knows it landedSMS — TwilioEmail — Gmail App Password (one click) or any SMTP. ask over email sends a reply link the user clicks to answerPriority — Channelslow — email onlynormal — desktop + Telegram + emailhigh — desktop + Telegram + SMS + email — bypasses DND and idle gatingPath — PurposeChannels — The Channels tool exposed by this serveromni-notify-ui on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 2 environment variables: CLAUDE_FILE_PATH, CHAT_ID. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Omni's toolset — Desktop, Telegram, SMS and 7 more — is a fair guide to whether it matches your workflow. It is maintained by karish911; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Desktop | native node-notifier (macOS/Windows/Linux). Per-channel **system-sound toggle** and optional **text-to-speech** with a voice picker covering 30+ neural voices (US/UK/AU/CA/IN/IE/NZ/…) via msedge-tts, no API key. |
| Telegram | bidirectional. The bot **replies in-thread** to user messages and acknowledges every inbound message so the user knows it landed. |
| SMS | Twilio. |
| Gmail App Password (one click) or any SMTP. ask over email sends a reply link the user clicks to answer. | |
| Priority | Channels |
| low | email only |
| normal | desktop + Telegram + email |
| high | desktop + Telegram + SMS + email — **bypasses DND and idle gating** |
| Path | Purpose |
| Channels | The Channels tool exposed by this server. |
{
"mcpServers": {
"notify-1": {
"command": "npx",
"args": ["-y", "omni-notify-ui"],
"env": {
"CLAUDE_FILE_PATH": "your-value",
"CHAT_ID": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| CLAUDE_FILE_PATH | Filesystem location the server is allowed to use. | Optional |
| CHAT_ID | Configuration value read at startup. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.