Telegram Bridge runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 21 Sep 2026.
Stdio MCP bridge to Telegram Bot API with scrubbing and chat 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": {
"args": [
"mcp-telegram-bridge"
],
"command": "uvx"
}
}
}
[mcp_servers.mcp-telegram-bridge]
command = "uvx"
args = ["mcp-telegram-bridge"]
{
"mcpServers": {
"mcp-telegram-bridge": {
"args": [
"mcp-telegram-bridge"
],
"command": "uvx"
}
}
}
{
"mcpServers": {
"mcp-telegram-bridge": {
"args": [
"mcp-telegram-bridge"
],
"command": "uvx"
}
}
}
Chat with Pally, the AI assistant in your texts and on Telegram, from any MCP-compatible AI app.
MCP server that exposes a Telegram bot
Agent email with allowlist and consent via AssistantMail.
A dynamic, self-refreshing MCP gateway for the complete Telegram Bot API
MCP server for Telegram Archive — search messages, browse chats, and access history
Read and reply to your personal Telegram chats and all your Slack workspaces.
Self-hosted, consent-based access to Telegram accounts and bots for MCP clients
Telegram for AI agents: messages, chats, media, and contacts in bot and user-account modes.
Answers built from our own checks of this server.