OmniBridge MCP is a multi-channel notification gateway that lets AI agents push alerts to chat platforms and inspect channel/queue health.
Send Telegram messages (Markdown, optional silent mode) to a chat ID, user, or @channel.
Send Discord webhook messages or rich embeds (title, description, color) with an optional per-call webhook override.
Check configuration and readiness of all connected notification channels via get_channel_status.
Per README, also supports Slack, WhatsApp Cloud API, Matrix, and HMAC-SHA256 signed custom webhooks, plus a persistent SQLite WAL retry queue with stats and flush tools.
Includes SSRF/prefix guards, rate limiting, and token redaction for safe outbound delivery.
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., "@OmniBridge MCP send a Discord alert that the nightly build failed"
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.
OmniBridge MCP is a Model Context Protocol (2024-11-05) notification and webhook gateway that lets AI agents send alerts across Telegram, Discord, Slack, WhatsApp Cloud API, Matrix, and HMAC-signed webhooks with per-channel rate limiting and a persistent SQLite WAL retry queue.
6 Outbound Channels: Telegram Bot API, Discord Webhooks, Slack Block Kit Webhooks, WhatsApp Cloud API, Matrix rooms, and HMAC-SHA256 custom webhooks.
Outbound SSRF & Prefix Guards: Enforces official https://discord.com/api/webhooks/ and https://hooks.slack.com/ prefixes even on per-call overrides, blocks loopback/RFC1918/link-local (169.254.169.254) webhook targets, URL-encodes Matrix room IDs, and redacts bot tokens from transport errors.
Persistent SQLite WAL Queue & Flush Worker: Rate-limited and transient 5xx/network failures are stored in ~/.omnibridge/queue.db (0600 permissions) and retried with exponential backoff via flush_queue or omnibridge-cli flush.
Related MCP server: mcp-telegram
uvxuvx omnibridge-mcp{
"mcpServers": {
"omnibridge-mcp": {
"command": "uvx",
"args": ["omnibridge-mcp"],
"env": {
"TELEGRAM_BOT_TOKEN": "your_bot_token_here",
"DISCORD_WEBHOOK_URL": "https://discord.com/api/webhooks/..."
}
}
}
}omnibridge-cli status
omnibridge-cli flush
omnibridge-cli test --channel discord --message "OmniBridge test alert"Tool | Parameters | Description |
|
| Send a Telegram notification with Markdown formatting |
|
| Send a Discord webhook message or rich embed |
|
| Send a WhatsApp Cloud API text message |
|
| Send a Slack Block Kit webhook notification |
|
| Send a Matrix room event ( |
|
| Deliver a JSON webhook signed with |
| (none) | Return pending, retrying, delivered, and failed counts in the SQLite WAL queue |
|
| Process due messages in the SQLite WAL retry queue |
| (none) | Return configuration status for all 6 channels and current queue counts |
Module | Description | Repository |
CrawlEngine MCP | HTTP web extraction to clean Markdown, JSON-LD parsing, and proxy rotation | |
BrowserBridge MCP | Lightweight HTTP/DOM session automation with SHA-256 action receipts | |
PgSafe MCP | Read-only PostgreSQL/SQLite query guard, PII masking, and dry-run mutations | |
OmniBridge MCP | Multi-channel notification bus with SQLite retry queue | |
SysFlow MCP | Linux systemd inspection, confined log tailing, and port auditing | |
FastMCP Forge | Zero-dependency FastMCP framework, CLI scaffolder, and SSE middleware |
If you find this project useful, you can support maintenance on Ko-fi.
MIT (c) 2026 Johann Schiffer
Check configuration and operational readiness of all connected notification channels.
Inputs: no named parameters.
Send a rich webhook notification or embed to a Discord channel.
Inputs: color, title, content, description, +1 more.
Send a real-time notification or message to a Telegram chat, user, or channel.
Inputs: text (required), chat_id (required), disable_notification.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 3 tools
Each tool has a clearly distinct purpose: sending to Telegram, sending to Discord, and checking channel status. There is no overlap in the resource+action pairs, so an agent can select unambiguously.
All three follow a consistent snake_case verb_noun pattern (send_telegram_message, send_discord_alert, get_channel_status). The only minor deviation is the noun choice (message vs. alert) between the two send tools, but the structure remains predictable.
Three tools is a reasonable, well-scoped set for a notification bridge, with each tool earning its place. It is on the lean side, supporting only two channels plus a status check, but nothing is redundant.
Despite the 'OmniBridge' name implying broad multi-channel coverage, only Telegram and Discord are supported, and there is no tool to configure or add channels. Core send and status operations exist, but channel lifecycle and broader integrations are notable gaps.
Telegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
