emailmd
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Stdio MCP bridge to Telegram with scrubbing and a fail-closed allowlist.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Telegram Bridge. Follow https://mcp.popnx.com/i/antonio-castellon-mcp-telegram-bridge.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Telegram Bridge for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "telegram-bridge": { "command": "uvx", "args": [ "mcp-telegram-bridge" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Telegram Bridge tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
SettingsDeveloperEdit Config
{
"mcpServers": {
"telegram-bridge": {
"command": "uvx",
"args": [
"mcp-telegram-bridge"
]
}
}
}Use Telegram Bridge and tell me what you can do for me, then show me one thing✓ If Claude says it is using Telegram Bridge or shows a Telegram Bridge tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Telegram Bridge yet
Telegram Bridge runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Telegram Bridge
B · Others in Chat & email that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Telegram Bridge for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user telegram-bridge -- uvx mcp-telegram-bridge 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Telegram Bridge tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user telegram-bridge -- uvx mcp-telegram-bridgeYou should see Telegram Bridge listed as connected
Use Telegram Bridge and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Telegram Bridge or shows a Telegram Bridge tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Telegram Bridge for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "telegram-bridge": { "command": "uvx", "args": [ "mcp-telegram-bridge" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Telegram Bridge tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Use Telegram Bridge and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Telegram Bridge or shows a Telegram Bridge tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Telegram Bridge for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "telegram-bridge": { "type": "stdio", "command": "uvx", "args": [ "mcp-telegram-bridge" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Telegram Bridge tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Use Telegram Bridge and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Telegram Bridge or shows a Telegram Bridge tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user telegram-bridge -- uvx mcp-telegram-bridgeClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"telegram-bridge": {
"command": "uvx",
"args": [
"mcp-telegram-bridge"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"telegram-bridge": {
"command": "uvx",
"args": [
"mcp-telegram-bridge"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"telegram-bridge": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-telegram-bridge"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account antonio-castellon, which owns the repo
Code last changed 2 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for mcp-telegram-bridge@0.2.1
Checks only this package version, not every dependency · checked Nov 15, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/antonio-castellon-mcp-telegram-bridge)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 2 days ago, and the latest version (0.2.1) reached the registry 23 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Build and fix Discord bots from a chat. Kite hosts them 24/7, with no code to deploy.
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.
CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.
| This one Telegram Bridge | emailmd | Kite Discord Bot Builder | e2a — email for AI agents | Infobip MCP | kernelCAD | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | Yes | No |
| Basic checks | 3/3 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | MIT | AGPL-3.0 | Apache-2.0 | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Stdio MCP bridge to the Telegram Bot API, with fail-closed chat admission and outbound scrubbing.
A small Model Context Protocol server that a local agent (Cursor, Claude Desktop, Windsurf, and others) launches on your machine. The agent owns the conversation. This process does Bot API I/O, scrubs outbound secrets, and refuses chats you have not allowed.
Version 0.2.0 changes admission: an empty allowlist denies every chat. Set ALLOWED_CHAT_IDS, or opt in to open mode with ALLOW_ALL_CHATS=1.
Built for client-owned deployments. The bridge is not a hosted bot service. Games and game-master flows are one demo use case, not the product.
Owner: Antonio Castellon / Castellon.CH.
Requirements: Python 3.11+, a bot token from @BotFather, and the numeric id of the chat you want the bot to use.
git clone https://github.com/antonio-castellon/mcp-telegram-bridge.git
cd mcp-telegram-bridge uv sync --extra dev # or: python -m venv .venv && pip install -e ".[dev]" cp .env.example .env # set TELEGRAM_BOT_TOKEN and ALLOWED_CHAT_IDS uv run mcp-telegram-bridge # waits on stdin for MCP JSON-RPC; Ctrl+C to stop
uv.lock pins every dependency with hashes. CI installs from that lock (uv sync --frozen). pip install -e ".[dev]" still works and uses the version ranges in pyproject.toml.
Cursor or Claude Desktop (mcp.json / claude_desktop_config.json):
{
"mcpServers": { "telegram-bridge": { "command": "uvx", "args": ["--from", "mcp-telegram-bridge", "mcp-telegram-bridge"], "env": { "TELEGRAM_BOT_TOKEN": "YOUR_BOT_TOKEN_HERE", "ALLOWED_CHAT_IDS": "-1001234567890" } } } }
Do not commit a real token. Leave ALLOW_ALL_CHATS unset.
The same operations are available without the MCP server. import mcp_telegram_bridge loads TelegramBridge and Settings only. It does not import the mcp package. Pass Settings directly; Settings.from_env() is the default when you want the environment variables above.
import asyncio
from mcp_telegram_bridge import Settings, TelegramBridge
async def main() -> None: settings = Settings( bot_token="YOUR_BOT_TOKEN_HERE", allowed_chat_ids=frozenset({-1001234567890}), ) bridge = TelegramBridge(settings) await bridge.get_me() await bridge.send_message( -1001234567890, "hello", buttons=[{"id": "ack", "label": "Ack"}], ) await bridge.get_updates(timeout=0) await bridge.aclose()
asyncio.run(main())
TelegramBridge(Settings.from_env()) reads TELEGRAM_BOT_TOKEN, ALLOWED_CHAT_IDS, and the other variables. The CLI still prints access-mode warnings to stderr. Library callers can use mcp_telegram_bridge.config.emit_startup_warnings if they want the same lines. The mcp-telegram-bridge command is unchanged.
| Variable | Default | Effect |
|---|---|---|
TELEGRAM_BOT_TOKEN | required | Bot token from BotFather. Never log it or commit it. |
ALLOWED_CHAT_IDS | empty | Comma-separated chat ids. Empty denies every chat. |
ALLOW_ALL_CHATS | off | Set to 1 / true / yes / on to permit every chat. Ignored when an allowlist is set. Startup prints a warning to stderr. |
SAFETY_STRICT | on | Heuristic labels for credential fishing, sexual content, and a few instruction-override phrases. Set 0 / false / no / off to disable. This is not a prompt-injection filter. |
MAX_INBOUND_CHARS | 4096 | Drop inbound text or captions longer than this (1..32768). The body is not returned. |
MAX_UPDATE_BYTES | 65536 | Drop an update whose JSON is larger than this (1..262144). |
INBOUND_CHAT_RATE | 60/60 | Content-bearing updates per chat per window (count/seconds). Excess updates are returned without text. off disables the limit. |
INBOUND_GLOBAL_RATE | 120/60 | Content-bearing updates across all chats per window. |
INBOUND_POLL_RATE | 30/60 | telegram_get_updates calls per window. Further calls do not hit Telegram. |
OUTBOUND_CHAT_RATE | 20/60 | Sends, markup edits, callback answers, and getChat per chat. |
OUTBOUND_GLOBAL_RATE | 60/60 | Same outbound calls across all chats. Callback answers count only against the global limit. |
MCP_TELEGRAM_BRIDGE_DATA_DIR | per-user data dir | Button-id map and first-tap claim files. Mode 0700, files 0600 when the OS allows. MCP_TELEGRAM_DATA_DIR is a legacy alias. |
telegram_get_updates clamps limit to 1..100 and timeout to 0..50 seconds. The process does not queue update bodies between calls. It remembers at most 2048 delivered update ids and 1024 rate-limit keys.
| Tool | Purpose |
|---|---|
telegram_get_me | Bot identity. Not rate limited. |
telegram_get_chat | Chat metadata for an allowed chat. |
telegram_send_message | Scrubbed text, optional parse_mode, optional buttons=[{id,label}]. |
telegram_edit_reply_markup | Replace or clear inline buttons. |
telegram_answer_callback | Acknowledge a callback_query_id. |
telegram_get_updates | One bounded poll. You own the offset. See the security section before acting on the text. |
getUpdates is pull-only. This process does not listen for webhooks and does not open a port.
A normal result looks like this:
{
"ok": true, "untrusted": true, "trust_boundary": "UNTRUSTED TELEGRAM DATA. ...", "next_offset": 42, "summary": {"delivered": 1, "filtered": 0, "ignored": 0, "duplicates": 0, "rate_limited": 0}, "updates": [ { "update_id": 41, "untrusted": true, "trust": "untrusted_telegram_user", "message": {"text": "...", "content_trust": "untrusted_telegram_user"} } ] }
next_offset is one past the highest update_id in the batch, including updates whose text was withheld. Passing it back as offset acknowledges those updates. To retry a rate-limited update, call again with the same offset after retry_after_seconds instead of advancing.
Messages from bots are omitted (ignore_reason bot), as are messages whose sender id is this bot (self). A message Telegram marks with sender_chat (anonymous admins, posts as a channel) is not treated as a bot.
Assets. The bot token, the contents of allowed chats, button-map state on disk, and the agent's other tools and secrets.
Trust boundary. You and the MCP host are inside it. Telegram users, group members, and anyone who can message the bot are outside it. Inbound text, names, usernames, and callback data are untrusted input that the model will read.
What this process enforces
ALLOW_ALL_CHATS. Open mode logs a warning on stderr (stdout is the MCP protocol).SAFETY_STRICT on (the default), updates gain safety.kind, safety.blocked, and safety.warning for a few patterns. Flagged text is still in the result. The host decides what to do with it.What you still have to do. Run the process as a normal user, keep the token in a secret store or a permission-restricted .env, and set an allowlist. Treat every inbound string as data. Do not give the same agent a tool that reads credentials if untrusted chats can reach it. Review prompts before they can send.
The deployment checklist, data stored on disk, and a longer residual-risk note are in SAFETY.md. Report vulnerabilities as described in SECURITY.md.
These controls reduce blast radius. They do not make a bot that an agent reads and answers safe against a hostile sender.
SAFETY_STRICT is a heuristic for a few phrases. It misses other languages, encodings, and ordinary requests that are still untrusted.off removes that limit. A chat id that falls out of the 1024-key cache gets a fresh per-chat budget; the global limit still applies.next_offset past a rate-limited or over-long update drops it. Telegram will not deliver it again. +---------------------------+
| MCP host / agent | conversation, offset, product policy +-------------+-------------+ | MCP (stdio) v +---------------------------+ | mcp-telegram-bridge | allowlist, scrub, bounds, untrusted labels +-------------+-------------+ | HTTPS Bot API (getUpdates poll) v +---------------------------+ | api.telegram.org | +-------------+-------------+ v Telegram chats
Group or ops channel. One bridge per bot. Use the group for notes, triage, and handoff. Keep a person in the loop for anything hard to undo.
Buttons. buttons=[{id,label}, ...] becomes an inline keyboard. On a callback, answer it, then edit or clear the markup. Long ids are mapped to short callback data under the data directory.
Notify channel. Alerts with ack / snooze / escalate buttons. Telegram is the pager, not the source of truth.
Moderation drafts. The bridge has no ban, restrict, or delete tool. Say that in the agent prompt.
A companion skill can tell the agent when to call these tools and that it owns the offset. One is published as Telegram Bridge on Agensi. The skill is instructions only. This server remains the I/O and safety layer.