MCP Telegram Bridge

Purpose: Connecting MCP agents to Telegram while controlling allowed chats and sanitizing outbound messages.

Inferred · not functionally tested

Audience: developers building MCP hosts and agent integrations

Inferred · not functionally tested

Functions: agents, collaboration

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: Open Source · platforms: DESKTOP, CLI, WEB · deployment: browser, cli, api_only, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

In the Frameworks & SDKs space, MCP Telegram Bridge takes a focused approach. Inferred · not functionally tested: It focuses on connecting MCP agents to Telegram while controlling allowed chats and sanitizing outbound messages. Inferred · not functionally tested: It is built as an open-source project for developers building MCP hosts and agent integrations. Basis unknown · not verified: The project is open source (Open Source). Basis unknown · not verified: MCP Telegram Bridge is available on the web, the command line, and API, and it can be self-hosted.

Behind MCP Telegram Bridge is Antonio Castellón. Inferred · not functionally tested: Key capabilities include telegram messaging, MCP host bridge, and Bot API I/O. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.