Telegram MCP Server
MCP ServerFreeSend messages and manage Telegram chats and bots via MCP.
Capabilities12 decomposed
message-sending-via-telegram-bot-api
Medium confidenceSends text messages to Telegram chats and channels by wrapping the Telegram Bot API's sendMessage endpoint. The MCP server translates tool calls into HTTP requests to Telegram's API, handling authentication via bot token and managing chat/channel ID resolution. Supports formatting options like markdown and HTML parsing modes for rich text delivery.
Exposes Telegram Bot API as MCP tools, allowing Claude and other LLMs to send messages without custom integration code. Uses MCP's schema-based tool definition to map Telegram API parameters directly to LLM-callable functions.
Simpler than building custom Telegram bot handlers because MCP abstracts authentication and API routing; more flexible than hardcoded bot logic because LLMs can dynamically decide when and what to send.
message-retrieval-and-chat-history
Medium confidenceRetrieves messages from Telegram chats and channels by calling the Telegram Bot API's getUpdates or message history endpoints. The MCP server fetches recent messages with metadata (sender, timestamp, message_id) and returns them as structured data. Supports filtering by chat_id and limiting result count for efficient context loading.
Bridges Telegram message history into LLM context by exposing getUpdates as an MCP tool, enabling stateful conversation memory without custom polling loops. Structures raw Telegram API responses into LLM-friendly formats.
More direct than webhook-based approaches because it uses polling (simpler deployment, no public endpoint needed); more flexible than hardcoded chat handlers because LLMs can decide when to fetch history and how much context to load.
webhook-based-update-handling-integration
Medium confidenceIntegrates with Telegram's webhook system to receive real-time updates (messages, callbacks, edits) via HTTP POST requests. The MCP server can be configured to work with webhook-based bots (alternative to polling), receiving updates from Telegram's servers and routing them to connected LLM clients. Supports update filtering and acknowledgment.
Bridges Telegram's webhook system into MCP, enabling event-driven bot architectures. Handles webhook registration and update routing without requiring polling loops.
Lower latency than polling because updates arrive immediately; more scalable than getUpdates polling because it eliminates constant API calls and reduces rate-limit pressure.
error-handling-and-api-response-mapping
Medium confidenceTranslates Telegram Bot API errors and responses into structured MCP-compatible formats. The MCP server catches API failures (rate limits, invalid parameters, permission errors) and maps them to descriptive error objects that LLMs can reason about. Implements retry logic for transient failures and provides actionable error messages.
Implements error mapping layer that translates raw Telegram API errors into LLM-friendly error objects. Provides structured error information that LLMs can use for decision-making and recovery.
More actionable than raw API errors because it provides context and recovery suggestions; more reliable than ignoring errors because it enables LLM agents to handle failures intelligently.
chat-and-channel-metadata-access
Medium confidenceRetrieves metadata about Telegram chats and channels (title, description, member count, permissions) via the Telegram Bot API's getChat endpoint. The MCP server translates requests into API calls and returns structured chat information. Enables LLM agents to understand chat context and permissions before taking actions.
Exposes Telegram's getChat endpoint as an MCP tool, allowing LLMs to query chat context and permissions dynamically. Structures API responses for LLM reasoning about chat state.
Simpler than hardcoding chat rules because LLMs can query metadata at runtime; more reliable than inferring permissions from failed API calls because it proactively checks permissions before attempting actions.
bot-command-handler-registration
Medium confidenceRegisters and manages bot commands that Telegram users can invoke via the / prefix. The MCP server maps command definitions (name, description, scope) to Telegram's setMyCommands API, making commands discoverable in the Telegram client's command menu. Supports per-chat and per-user command scoping.
Exposes Telegram's setMyCommands as an MCP tool, enabling dynamic command registration from LLM agents. Allows bots to advertise capabilities without hardcoding command lists.
More flexible than static command definitions because commands can be registered dynamically based on bot state; more discoverable than relying on help text because commands appear in Telegram's native command menu.
inline-keyboard-and-callback-button-handling
Medium confidenceConstructs and sends inline keyboards (button grids) with Telegram messages, enabling interactive user responses via callback queries. The MCP server builds keyboard JSON structures compatible with Telegram's InlineKeyboardMarkup format and handles callback data routing. Supports button linking, URL buttons, and callback-based interactions.
Exposes Telegram's InlineKeyboardMarkup as MCP tools, allowing LLMs to construct interactive interfaces without manual JSON building. Integrates callback handling into the MCP tool chain for event-driven bot logic.
More user-friendly than text-based commands because buttons reduce typing; more flexible than hardcoded button layouts because LLMs can dynamically generate buttons based on context.
file-and-media-upload-handling
Medium confidenceUploads files, images, audio, and video to Telegram chats via the Telegram Bot API's sendDocument, sendPhoto, sendAudio, and sendVideo endpoints. The MCP server accepts file paths or binary data, handles multipart form encoding, and manages file metadata. Supports captions and file type validation.
Wraps Telegram's file upload endpoints as MCP tools, enabling LLM agents to send generated artifacts without managing multipart encoding. Handles file type detection and metadata attachment.
Simpler than direct API calls because MCP abstracts multipart form handling; more reliable than URL-based sharing because it supports local file uploads and binary data directly.
user-and-member-information-retrieval
Medium confidenceFetches user profile information (name, username, profile photo) and chat member details via Telegram Bot API's getUser and getChatMember endpoints. The MCP server translates requests into API calls and returns structured user metadata. Enables LLM agents to personalize responses based on user context.
Exposes Telegram's getUser and getChatMember endpoints as MCP tools, allowing LLMs to query user context dynamically. Structures responses for LLM reasoning about user identity and permissions.
More flexible than hardcoded user checks because LLMs can query user info at runtime; more reliable than inferring user status from message metadata because it queries authoritative API endpoints.
message-editing-and-deletion
Medium confidenceEdits or deletes previously sent messages in Telegram chats via the Telegram Bot API's editMessageText and deleteMessage endpoints. The MCP server translates edit/delete requests into API calls using message_id and chat_id. Supports editing text, inline keyboards, and media captions with version tracking.
Exposes Telegram's editMessageText and deleteMessage as MCP tools, enabling LLM agents to manage message lifecycle without hardcoding update logic. Supports dynamic message updates based on agent reasoning.
More flexible than sending new messages because it preserves message history and reduces chat clutter; more reliable than relying on user edits because the bot maintains authoritative message state.
mcp-tool-schema-definition-and-routing
Medium confidenceDefines MCP tool schemas that map Telegram Bot API operations to LLM-callable functions. The MCP server implements the Model Context Protocol's tool definition format, specifying input parameters, descriptions, and return types for each Telegram operation. Routes LLM tool calls to appropriate Telegram API endpoints with parameter validation.
Implements MCP's tool definition protocol to expose Telegram operations as first-class LLM tools. Uses JSON schema to describe parameters and return types, enabling LLMs to reason about Telegram capabilities.
More discoverable than custom integrations because LLMs see tool schemas directly; more reliable than hardcoded tool lists because schemas are validated by MCP clients before execution.
mcp-resource-exposure-for-chat-context
Medium confidenceExposes Telegram chats and messages as MCP resources, allowing LLM clients to read chat content as structured data. The MCP server implements the Model Context Protocol's resource interface, providing URIs for chats (e.g., telegram://chat/123) and returning message history or metadata on request. Enables LLMs to access Telegram context without explicit tool calls.
Implements MCP's resource protocol to expose Telegram chats as readable data sources. Allows LLMs to access Telegram context passively without explicit tool invocation, integrating Telegram into the LLM's native context model.
More seamless than tool-based access because resources integrate into LLM context automatically; more efficient than polling because resources are fetched on-demand by the LLM client.
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with Telegram MCP Server, ranked by overlap. Discovered automatically through the match graph.
Serverless Telegram bot
[WhatsApp bot](https://github.com/danielgross/whatsapp-gpt)
GPTBots
Unleash AI chatbots with intuitive NLP and seamless integration for enhanced customer...
RevoChat
Help businesses effortlessly create and integrate custom chatbots into their websites, enhancing customer service and...
awesome-n8n-templates
280+ free n8n automation templates — ready-to-use workflows for Gmail, Telegram, Slack, Discord, WhatsApp, Google Drive, Notion, OpenAI, and more. AI agents, RAG chatbots, email automation, social media, DevOps, and document processing. The largest open-source n8n template collection.
botpress
The open-source hub to build & deploy GPT/LLM Agents ⚡️
agent-second-brain
Send voice notes to Telegram → get organized knowledge base, tasks in Todoist, and daily reports. Persistent memory with Ebbinghaus decay, vault health scoring, knowledge graph. Runs on Claude Code + OpenClaw. 5/mo.
Best For
- ✓AI agents and LLM applications needing real-time user notifications
- ✓Teams building Telegram-integrated chatbots with Claude or other LLMs
- ✓Developers automating alert delivery to Telegram without managing bot infrastructure
- ✓LLM agents that need to understand Telegram conversation context before responding
- ✓Developers building Telegram-based customer support bots with memory
- ✓Teams analyzing Telegram channel messages for sentiment or content extraction
- ✓Teams deploying Telegram bots in production with low-latency requirements
- ✓Developers building event-driven LLM agents triggered by Telegram messages
Known Limitations
- ⚠Message size capped at Telegram's 4096 character limit per message
- ⚠No built-in message queuing or retry logic — failed sends require external handling
- ⚠Requires valid Telegram Bot API token with appropriate permissions
- ⚠No support for scheduled message delivery — sends are immediate only
- ⚠getUpdates only returns new updates since last poll — no arbitrary historical retrieval without offset tracking
- ⚠Message history access depends on Telegram Bot API permissions and chat privacy settings
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
About
Community MCP server for Telegram messaging platform. Enables sending and reading messages, managing chats and channels, handling bot commands, and accessing Telegram Bot API functionality.
Categories
Alternatives to Telegram MCP Server
Are you the builder of Telegram MCP Server?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →