Envía un mensaje real por Telegram. input='<chat_id>||<mensaje>'. [x402: 0.01 USDC on Base, pay-per-use]
ConnectorNo auth
726,195 tools. Updated 2026-10-30 20:27
"telegram" matching MCP tools:
- Approve Telegram pairing via OpenClaw shell script.ConnectorNo auth
- Add Telegram channel to OpenClaw using bot token.ConnectorNo 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.mdConnectorDestructiveNo 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.mdConnectorDestructiveNo auth
- Only for the Awning team. Create a link to bind your Telegram to your signed-in operator account. Open it yourself and confirm in the bot. A server administrator must also allow your numeric ID in OPERATOR_TELEGRAM_IDS before moderation is enabled. Use it once, to set up Telegram for the operator; it takes no input.ConnectorNo auth
Matching MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables ChatGPT to read a personal Telegram account's folders and conversations, prepare drafts, and carry out delegated actions by writing and running JavaScript/TypeScript against the full mtcute SDK through a single MCP tool. Supports one account and one owner per installation, with code-and-2FA login and encrypted session storage.1MIT
- FlicenseAqualityCmaintenanceEnables 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-
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.
- Turn Telegram notifications for a feed on (on: true) or off (on: false). On: the bot sends the user every new matching job, filtered by the feed's ai_filter; needs a free slot (up to 5 feeds with alerts) or fails with feed_limit_reached. Off: the feed stays for you only (up to 5 such feeds). Ask the user first, then pass user_confirmed: true. The user is notified in Telegram.ConnectorOAuth
- Replace the Telegram alert filters. Send the COMPLETE `sellerFilter` and/or `buyerFilter` objects (read the current ones with `tronsave_get_telegram_notify_setting`, edit, send back); each range or value has `isEnabled` plus its numbers. Only changes which alerts are sent; no funds move. Idempotent. Requires a wallet signature identity and a linked Telegram account.ConnectorNo auth
- Replace the Telegram alert filters. Send the COMPLETE `sellerFilter` and/or `buyerFilter` objects (read the current ones with `tronsave_get_telegram_notify_setting`, edit, send back); each range or value has `isEnabled` plus its numbers. Only changes which alerts are sent; no funds move. Idempotent. Requires a wallet signature identity and a linked Telegram account.ConnectorNo auth
- Replace the Telegram alert filters. Send the COMPLETE `sellerFilter` and/or `buyerFilter` objects (read the current ones with `tronsave_get_telegram_notify_setting`, edit, send back); each range or value has `isEnabled` plus its numbers. Only changes which alerts are sent; no funds move. Idempotent. Requires a wallet signature identity and a linked Telegram account.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. schedule_date (ISO 8601, must be in the future) queues the message instead of delivering it now, so the result carries status='scheduled' plus scheduled and schedule_date. save_as_draft=true saves the text as the chat's draft instead of sending it (empty message clears the draft; user sessions only, bots cannot; text-only, so no files, no parse_mode='rich', no schedule_date). 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.mdConnectorDestructiveNo 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. schedule_date (ISO 8601, must be in the future) queues the message instead of delivering it now, so the result carries status='scheduled' plus scheduled and schedule_date. save_as_draft=true saves the text as the chat's draft instead of sending it (empty message clears the draft; user sessions only, bots cannot; text-only, so no files, no parse_mode='rich', no schedule_date). 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.mdConnectorDestructiveNo auth
- For channel comments use the discussion group chat_id and reply_to_message_id returned with the post. Never use this tool to publish channel posts; use telegram_create_post. Send a message to a real person from the user's own Telegram account. This is irreversible and visible to the recipient immediately. Confirm the exact wording and the recipient with the user before calling. Only chats already in the archive can be messaged; resolve the person with telegram_find_chat first. Telegram accepts a business reply only within 24 hours of that person's last message — outside that window this fails, and nothing but their next message reopens it.ConnectorDestructiveOAuth
- Deletes ONE message you sent in a Telegram private chat or basic group, for everyone, only after the receiver acknowledged it: the receiver must have replied to that exact message with the text ACK (a human in the Telegram app, or an agent with telegram_send_message reply_to_message_id). DESTRUCTIVE, with a preview: confirm=false (the default) checks the ACK and deletes NOTHING; show the preview to the user and call again with confirm=true and the same account only after they approve. The confirm checks everything again. Reading the chat, unread=0 or any text never count as an ACK. The ACK proves that another Telegram account replied, not that it is another person; an account linked in this LMCP is never accepted as the receiver, so each computer with agents needs its own Telegram account. In a basic group the ACK proves that the user you named as receiver replied, not that the message was meant for them: the receiver is whoever you name. Supergroups and channels are not supported. state deleted means the message no longer exists in this account (requested for everyone); unknown means it may have been deleted, so call again and the answer will be deleted or not_found.ConnectorDestructiveOAuth
- Get a public Telegram group's profile and return its title, description, member count and, when shown, how many members are online. Use this to size or identify a public group by username (or t.me link); only the profile is available, not the group's messages. A channel name returns an error pointing to telegram_channel, and bots, user accounts and invite links are rejected. Results must not be used to train AI or machine-learning systems.ConnectorNo auth
- Get a public Telegram group's profile and return its title, description, member count and, when shown, how many members are online. Use this to size or identify a public group by username (or t.me link); only the profile is available, not the group's messages. A channel name returns an error pointing to telegram_channel, and bots, user accounts and invite links are rejected. Results must not be used to train AI or machine-learning systems.ConnectorNo 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
- 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
- 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.ConnectorDestructiveOAuth