# How to integrate Telegram MCP with Atomic Agent ```json { "title": "How to integrate Telegram MCP with Atomic Agent", "toolkit": "Telegram", "toolkit_slug": "telegram", "framework": "Atomic Agent", "framework_slug": "atomic-agent", "url": "https://composio.dev/toolkits/telegram/framework/atomic-agent", "markdown_url": "https://composio.dev/toolkits/telegram/framework/atomic-agent.md", "updated_at": "2026-08-28T15:34:56.492Z" } ``` ## Introduction Atomic Agent is an open-source AI agent that runs on your machine and supports local models through llama.cpp. Connect it to 1,500+ apps through Composio, including Telegram. This guide uses Atomic Agent's built-in Composio integration. You need Atomic Agent v0.5.6 or later, your own Composio API key, and a Telegram account. See the [Atomic Agent documentation](https://atomicagent.io/docs/?cta_placement=atomic-agent-docs) for installation instructions. ## Also integrate Telegram with - [ChatGPT](https://composio.dev/toolkits/telegram/framework/chatgpt) - [Antigravity](https://composio.dev/toolkits/telegram/framework/antigravity) - [OpenAI Agents SDK](https://composio.dev/toolkits/telegram/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/telegram/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/telegram/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/telegram/framework/claude-cowork) - [Grok Bot](https://composio.dev/toolkits/telegram/framework/grok-bot) - [Codex](https://composio.dev/toolkits/telegram/framework/codex) - [Kimi Code](https://composio.dev/toolkits/telegram/framework/kimi) - [Grok Build](https://composio.dev/toolkits/telegram/framework/grok-build) - [Cursor](https://composio.dev/toolkits/telegram/framework/cursor) - [VS Code](https://composio.dev/toolkits/telegram/framework/vscode) - [OpenCode](https://composio.dev/toolkits/telegram/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/telegram/framework/openclaw) - [Hermes](https://composio.dev/toolkits/telegram/framework/hermes-agent) - [Pi](https://composio.dev/toolkits/telegram/framework/pi-agent) - [DeepSeek Harness](https://composio.dev/toolkits/telegram/framework/deepseek) - [CLI](https://composio.dev/toolkits/telegram/framework/cli) - [Google ADK](https://composio.dev/toolkits/telegram/framework/google-adk) - [LangChain](https://composio.dev/toolkits/telegram/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/telegram/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/telegram/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/telegram/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/telegram/framework/crew-ai) - [Pydantic AI](https://composio.dev/toolkits/telegram/framework/pydantic-ai) - [AutoGen](https://composio.dev/toolkits/telegram/framework/autogen) ## TL;DR ### How Atomic Agent connects to Telegram Atomic Agent connects to Composio's Tool Router over Streamable HTTP MCP. It discovers the tools needed for your request, and Composio handles account authentication. Execution and account-connection tools follow Atomic Agent's configured approval policy. Review any approval prompt before allowing an action on your connected account. ## Connect Telegram to Atomic Agent ### Connect Telegram to Atomic Agent - Sign up or sign in to the [Composio dashboard](https://dashboard.composio.dev/?cta_placement=atomic-agent-api-key). Copy your API key. - In Atomic Agent, open the Integrations tab and select Composio. Select API key, press e, paste the key, and press Enter. The tools become available immediately, without a restart. - Ask Atomic Agent to do something in Telegram. It searches Composio for the right tool. - On first use, open the sign-in link returned in the chat. Connect your Telegram account, then return to Atomic Agent to continue. ### Headless setup Add the following line to ~/.atomic-agent/.env, replacing YOUR_COMPOSIO_API_KEY with your key. Start Atomic Agent after saving the file. ```bash COMPOSIO_API_KEY=YOUR_COMPOSIO_API_KEY ``` ## What is the Telegram MCP server, and what's possible with it? The Telegram MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Telegram account. It provides structured and secure access to your chats and bot functionality, so your agent can send messages, manage conversations, retrieve chat data, and interact with users or groups on your behalf. - Automated message sending and editing: Let your agent send new messages or edit existing ones in any chat where your bot is present, making real-time communication a breeze. - Chat and group management: Effortlessly manage group chats by retrieving chat details, getting administrators, exporting invite links, or counting group members. - Advanced chat history and message handling: Ask your agent to fetch chat history, forward messages between chats, or delete messages for streamlined moderation and record-keeping. - Bot and user interaction: Enable the agent to answer callback queries from inline keyboards and fetch basic bot information for smarter, context-aware responses. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `TELEGRAM_ANSWER_CALLBACK_QUERY` | Answer Callback Query | Use this method to send answers to callback queries sent from inline keyboards. The answer will be displayed to the user as a notification at the top of the chat screen or as an alert. | | `TELEGRAM_EXPORT_CHAT_INVITE_LINK` | Export Chat Invite Link | Generate a new primary invite link for a chat; any previously generated primary link is revoked. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. | | `TELEGRAM_DELETE_MESSAGE` | Delete Message | Delete a message, including service messages. Limitations: cannot delete messages older than 48 hours in groups, forwarded messages, or content in protected chats (returns 400 'message can’t be deleted'). Bot must have delete/manage rights in the target chat; works reliably only on bot-authored messages in groups. Verify permissions via TELEGRAM_GET_CHAT or TELEGRAM_GET_CHAT_ADMINISTRATORS before calling. On flood control, Telegram returns HTTP 429 with a retry_after field; honor that backoff value. | | `TELEGRAM_EDIT_MESSAGE` | Edit Message | Edit text messages sent by the bot. Only bot-authored messages can be edited; editing messages from other users will fail. In groups, the bot must have edit permissions. | | `TELEGRAM_FORWARD_MESSAGE` | Forward Message | Forward messages of any kind. Service messages can't be forwarded. | | `TELEGRAM_GET_CHAT` | Get Chat Info | Get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.). The bot must be a member of or have access to the target chat; calls fail if the bot was never added, was removed, or is blocked. | | `TELEGRAM_GET_CHAT_ADMINISTRATORS` | Get Chat Administrators | Get a list of administrators in a chat. On success, returns an Array of ChatMember objects containing information about all chat administrators except other bots. Only meaningful for supergroups and channels; private chats yield no useful data. The bot must be a member of the chat; if the bot has admin rights, its own entry will appear in the result, useful for verifying its permissions before moderation actions. | | `TELEGRAM_GET_CHAT_HISTORY` | Get Chat History | Get chat history messages via the getUpdates polling method, filtered by chat_id. Returns only updates from the specified chat. Bot can only retrieve messages sent after it joined the chat; missing older messages is expected. Requires no active webhook — a webhook causes HTTP 409 conflict; delete it before using this tool. Empty result arrays (ok=true) indicate no accessible messages, not a failure. Returned message dates are Unix timestamps in UTC seconds. | | `TELEGRAM_GET_CHAT_MEMBER` | Get Chat Member | Get a chat member's status/role (including the bot itself) to preflight permissions and troubleshoot 403/empty-history issues. Use before sending messages to verify bot membership and permissions. | | `TELEGRAM_GET_CHAT_MEMBERS_COUNT` | Get Chat Members Count | Get the number of members in a chat. The bot must be an administrator in the chat for this to work. Insufficient admin permissions surface as authorization errors, not as a zero or empty count. | | `TELEGRAM_GET_ME` | Get Bot Info | Get basic information about the bot using the Bot API getMe method. Returns fields like id, username, first_name, and capabilities. If the response returns ok=false, the bot token is invalid or revoked and must be replaced before any other API calls. Bot name, bio, and profile description are read-only via the Bot API; modify them via BotFather. | | `TELEGRAM_GET_UPDATES` | Get Updates | Use this method to receive incoming updates using long polling. An Array of Update objects is returned. IMPORTANT: This method will not work if an outgoing webhook is set up. Webhooks and getUpdates are mutually exclusive — call deleteWebhook first to switch modes (409 Conflict otherwise). Notes: - Only one method (webhook or polling) can be active at a time - Updates available for up to 24 hours if unclaimed - Recalculate offset after each response to avoid duplicates - Empty result array (ok=true) is valid, meaning no new updates - On HTTP 429, honor the retry_after value; keep polling to ~1 request/second - Only chats with updates since the bot joined or last offset appear in results - Update objects vary by type; always check update.message and update.message.text exist before accessing | | `TELEGRAM_SEND_DOCUMENT` | Send Document | Send general files (documents) to a Telegram chat using the Bot API. Prefer over TELEGRAM_SEND_PHOTO when original file format or image resolution must be preserved. Rapid sends trigger flood control (HTTP 429 with `retry_after` seconds); limit to ~1 message/second per chat and wait the specified `retry_after` duration before retrying. | | `TELEGRAM_SEND_LOCATION` | Send Location | Send point on the map location to a Telegram chat using the Bot API. | | `TELEGRAM_SEND_MESSAGE` | Send Message | Send a text message to a Telegram chat using the Bot API. Bots must be members of target groups/channels with post rights. Rate limit: ~1 msg/sec per chat, ~30 msg/sec globally; exceeding returns 429 with retry_after seconds that must be honored. | | `TELEGRAM_SEND_PHOTO` | Send Photo | Send photos to a Telegram chat using the Bot API. Telegram compresses and re-encodes images; use TELEGRAM_SEND_DOCUMENT to preserve original resolution/format. Each call produces a separate post; no media-group/album support. Returns HTTP 429 with `retry_after` seconds when sending too rapidly. | | `TELEGRAM_SEND_POLL` | Send Poll | Send a native poll to a Telegram chat using the Bot API. | | `TELEGRAM_SET_MY_COMMANDS` | Set Bot Commands | Use this method to change the list of the bot's commands. See https://core.telegram.org/bots#commands for more details about bot commands. | ## Supported Triggers None listed. ## Troubleshooting ### Why is my API key rejected? Copy the key directly from the Composio dashboard. Atomic Agent requires ASCII characters because it sends the key in an HTTP header. Remove any extra characters introduced when copying. ### Why are Composio tools unavailable after saving a key? Check that you use Atomic Agent v0.5.6 or later and that Composio is enabled in your configuration. A "composio": { "enabled": false } setting disables the integration while keeping the saved key on disk. ### Does Composio have a free plan? The Hobby plan includes 100,000 tool calls per month. Composio-managed OAuth apps have a lower included allowance. See [Composio pricing](/pricing) for the current limits that apply to your connection. ## Complete Code None listed. ## Conclusion ### Use Telegram from Atomic Agent With your account connected, ask Atomic Agent to work with Telegram in natural language. You can connect more apps through the same Composio integration as you need them. Visit the [Atomic Agent website](https://atomicagent.io/?cta_placement=atomic-agent-site) or inspect the [Atomic Agent source code](https://github.com/AtomicBot-ai/atomic-agent?cta_placement=atomic-agent-repo). ## How to build Telegram MCP Agent with another framework - [ChatGPT](https://composio.dev/toolkits/telegram/framework/chatgpt) - [Antigravity](https://composio.dev/toolkits/telegram/framework/antigravity) - [OpenAI Agents SDK](https://composio.dev/toolkits/telegram/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/telegram/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/telegram/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/telegram/framework/claude-cowork) - [Grok Bot](https://composio.dev/toolkits/telegram/framework/grok-bot) - [Codex](https://composio.dev/toolkits/telegram/framework/codex) - [Kimi Code](https://composio.dev/toolkits/telegram/framework/kimi) - [Grok Build](https://composio.dev/toolkits/telegram/framework/grok-build) - [Cursor](https://composio.dev/toolkits/telegram/framework/cursor) - [VS Code](https://composio.dev/toolkits/telegram/framework/vscode) - [OpenCode](https://composio.dev/toolkits/telegram/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/telegram/framework/openclaw) - [Hermes](https://composio.dev/toolkits/telegram/framework/hermes-agent) - [Pi](https://composio.dev/toolkits/telegram/framework/pi-agent) - [DeepSeek Harness](https://composio.dev/toolkits/telegram/framework/deepseek) - [CLI](https://composio.dev/toolkits/telegram/framework/cli) - [Google ADK](https://composio.dev/toolkits/telegram/framework/google-adk) - [LangChain](https://composio.dev/toolkits/telegram/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/telegram/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/telegram/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/telegram/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/telegram/framework/crew-ai) - [Pydantic AI](https://composio.dev/toolkits/telegram/framework/pydantic-ai) - [AutoGen](https://composio.dev/toolkits/telegram/framework/autogen) ## Related Toolkits - [Gmail](https://composio.dev/toolkits/gmail) - Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable. - [Outlook](https://composio.dev/toolkits/outlook) - Outlook is Microsoft's email and calendaring platform for unified communications and scheduling. It helps users stay organized with powerful email, contacts, and calendar management. - [Slack](https://composio.dev/toolkits/slack) - Slack is a channel-based messaging platform for teams and organizations. It helps people collaborate in real time, share files, and connect all their tools in one place. - [Gong](https://composio.dev/toolkits/gong) - Gong is a platform for video meetings, call recording, and team collaboration. It helps teams capture conversations, analyze calls, and turn insights into action. - [Microsoft teams](https://composio.dev/toolkits/microsoft_teams) - Microsoft Teams is a collaboration platform that combines chat, meetings, and file sharing within Microsoft 365. It keeps distributed teams connected and productive through seamless virtual communication. - [Slackbot](https://composio.dev/toolkits/slackbot) - Slackbot is a conversational automation tool for Slack that handles reminders, notifications, and automated responses. It boosts team productivity by streamlining onboarding, answering FAQs, and managing timely alerts—all right inside Slack. - [2chat](https://composio.dev/toolkits/_2chat) - 2chat is an API platform for WhatsApp and multichannel text messaging. It streamlines chat automation, group management, and real-time messaging for developers. - [Agent mail](https://composio.dev/toolkits/agent_mail) - Agent mail provides AI agents with dedicated email inboxes for sending, receiving, and managing emails. It empowers agents to communicate autonomously with people, services, and other agents—no human intervention needed. - [Android Texter](https://composio.dev/toolkits/android_texter) - Android Texter is an API service that connects Android phones to SMS, MMS, contacts, and device data. Use it to automate mobile messaging without building your own phone-to-API bridge. - [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place. - [Blooio](https://composio.dev/toolkits/blooio) - Blooio is a stable v2 API platform for messaging, chats, contacts, groups, phone numbers, and account analytics. It gives teams a clean way to build reliable communication workflows without stitching together fragile custom APIs. - [CallOnTheGo](https://composio.dev/toolkits/callonthego) - CallOnTheGo is a telephony API for managing phone numbers, caller IDs, suppression lists, audio assets, contact lists, and Voice AI campaigns. It provides programmatic control over calling infrastructure and campaign automation for scalable voice outreach. - [Carbon Voice MCP](https://composio.dev/toolkits/carbon_voice_mcp) - Carbon Voice MCP is a voice-first collaboration platform for messages, conversations, and workflows. Use it to centralize voice communications and streamline team collaboration. - [CardClan](https://composio.dev/toolkits/cardclan) - CardClan is a digital card platform for creating and sending personalized team cards. Use it to celebrate moments, share card links, and manage card workflows without extra coordination. - [Chatwork](https://composio.dev/toolkits/chatwork) - Chatwork is a team communication platform with group chats, file sharing, and task management. It helps businesses boost collaboration and streamline productivity. - [Clickmeeting](https://composio.dev/toolkits/clickmeeting) - ClickMeeting is a cloud-based platform for running online meetings and webinars. It helps businesses and individuals host, manage, and engage virtual audiences with ease. - [Confluence](https://composio.dev/toolkits/confluence) - Confluence is Atlassian's team collaboration and knowledge management platform. It helps your team organize, share, and update documents and project content in one secure workspace. - [Daily](https://composio.dev/toolkits/daily) - Daily is a WebRTC video and audio API platform for building rooms, meetings, recordings, live streams, transcriptions, and telephony. It gives developers reliable real-time media infrastructure without managing complex conferencing stacks. - [Dailybot](https://composio.dev/toolkits/dailybot) - DailyBot streamlines team collaboration with chat-based standups, reminders, and polls. It keeps work flowing smoothly in your favorite messaging platforms. - [Dialmycalls](https://composio.dev/toolkits/dialmycalls) - Dialmycalls is a mass notification service for sending voice and text messages to contacts. It helps teams and organizations quickly broadcast urgent alerts and updates. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Telegram MCP? With a standalone Telegram MCP server, the agents and LLMs can only access a fixed set of Telegram tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Telegram and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Atomic Agent? Yes, you can. Atomic Agent fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Telegram tools. ### Can I manage the permissions and scopes for Telegram while using Tool Router? Yes, absolutely. You can configure which Telegram scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do. ### How safe is my data with Composio Tool Router? All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Telegram data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)