Back to Browse

Telegram Bridge MCP Server

CommunicationLow Risk10.0LocalNew
Free

Stdio MCP bridge to Telegram Bot API with scrubbing and chat allowlist.

About

Controlled Telegram channel bridge for any MCP host (Cursor, Claude Desktop, Windsurf, and others). A small stdio Model Context Protocol server that sits between your local agent and the Telegram Bot API. The agent owns conversation logic; this process handles I/O, always-on outbound secret scrubbing, and optional chat allowlist enforcement. Optional strict inbound classification is off by default.

Built for client-owned deployments: the bridge runs on your machine. Games and game-master flows are one demo use case, not the product. Same control-layer pattern is useful for SME notify channels, specialist handoff, and moderated drafts alongside email or ERP connectors.

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (2 strong, 3 medium validity signals). 1 code issue detected. No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

11 files analyzed · 2 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Bot token from @BotFather. Never commit this value.Required

Environment variable: TELEGRAM_BOT_TOKEN

Comma-separated Telegram chat IDs the bridge may send to. Leave empty only if you intentionally accept every chat the bot can see.Optional

Environment variable: ALLOWED_CHAT_IDS

Set to `1` / `true` / `yes` / `on` to enable heuristic inbound secret/NSFW classification on `telegram_get_updates`. Default is off.Optional

Environment variable: SAFETY_STRICT

Directory for button-map / claim state (defaults to platform user data dir). Created with restrictive permissions when possible.Optional

Environment variable: MCP_TELEGRAM_BRIDGE_DATA_DIR

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-antonio-castellon-mcp-telegram-bridge": {
      "args": [
        "mcp-telegram-bridge"
      ],
      "command": "uvx"
    }
  }
}

Getting Started

Once installed, try these example prompts and explore these capabilities:

  • 1"Check that the Telegram bot is online" → uses `telegram_get_me`
  • 2"Send this triage note to the ops chat with Ack / Snooze buttons" → `telegram_send_message` with buttons
  • 3"Poll for new messages and button taps" → `telegram_get_updates` (agent owns the offset loop)
  • 4"Clear the spent buttons on that message" → `telegram_edit_reply_markup`
  • 5"Acknowledge this callback query" → `telegram_answer_callback`

Reviews

No reviews yet

Be the first to review this server!

Version History

v0.1.2Sep 23, 2026Re-scanned

Updated to version 0.1.1.