Telegram Bot MCP Server for CrewAI 13 tools — connect in under 2 minutes
Connect your CrewAI agents to Telegram Bot through the Vinkius — pass the Edge URL in the `mcps` parameter and every Telegram Bot tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
from crewai import Agent, Task, Crew
agent = Agent(
role="Telegram Bot Specialist",
goal="Help users interact with Telegram Bot effectively",
backstory=(
"You are an expert at leveraging Telegram Bot tools "
"for automation and data analysis."
),
# Your Vinkius token — get it at cloud.vinkius.com
mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)
task = Task(
description=(
"Explore all available tools in Telegram Bot "
"and summarize their capabilities."
),
agent=agent,
expected_output=(
"A detailed summary of 13 available tools "
"and what they can do."
),
)
crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About Telegram Bot MCP Server
Connect any Telegram Bot to your AI agent and automate messaging, broadcasting, and chat management through natural language commands.
When paired with CrewAI, Telegram Bot becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Telegram Bot tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.
What you can do
- Bot Information — Retrieve your bot's profile details, username, and configuration
- Message Handling — Send text messages with Markdown or HTML formatting to any chat or channel
- Media Delivery — Send photos, documents, videos, and audio files via URL or file_id
- Chat Management — Get detailed info about groups, channels, and private chats including member counts and admin lists
- Message Operations — Forward and delete messages programmatically in any chat
The Telegram Bot MCP Server exposes 13 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect Telegram Bot to CrewAI via MCP
Follow these steps to integrate the Telegram Bot MCP Server with CrewAI.
Install CrewAI
Run pip install crewai
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
Customize the agent
Adjust the role, goal, and backstory to fit your use case
Run the crew
Run python crew.py — CrewAI auto-discovers 13 tools from Telegram Bot
Why Use CrewAI with the Telegram Bot MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Telegram Bot through the Model Context Protocol.
Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools
CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Telegram Bot + CrewAI Use Cases
Practical scenarios where CrewAI combined with the Telegram Bot MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries Telegram Bot for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff
Scheduled intelligence reports: set up a crew that periodically queries Telegram Bot, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain Telegram Bot tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow
Compliance and audit automation: a compliance agent queries Telegram Bot against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
Telegram Bot MCP Tools for CrewAI (13)
These 13 tools become available when you connect Telegram Bot to CrewAI via MCP:
delete_message
Delete a message from Telegram
forward_message
Forward a message in Telegram
get_bot_info
Get information about the Telegram bot
get_chat_admins
Get list of chat administrators
get_chat_info
Get information about a Telegram chat
get_chat_members_count
Get the number of chat members
get_updates
Useful for seeing what users have sent. Get updates for the Telegram bot
get_user_profile_photos
Returns a list of photo sizes. Get user profile photos
send_audio
Send an audio file to a Telegram chat
send_document
Send a document to a Telegram chat
send_message
Supports Markdown and HTML parse modes for formatting. Send a text message to a Telegram chat
send_photo
Optionally includes a caption. Send a photo to a Telegram chat
send_video
Send a video to a Telegram chat
Example Prompts for Telegram Bot in CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with Telegram Bot immediately.
"Get information about my Telegram bot."
"Send a message to my channel @mychannel saying 'Hello everyone!'"
"How many members are in my group -1001234567890?"
Troubleshooting Telegram Bot MCP Server with CrewAI
Common issues when connecting Telegram Bot to CrewAI through the Vinkius, and how to resolve them.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
Telegram Bot + CrewAI FAQ
Common questions about integrating Telegram Bot MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.Can different agents in the same crew use different MCP servers?
mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.What happens when an MCP tool call fails during a crew run?
Can CrewAI agents call multiple MCP tools in parallel?
process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.Can I run CrewAI crews on a schedule (cron)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.Connect Telegram Bot with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Telegram Bot to CrewAI
Get your token, paste the configuration, and start using 13 tools in under 2 minutes. No API key management needed.
