Telegram

@telegram show me the last 20 messages from our #product-updates channel so I can draft a weekly summary

Retrieved 20 recent messages from #product-updates. The channel shows 8 feature announcements, 5 bug-fix notifications, 4 deployment confirmations, and 3 user feedback threads. Most active discussion centered around the new dashboard redesign (12 replies) and API rate-limit adjustments (7 replies). Messages span March 15-22, with peak activity on March 18.

This example uses Get Chat History to fetch messages. Requires the bot to be added to the target channel with read permissions. Telegram's getUpdates method has a 100-message rolling window, so 'last 20' works reliably but deeper history may require adjusting your bot's offset parameter or using a different retrieval strategy.

@telegram forward the message about Q1 roadmap priorities from Sarah to our #leadership-sync channel

Forwarded Sarah's message (sent March 20, 2:34 PM) to #leadership-sync. The message contained a bulleted list of 5 Q1 priorities with owner assignments and target dates. Forward preserved the original timestamp and sender attribution. Message ID in destination channel: 8472.

This demonstrates Forward Message for cross-channel coordination. The bot must have posting permissions in the destination channel. Forwarded messages retain original sender context, which helps preserve attribution but means you can't anonymize or rewrite content during the forward—use Edit Message afterward if you need to add context.

@telegram who are the admins in our #engineering channel and what permissions does each one have?

Found 4 administrators in #engineering: Alex Chen (creator, all permissions), Jordan Kim (can delete messages, pin messages, invite users), Sam Patel (can manage video chats, invite users), and @ProductBot (can post messages, edit messages). Two members have restricted 'can invite users' only. The channel has 47 total members.

Uses Get Chat Administrators to audit channel governance. Useful for onboarding or security reviews. Returns ChatMember objects with granular permission flags, but the MCP won't show you *why* someone has those permissions (manual grant vs. role inheritance). If your bot isn't an admin itself, this call will fail with a 'not enough rights' error.

When Telegram MCP beats email for support handoffs

A 6-person support team uses Telegram as their primary customer channel and needs AI to draft replies, escalate to the right person, and log resolutions. This MCP is the right call if your team already lives in Telegram and handles under 200 tickets a day. The Edit Message and Answer Callback Query tools let Switchy refine responses inline and handle button clicks without switching contexts. The Get Chat History tool pulls recent context so the AI doesn't ask customers to repeat themselves. The threshold: if you need structured ticket IDs or SLA tracking, Telegram's flat chat model gets messy fast—Linear or Zendesk MCPs win there. But for conversational support where speed matters more than audit trails, this MCP keeps your team in one place and cuts reply time in half.

Telegram MCP for group chat moderation workflows

A 2-person community team moderates a 50-member Telegram group for a SaaS product's power users. They need AI to flag spam, answer repeat questions, and surface admin requests without reading every message. This MCP works if your group is under 100 members and you trust the bot with admin rights. The Get Chat Administrators and Delete Message tools let Switchy enforce rules and remove bad actors. The Forward Message tool escalates edge cases to a private admin chat. The trade-off: Telegram's API doesn't expose message sentiment or thread structure, so the AI can't distinguish heated debate from actual toxicity without reading full history. If your community is over 200 members or spans multiple groups, Discord's richer metadata wins. For tight-knit groups where you know the regulars, this MCP automates the grunt work and keeps moderators focused on real problems.

When Telegram MCP fits inbound lead capture

A 3-person sales team at a B2B startup uses a Telegram bot to capture inbound leads from a landing page. Prospects message the bot with questions, and the team needs AI to qualify intent, book demos, and route hot leads to Slack. This MCP is the right call if you get under 50 leads a week and your buyers prefer chat over forms. The Get Bot Info and Edit Message tools let Switchy personalize responses and correct mistakes mid-conversation. The Export Chat Invite Link tool generates one-time links for demo groups. The boundary: Telegram doesn't integrate with CRMs natively, so you'll need Zapier or a custom webhook to log leads in HubSpot. If your lead volume is over 100 a week or you need multi-step nurture sequences, a dedicated chatbot platform like Intercom wins. For lean teams testing a conversational funnel, this MCP gets you live in an afternoon and costs nothing but API setup.