# How to integrate Telegram MCP with CrewAI ```json { "title": "How to integrate Telegram MCP with CrewAI", "toolkit": "Telegram", "toolkit_slug": "telegram", "framework": "CrewAI", "framework_slug": "crew-ai", "url": "https://composio.dev/toolkits/telegram/framework/crew-ai", "markdown_url": "https://composio.dev/toolkits/telegram/framework/crew-ai.md", "updated_at": "2026-05-06T08:30:55.761Z" } ``` ## Introduction This guide walks you through connecting Telegram to CrewAI using the Composio tool router. By the end, you'll have a working Telegram agent that can send a welcome message to new group members, forward latest announcement to all admins, get total member count of your group through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Telegram account through Composio's Telegram MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Telegram with - [ChatGPT](https://composio.dev/toolkits/telegram/framework/chatgpt) - [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) - [Codex](https://composio.dev/toolkits/telegram/framework/codex) - [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) - [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) ## TL;DR Here's what you'll learn: - Get a Composio API key and configure your Telegram connection - Set up CrewAI with an MCP enabled agent - Create a Tool Router session or standalone MCP server for Telegram - Build a conversational loop where your agent can execute Telegram operations ## What is CrewAI? CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews. Key features include: - Agent Roles: Define specialized agents with specific goals and backstories - Task Management: Create tasks with clear descriptions and expected outputs - Crew Orchestration: Combine agents and tasks into collaborative workflows - MCP Integration: Connect to external tools through Model Context Protocol ## 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_DELETE_MESSAGE` | Delete Message | Delete a message, including service messages, with certain limitations. | | `TELEGRAM_EDIT_MESSAGE` | Edit Message | Edit text messages sent by the bot. | | `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_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.). | | `TELEGRAM_GET_CHAT_ADMINISTRATORS` | Get Chat Administrators | Get a list of administrators in a chat. on success, returns an array of chatmember objects that contains information about all chat administrators except other bots. | | `TELEGRAM_GET_CHAT_HISTORY` | Get Chat History | Get chat history messages. note: this uses the getupdates method with specific parameters to retrieve historical messages. | | `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. | | `TELEGRAM_GET_ME` | Get Bot Info | Get basic information about the bot using the bot api getme method. | | `TELEGRAM_GET_UPDATES` | Get Updates | Use this method to receive incoming updates using long polling. an array of update objects is returned. | | `TELEGRAM_SEND_DOCUMENT` | Send Document | Send general files (documents) to a telegram chat using the bot api. | | `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. | | `TELEGRAM_SEND_PHOTO` | Send Photo | Send photos to a telegram chat using the bot api. | | `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. ## Creating MCP Server - Stand-alone vs Composio SDK The Telegram MCP server is an implementation of the Model Context Protocol that connects your AI agent to Telegram. It provides structured and secure access so your agent can perform Telegram operations on your behalf through a secure, permission-based interface. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before starting, make sure you have: - Python 3.9 or higher - A Composio account and API key - A Telegram connection authorized in Composio - An OpenAI API key for the CrewAI LLM - Basic familiarity with Python ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider. - Keep the API key safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install dependencies **What's happening:** - composio connects your agent to Telegram via MCP - crewai provides Agent, Task, Crew, and LLM primitives - crewai-tools[mcp] includes MCP helpers - python-dotenv loads environment variables from .env ```bash pip install composio crewai crewai-tools[mcp] python-dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's happening: - COMPOSIO_API_KEY authenticates with Composio - USER_ID scopes the session to your account - OPENAI_API_KEY lets CrewAI use your chosen OpenAI model ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here OPENAI_API_KEY=your_openai_api_key_here ``` ### 4. Import dependencies **What's happening:** - CrewAI classes define agents and tasks, and run the workflow - MCPServerHTTP connects the agent to an MCP endpoint - Composio will give you a short lived Telegram MCP URL ```python import os from composio import Composio from crewai import Agent, Task, Crew from crewai_tools import MCPServerAdapter import dotenv dotenv.load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set") ``` ### 5. Create a Composio Tool Router session for Telegram **What's happening:** - You create a Telegram only session through Composio - Composio returns an MCP HTTP URL that exposes Telegram tools ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["telegram"]) url = session.mcp.url ``` ### 6. Initialize the MCP Server **What's Happening:** - Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication. - MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format. - Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools. - Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops. - Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries. ```python server_params = { "url": url, "transport": "streamable-http", "headers": {"x-api-key": COMPOSIO_API_KEY}, } with MCPServerAdapter(server_params) as tools: agent = Agent( role="Search Assistant", goal="Help users search the internet effectively", backstory="You are a helpful assistant with access to search tools.", tools=tools, verbose=False, max_iter=10, ) ``` ### 7. Create a CLI Chatloop and define the Crew **What's Happening:** - Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable. - Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean. - Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses. - Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context. - Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response. - Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity. ```python print("Chat started! Type 'exit' or 'quit' to end.\n") conversation_context = "" while True: user_input = input("You: ").strip() if user_input.lower() in ["exit", "quit", "bye"]: print("\nGoodbye!") break if not user_input: continue conversation_context += f"\nUser: {user_input}\n" print("\nAgent is thinking...\n") task = Task( description=( f"Conversation history:\n{conversation_context}\n\n" f"Current request: {user_input}" ), expected_output="A helpful response addressing the user's request", agent=agent, ) crew = Crew(agents=[agent], tasks=[task], verbose=False) result = crew.kickoff() response = str(result) conversation_context += f"Agent: {response}\n" print(f"Agent: {response}\n") ``` ## Complete Code ```python from crewai import Agent, Task, Crew, LLM from crewai_tools import MCPServerAdapter from composio import Composio from dotenv import load_dotenv import os load_dotenv() GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY") COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not GOOGLE_API_KEY: raise ValueError("GOOGLE_API_KEY is not set in the environment.") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set in the environment.") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set in the environment.") # Initialize Composio and create a session composio = Composio(api_key=COMPOSIO_API_KEY) session = composio.create( user_id=COMPOSIO_USER_ID, toolkits=["telegram"], ) url = session.mcp.url # Configure LLM llm = LLM( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY"), ) server_params = { "url": url, "transport": "streamable-http", "headers": {"x-api-key": COMPOSIO_API_KEY}, } with MCPServerAdapter(server_params) as tools: agent = Agent( role="Search Assistant", goal="Help users with internet searches", backstory="You are an expert assistant with access to Composio Search tools.", tools=tools, llm=llm, verbose=False, max_iter=10, ) print("Chat started! Type 'exit' or 'quit' to end.\n") conversation_context = "" while True: user_input = input("You: ").strip() if user_input.lower() in ["exit", "quit", "bye"]: print("\nGoodbye!") break if not user_input: continue conversation_context += f"\nUser: {user_input}\n" print("\nAgent is thinking...\n") task = Task( description=( f"Conversation history:\n{conversation_context}\n\n" f"Current request: {user_input}" ), expected_output="A helpful response addressing the user's request", agent=agent, ) crew = Crew(agents=[agent], tasks=[task], verbose=False) result = crew.kickoff() response = str(result) conversation_context += f"Agent: {response}\n" print(f"Agent: {response}\n") ``` ## Conclusion You now have a CrewAI agent connected to Telegram through Composio's Tool Router. The agent can perform Telegram operations through natural language commands. Next steps: - Add role-specific instructions to customize agent behavior - Plug in more toolkits for multi-app workflows - Chain tasks for complex multi-step operations ## How to build Telegram MCP Agent with another framework - [ChatGPT](https://composio.dev/toolkits/telegram/framework/chatgpt) - [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) - [Codex](https://composio.dev/toolkits/telegram/framework/codex) - [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) - [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) ## 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. - [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. - [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. - [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. - [Dialpad](https://composio.dev/toolkits/dialpad) - Dialpad is a cloud-based business phone and contact center system for teams. It unifies voice, video, messaging, and meetings across your devices. - [Discord](https://composio.dev/toolkits/discord) - Discord is a real-time messaging and VoIP platform for communities and teams. It lets users chat, share media, and collaborate across public and private channels. - [Discordbot](https://composio.dev/toolkits/discordbot) - Discordbot is an automation tool for Discord servers that handles moderation, messaging, and user engagement. It helps communities run smoothly by automating routine and complex tasks. - [Echtpost](https://composio.dev/toolkits/echtpost) - Echtpost is a secure digital communication platform for encrypted document and message exchange. It ensures confidential data stays private and protected during transmission. - [Egnyte](https://composio.dev/toolkits/egnyte) - Egnyte is a cloud-based platform for secure file sharing, storage, and governance. It helps teams collaborate efficiently while maintaining data compliance and security. - [Google Meet](https://composio.dev/toolkits/googlemeet) - Google Meet is a secure video conferencing platform for virtual meetings, chat, and screen sharing. It helps teams connect, collaborate, and communicate seamlessly from anywhere. ## 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 CrewAI? Yes, you can. CrewAI 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)