OmniBridge MCP
# OmniBridge MCP (Lite Edition)
[](LICENSE)
[](https://python.org)
[](https://modelcontextprotocol.io)
**OmniBridge MCP** is a lightweight, zero-latency Model Context Protocol server that gives AI agents (in **Claude Desktop**, **Cursor**, **Windsurf**, and **Antigravity**) direct, controlled access to send real-time alerts, operational notifications, and webhooks without exposing your primary API keys or relying on bloated middleware.
---
## โก Key Features (Lite Edition)
- ๐ **Zero Heavy Dependencies**: Pure Python implementation with minimal footprint (`httpx`).
- ๐ฌ **Telegram Bot API**: Send markdown-formatted alerts, silent notifications, and direct messages.
- ๐ฎ **Discord Webhooks**: Send rich embed cards with custom colors, titles, and timestamps.
- ๐ **Universal Compatibility**: Works out of the box with any MCP-compliant client via standard IO (`stdio`).
- ๐งช **Built-in CLI**: Interactive test tool to verify credentials and channel delivery in seconds.
---
## ๐ Quick Setup in 2 Minutes
### 1. Installation
```bash
git clone https://github.com/johannschiffer/omnibridge-mcp.git
cd omnibridge-mcp
pip install -r requirements.txt
```
### 2. Environment Variables
Create a `.env` file or export variables in your shell:
```bash
# Telegram Bot Token (from @BotFather)
export TELEGRAM_BOT_TOKEN="123456789:ABCdefGhIJKlmNoPQRsTUVwxyZ"
# Discord Webhook URL (from Channel Settings -> Integrations -> Webhooks)
export DISCORD_WEBHOOK_URL="https://discord.com/api/webhooks/..."
```
### 3. Verify with CLI
```bash
# Check channels configuration
python -m omnibridge.cli status
# Send a test alert to Discord
python -m omnibridge.cli test --channel discord --message "OmniBridge is live!"
```
---
## ๐ฅ๏ธ Client Configuration
### Claude Desktop (`claude_desktop_config.json`)
On macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%\Claude\claude_desktop_config.json`
On Linux: `~/.config/Claude/claude_desktop_config.json`
```json
{
"mcpServers": {
"omnibridge": {
"command": "python",
"args": ["-m", "omnibridge.server"],
"cwd": "/path/to/omnibridge-mcp",
"env": {
"TELEGRAM_BOT_TOKEN": "your_bot_token_here",
"DISCORD_WEBHOOK_URL": "your_discord_webhook_url_here"
}
}
}
}
```
### Cursor (`.cursor/mcp.json`)
```json
{
"mcpServers": {
"omnibridge": {
"command": "python -m omnibridge.server",
"env": {
"TELEGRAM_BOT_TOKEN": "your_bot_token_here",
"DISCORD_WEBHOOK_URL": "your_discord_webhook_url_here"
}
}
}
}
```
---
## ๐ ๏ธ MCP Tools Available
| Tool | Parameters | Description |
|---|---|---|
| `send_telegram_message` | `chat_id`, `text`, `disable_notification` | Sends Telegram notification with Markdown support |
| `send_discord_alert` | `content`, `title`, `description`, `color`, `webhook_url` | Sends Discord rich embed card |
| `get_channel_status` | *(none)* | Returns connectivity and health of all channels |
---
## ๐ Need Enterprise Features? Upgrade to OmniBridge Pro
Looking for production-grade reliability, business messaging, and fault tolerance?
| Feature | Lite (Open Source) | Pro ($14.99 USD) |
|---|:---:|:---:|
| **Telegram Bot API** | โ
| โ
|
| **Discord Webhooks** | โ
| โ
|
| **WhatsApp Cloud API** | โ | โ
|
| **Slack Block Kit & Webhooks** | โ | โ
|
| **Matrix Protocol Rooms** | โ | โ
|
| **Custom Webhooks with HMAC** | โ | โ
|
| **Offline WAL Resilient Queue** *(Zero Message Loss)* | โ | โ
|
| **Adaptive Rate Limiting** *(Anti-ban protection)* | โ | โ
|
| **Production Docker & Compose** | โ | โ
|
| **Full Pytest Suite & Architecture PDF** | โ | โ
|
๐ **[Get OmniBridge Pro on Gumroad ($14.99)](https://johanld.gumroad.com/l/omnibridge-mcp-pro)**
---
## ๐ License
MIT License. See [LICENSE](LICENSE) for details.
TDQS
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.