A small stdio Model Context Protocol server that sits between your local agent (Cursor, Claude Desktop, Windsurf, Grok/Cursor agents, and others) and the Telegram Bot API. The agent owns conversation logic; this…
Telegram Bridge source profile. From the maintainer documentation: “A small stdio Model Context Protocol server that sits between your local agent (Cursor, Claude Desktop, Windsurf, Grok/Cursor agents, and others) and the Telegram Bot API. The agent owns conversation logic; this process handles I/O, always-on outbound scrubbing, and chat allowlist enforcement. Optional strict inbound classification is disabled by default.”
The documented pypi package is mcp-telegram-bridge. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.
The example declares TELEGRAM_BOT_TOKEN, ALLOWED_CHAT_IDS. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| telegram_get_me | Bot identity / connectivity check |
| telegram_send_message | chat_id, text, optional parse_mode, optional buttons=[{id,label}] |
| telegram_edit_reply_markup | Strip or replace inline buttons |
| telegram_answer_callback | Ack a callback_query_id (optional toast) |
| telegram_get_updates | offset, limit, timeout - returns messages + callback_queries; agent owns the loop |
| telegram_get_chat | Chat metadata |
{
"mcpServers": {
"telegram-bridge": {
"command": "uvx",
"args": [
"--from",
"mcp-telegram-bridge",
"mcp-telegram-bridge"
],
"env": {
"TELEGRAM_BOT_TOKEN": "YOUR_TELEGRAM_BOT_TOKEN",
"ALLOWED_CHAT_IDS": "-1001234567890"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| TELEGRAM_BOT_TOKEN | Declared in the maintainer’s client configuration. | Check documentation |
| ALLOWED_CHAT_IDS | Declared in the maintainer’s client configuration. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Send transactional emails from AI agents via Truncus. Validate, track delivery, and manage domains.
Ephemeral mailboxes and a mock OAuth IdP for testing email and auth flows — 39 API-driven tools
A comprehensive Model Context Protocol (MCP) server that provides tools for managing PocketBase instances. This server enables LLMs to interact with PocketBase databases through a standardized…
ThinAir Geo is the geospatial intelligence layer behind ThinAir fleet workflows: geocoding, routing context, address search, service-area visibility, map intelligence, traffic, weather, and…