Skip to main content
Glama
649,985 tools. Updated 2026-10-09 14:47

"Telegram" matching MCP tools:

  • Envía un mensaje real por Telegram. input='<chat_id>||<mensaje>'. [x402: 0.01 USDC on Base, pay-per-use]
    ConnectorNo auth
  • REAL action: book at a network venue on the user's behalf. provider_id + item (the venue interprets it). Doctor: item={date,time}. Hostel: item={check_in,check_out,guests,promo_code?} — do NOT ask for name/contact: identity comes from a one-time Telegram consent. Spa: item={date,time,procedure}. Hostel: book returns a HOLD with payment_url; the booking is finalized by PAYMENT, not by this call. CONSENT: do NOT ask for approval up front — just call book. ONLY if the call returns consent_url/telegram.consent_url (linked=false = not yet authorized at this venue) do you show that link to the user for a one-tap approval in Telegram, then retry. If consent_url_native (tg://...) is present, try to open it on the user's device (open/xdg-open/Start-Process — launches Telegram directly if installed). BUT tg:// fails SILENTLY without Telegram — so ALWAYS also show the user consent_url (https): t.me opens the app or offers to install it. Open once, then retry. If already authorized (consent given earlier) book succeeds IMMEDIATELY, with no prompts. Never ask for consent when you already have it.
    ConnectorNo auth
  • Send text and optional file attachments to a Telegram chat. Supports reply-to (including forum topics and channel discussion groups), parse_mode: classic markdown/html/auto (entities) or rich (Rich Message document; dialect auto-detected). parse_mode=rich cannot be combined with files. File attachments as http(s) URLs, local paths, or data: URIs. When files are provided, the message text becomes a caption. For channel posts with reply_to_id, automatically posts in the linked discussion group. Success: dict with message_id, date, chat, text, status='sent', and sender info (rich messages also set rich=true and rich_format). Error: dict with ok=false and error string. Use send_message to create new messages; use edit_message to modify existing ones. Use send_message_to_phone when targeting a phone number instead of a chat_id. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md
    Connector
    Destructive
    No auth
  • Low-level Telegram API (MTProto) invoke for methods not wrapped by other tools. Dangerous methods require allow_dangerous=true. Success: API result dict or normalized error. PII and credential-shaped fields (phone, access_hash) are dropped from a successful result by default; pass include_sensitive=true for the raw payload. A bare message id needs a chat binding: requests with no peer field (messages.GetMessages, messages.DeleteMessages) are refused, because a bare id resolves against an arbitrary dialog. Use channels.GetMessages or messages.GetHistory, which carry the binding. messages.GetHistory cannot address a forum topic (no thread_id/top_msg_id in the schema, and channels.GetHistory does not exist) -- use messages.Search with top_msg_id, or the high-level get_messages with reply_to_id. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md
    Connector
    Destructive
    No auth

Matching MCP Servers

  • F
    license
    A
    quality
    C
    maintenance
    Enables fetching the most recent image from a specified Telegram group and waiting for new images to be posted, using a user account over MTProto.
    2
    -
  • A
    license
    A
    quality
    C
    maintenance
    An MCP server that lets an LLM send messages, photos, and documents to Telegram through a bot. Provides four tools: get_me, send_message, send_photo, and send_document.
    4
    MIT

Matching MCP Connectors

  • Telegram: FASTEST real time Telegram API. Retrieve channel's info and messages in milliseconds..

  • Telegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack.

  • Send text and optional file attachments to a Telegram chat. Supports reply-to (including forum topics and channel discussion groups), parse_mode: classic markdown/html/auto (entities) or rich (Rich Message document; dialect auto-detected). parse_mode=rich cannot be combined with files. File attachments as http(s) URLs, local paths, or data: URIs. When files are provided, the message text becomes a caption. For channel posts with reply_to_id, automatically posts in the linked discussion group. Success: dict with message_id, date, chat, text, status='sent', and sender info (rich messages also set rich=true and rich_format). Error: dict with ok=false and error string. Use send_message to create new messages; use edit_message to modify existing ones. Use send_message_to_phone when targeting a phone number instead of a chat_id. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md
    Connector
    Destructive
    No auth
  • Low-level Telegram API (MTProto) invoke for methods not wrapped by other tools. Dangerous methods require allow_dangerous=true. Success: API result dict or normalized error. PII and credential-shaped fields (phone, access_hash) are dropped from a successful result by default; pass include_sensitive=true for the raw payload. A bare message id needs a chat binding: requests with no peer field (messages.GetMessages, messages.DeleteMessages) are refused, because a bare id resolves against an arbitrary dialog. Use channels.GetMessages or messages.GetHistory, which carry the binding. messages.GetHistory cannot address a forum topic (no thread_id/top_msg_id in the schema, and channels.GetHistory does not exist) -- use messages.Search with top_msg_id, or the high-level get_messages with reply_to_id. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md
    Connector
    Destructive
    No auth
  • Call this for network-wide numbers across all public Telegram groups tracked by Limzo (group count, messages, active users, replies, reactions, karma — 7-day and all-time) plus durable lifetime totals (messages analyzed, members tracked, spam messages removed) and the current top groups by Limzo Score. For finding a specific group, prefer list_groups.
    ConnectorNo auth
  • Agent-to-agent messaging via Telegram — the fastest real-time channel between agents. Two modes: (1) Direct DM: provide target_agent_id to deliver a private message to that agent's operator on Telegram (they must have registered their Telegram via /api/agent/set-contact). (2) Group broadcast: omit target_agent_id to post to @x711criptic, the live x711 agent community on Telegram — all operators monitoring the group see your message instantly. Requires API key. Returns: { delivered, method: 'direct'|'group', to, note }. Cost: $0.02.
    ConnectorNo auth
  • Agent-to-agent messaging via Telegram — the fastest real-time channel between agents. Two modes: (1) Direct DM: provide target_agent_id to deliver a private message to that agent's operator on Telegram (they must have registered their Telegram via /api/agent/set-contact). (2) Group broadcast: omit target_agent_id to post to @x711criptic, the live x711 agent community on Telegram — all operators monitoring the group see your message instantly. Requires API key. Returns: { delivered, method: 'direct'|'group', to, note }. Cost: $0.02.
    ConnectorNo auth
  • Replace the text of an existing message in a Telegram chat. Only works on messages sent by the authenticated account. Cannot edit media or other message attributes — text only. parse_mode: classic markdown/html/auto or rich (Rich Message; dialect auto-detected). Success: dict with message_id, date, chat, text, status='edited', and edit_date (rich messages also set rich=true and rich_format). Error: dict with ok=false and error string (e.g. message not found or not editable). Use edit_message to update a previously sent message; use send_message to create new ones. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md
    Connector
    Destructive
    No auth
  • Replace the text of an existing message in a Telegram chat. Only works on messages sent by the authenticated account. Cannot edit media or other message attributes — text only. parse_mode: classic markdown/html/auto or rich (Rich Message; dialect auto-detected). Success: dict with message_id, date, chat, text, status='edited', and edit_date (rich messages also set rich=true and rich_format). Error: dict with ok=false and error string (e.g. message not found or not editable). Use edit_message to update a previously sent message; use send_message to create new ones. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md
    Connector
    Destructive
    No auth
  • Call this for network-wide numbers across all public Telegram groups tracked by Limzo (group count, messages, active users, replies, reactions, karma — 7-day and all-time) plus durable lifetime totals (messages analyzed, members tracked, spam messages removed) and the current top groups by Limzo Score. For finding a specific group, prefer list_groups.
    ConnectorNo auth
  • List runnable Epsilon integration examples (Python cron DCA, LangChain tools, Vercel AI SDK tools, Telegram bot). Fetch full source with get_example. No API key required.
    ConnectorAPI key
  • Pagá $0.10 USDC en Base por el juicio subjetivo/cultural de una persona real (no un LLM) sobre una pregunta — especializado en contexto argentino. Sin pago adjunto devuelve los requisitos de pago x402; con el pago, crea el ticket y devuelve {ticket, resultToken, poll}. La respuesta del humano llega de forma asíncrona (minutos u horas) y vuelve a vos, el agente, por get_human_verdict: no llega por Telegram (Telegram es solo cómo la persona recibe la pregunta).
    ConnectorNo auth
  • Get a secure connection (or reconnection) link for one of the user's provider accounts: LinkedIn, WhatsApp, Instagram, Telegram, Google/Gmail, Microsoft/Outlook or generic IMAP email. Use when the user asks to connect/add/reconnect an account, or after a connect_account/reconnect_account result. Pass account_id only to re-authenticate an existing disconnected account (from list_connected_accounts). For WhatsApp and Telegram prefer whatsapp_connect / telegram_connect, which show the QR code directly in the conversation; this tool is the browser fallback. Never ask the user for provider passwords; the link opens the provider's own authentication.
    ConnectorOAuth
  • Send a photo, document, video, audio or voice message to a real person or group from the user's Telegram. Irreversible and immediately visible — confirm the recipient and what is being sent before calling. Give exactly one source: • from_chat_id + from_message_id — forward a file that is already in the archive. Costs no upload and has no size limit, because Telegram already holds the file. Works only for messages the collector saw live; imported history has no file id. • url — a public http(s) link that Telegram fetches itself. In a private chat this is sent as the user. In a group there is no business connection, so it is sent as the bot — say so if that matters.
    Connector
    Destructive
    OAuth
  • Start connecting one of the user's own social accounts to their SocialClaw workspace. For most providers this returns an authorizeUrl; give it to the user so they sign in with the provider themselves (SocialClaw never sees their password). Telegram and Discord have no sign-in page: Telegram takes the bot token and chat id of a bot the user created and made admin of their channel, and Discord takes a webhook URL the user created for their channel. Only pass values the user gave you for this purpose.
    ConnectorNo auth
  • Створити Telegram-шаблон повідомлення. Вставляй 'html_name' поля в body БЕЗ жодних дужок (напр. Full Name). Отримай html_name через get_form_fields.
    ConnectorNo auth
  • Створити Telegram-шаблон повідомлення. Вставляй 'html_name' поля в body БЕЗ жодних дужок (напр. Full Name). Отримай html_name через get_form_fields.
    ConnectorNo auth