Sign in Book a demo
Back to Tools
Communication API Key
Build Your Agent View Telegram Docs
telegram logo

Telegram MCP Tools for AI Agents

Let an agent read recent chats, send text or voice messages, and wait for new replies or button taps.

Available Tools

7 tools available in this integration

Telegram.GetChatInfo

Get metadata about a Telegram chat, group, or channel.

Telegram.GetMessages

Get recent private-chat messages sent to the bot via Telegram's getUpdates API.

Telegram.SendMessage

Send a text message to a Telegram chat, group, or channel.

Telegram.SendTtsAudio

Convert text to speech using OpenAI TTS and send it as an audio message on Telegram.

Telegram.WaitForButtonPress

Resume waiting for an inline-button tap on a message that was already sent with buttons.

Telegram.WaitForNewMessage

Wait for the next new message in a Telegram private chat, returning as soon as one arrives.

Telegram.WhoAmI

Get information about the Telegram bot.

Why agent-optimized tools matter

Built for intent, not API schemas

Ask the agent to "read the latest message from the support bot and draft a reply." Arcade helps it use the right Telegram actions without guessing chat IDs, update details, or raw Bot API requests.

Up to 100x fewer tokens

Telegram reads return focused chat metadata or recent private-chat messages when requested. The agent can process the relevant update without loading a full conversation history or unrelated chats into the model.

Complete the workflow end to end

Inspect the chat, read the incoming message, compose a reply, request approval, and send text or audio through one toolkit designed around the complete Telegram messaging task.

Make actions predictable and controlled

Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.

Securing Telegram

The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.

This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.

Learn about Contextual Access Policies

For Telegram, you can implement some of these policies:

Access when tools are listed for a user
  • Hide Telegram.SendMessage from agents outside the roles your IDP marks as approved communicators, so an agent cannot contact users or groups without the right access.
  • Restrict Telegram.SendTtsAudio to agents operating under your approved outbound-communications role, so unapproved automation cannot send synthesized audio to a chat.
  • Deny Telegram.WaitForButtonPress to agents that do not run your approved interactive workflows, so an agent cannot act on a user's button choice outside that workflow.
Pre-execution before each tool call
  • Require human approval before Telegram.SendMessage runs, so an agent cannot publish an unreviewed message to a user, group, or channel.
  • Hold Telegram.SendTtsAudio for human approval, so an agent cannot send an unreviewed spoken announcement to a chat.
  • Block Telegram.GetMessages for chats outside your approved private-chat allowlist, so an agent cannot retrieve messages from an unapproved conversation.
Post-execution after the tool returns
  • Redact message bodies and sender contact details from Telegram.GetMessages before they reach the model, so private conversation content is not exposed during message retrieval.
  • Strip message text and sender identifiers from Telegram.WaitForNewMessage results, so an agent can detect an incoming event without receiving the private message content.
  • Deny Telegram.GetChatInfo results for private chats, so the model cannot use private-chat metadata such as titles, usernames, or member details.

How to use Telegram with your agent

Connect Telegram to an MCP client through Arcade, then give your agent access to messages, outbound replies, and interactive button flows. Follow the walkthrough from setup to your first agent request.

Your questions, answered

A Telegram MCP server exposes Telegram bot capabilities as structured tools that an AI agent can call through the Model Context Protocol. With a configured bot credential, the agent can inspect chats, read incoming private messages, wait for new messages or button presses, and send text or audio.

Telegram provides a Bot API rather than a first-party MCP server. Arcade adds the MCP and tools runtime around Telegram, including credential brokering, approval workflows, redaction, and access controls that work across supported clients.

Arcade agents can get chat and bot details, read recent private-chat messages sent to the bot, wait for new messages or inline-button presses, send text messages, and convert text to speech before sending it as Telegram audio. They cannot perform general Telegram account actions outside the bot capabilities exposed here.

Arcade uses one configured Telegram bot credential, such as the bot API key or secret, rather than Telegram OAuth scopes. That credential can reach the chats and bot operations allowed by Telegram; group or channel actions may also require the bot to have the necessary membership or administrator rights.

No. This integration uses one shared credential configured once, so calls run as the same Telegram bot rather than under a separate Telegram account for each user. The credential is brokered to the integration and is not handed to the model.

Yes. Contextual Access policies can require human approval before consequential Telegram actions such as sending a text message or audio message. The call waits until the policy's conditions, including approval, are satisfied.

Arcade proxies Telegram API calls and does not persist your message content as part of normal tool execution. The configured credential is brokered and stored encrypted at rest, and the model never receives it.

Any framework or client that can connect to Arcade's MCP gateway or tool APIs works, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.

Arcade can continue refreshing access while the configured Telegram credential remains valid. If the key or secret is revoked, rotated, or can no longer be used, calls stop until the credential is updated or reconnected.

Telegram's Bot API rate limits and chat-specific restrictions still apply to calls made through Arcade, including limits on message delivery and polling. Exact limits depend on Telegram and the chat, so high-volume bots should handle throttling and retry responses.

Ready to actually ship your agent?

Connect your agent to Telegram with a shared API key, agent-optimized tools and approval controls for consequential actions.

Build Your Agent Read the Telegram Quickstart