Telegram Bridge runs on your own machine — the client starts it, so there is no endpoint to ping. 339 installs a week from pypi. Last commit 4 Nov 2026.
Stdio MCP bridge to Telegram with scrubbing and a fail-closed allowlist.
Today is the operative word: we check Telegram Bridge every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-telegram-bridge -- uvx mcp-telegram-bridge
{
"mcpServers": {
"mcp-telegram-bridge": {
"command": "uvx",
"args": [
"mcp-telegram-bridge"
]
}
}
}
[mcp_servers.mcp-telegram-bridge]
command = "uvx"
args = ["mcp-telegram-bridge"]
{
"mcpServers": {
"mcp-telegram-bridge": {
"command": "uvx",
"args": [
"mcp-telegram-bridge"
]
}
}
}
{
"servers": {
"mcp-telegram-bridge": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-telegram-bridge"
]
}
}
}
Agent email with allowlist and consent via AssistantMail.
Gate AI agent actions behind a consent policy with human approval via Telegram. Fail-closed.
Self-hosted, consent-based access to Telegram accounts and bots for MCP clients
Chat with Pally, the AI assistant in your texts and on Telegram, from any MCP-compatible AI app.
Read chats and members; send, edit and delete messages with a bot in Telegram.
Telegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack.
Retired compatibility stub for AgentCanary MCP. Daily briefs continue on X and Telegram.
Local-first TDLib Telegram MCP server with 126 tools, account isolation and production guardrails.
Answers built from our own checks of this server.