Entergram Telegram MCP

Entergram Telegram MCP gives an assistant access to a shared workspace built around a team's personal Telegram accounts. The official hosted server connects over HTTP using OAuth with PKCE and scoped permissions. A stdio bridge is also available for clients unable to complete remote OAuth. Its distinguishing feature is access to personal-account conversations within a CRM workspace that combines a shared inbox, contact records and support workflows.

Highlights

• Read and search conversations across the personal Telegram accounts pooled in Entergram.
• Reply to chats when the client's permissions allow message sending.
• Edit contact records within a workspace that includes pipeline stages and custom fields.
• Open support tickets alongside the team's shared inbox workflows.
• Send messages in bulk to contact segments through personal Telegram accounts.

Good to know

• MCP access is included only in Pro, priced at 39 EUR per seat per month after a three-day trial.
• Permissions can restrict a client to reading chats or permit actions such as sending messages and editing contacts.
• The GitHub repository contains the stdio bridge; most current clients can use the hosted HTTP endpoint directly.
• Messages use real personal accounts, so responsibility for account conduct remains with their owners.

It fits teams managing Telegram sales or support together. Access follows a paid, per-seat subscription model through Entergram Pro.