
Mcp Telegram Bot
io.github.daedalusPublished by GitHub account daedalusv0.1.0Updated Oct 24, 2026
MCP server that exposes a Telegram bot
Overview
A local MCP server that connects an assistant to a Telegram bot so it can send messages, read recent updates and check bot status.
- What you can do
- Send messages to a Telegram chat through the bot's send_message tool. Retrieve bot information with get_me and recent incoming updates with get_updates. Read the bot://status resource for bot status.
- When to use it
- Useful when you want an assistant to post messages to Telegram chats or check what a bot has recently received, for example for notifications or simple chat workflows.
- Requirements
- Runs locally as a Python package installed with pip. Needs a Telegram bot created through BotFather and its bot token supplied in the TELEGRAM_BOT_TOKEN environment variable. Network access to Telegram is required.
Installation
In SourceWeft
- Open Mcp Telegram Bot in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-telegram-bot
MCP server that exposes a Telegram bot
[PyPI] [Python] [Coverage] [Ruff]
Install
Setup
- Create a Telegram bot by talking to @BotFather on Telegram
- Get your bot token
- Set the
TELEGRAM_BOT_TOKENenvironment variable
Usage
MCP Tools
- send_message: Send a message to a Telegram chat
- get_me: Get bot information
- get_updates: Get recent updates from Telegram
MCP Resources
- bot://status: Get bot status
mcp-name: io.github.daedalus/mcp-telegram-bot
Development
License
MIT
Source: README.md at commit 2dab562
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts