mcp-telegram-bot
MCP server that exposes a Telegram bot
Install
pip install mcp-telegram-bot
Setup
- Create a Telegram bot by talking to @BotFather on Telegram
- Get your bot token
- Set the
TELEGRAM_BOT_TOKENenvironment variable
Usage
export TELELEGRAM_BOT_TOKEN="your-bot-token-here"
mcp-telegram-bot
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
git clone https://github.com/daedalus/mcp-telegram-bot.git
cd mcp-telegram-bot
pip install -e ".[test]"
# run tests
pytest
# format
ruff format src/ tests/
# lint
ruff check src/ tests/
# type check
mypy src/
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for mcp-telegram-bot 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mcp_telegram_bot-0.1.0.tar.gz | 3.9 kB | With provenance | Details for mcp_telegram_bot-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_telegram_bot-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for mcp_telegram_bot-0.1.0-py3-none-any.whl |
Total release size: 8.7 kB
Release files / mcp_telegram_bot-0.1.0.tar.gz
| Download URL | mcp_telegram_bot-0.1.0.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ad8834e2e6060959cfc5ad333f6abced9962329cc2847689fdbf3c1af10dc38c
|
|
BLAKE2b-256 checksum How to use checksums |
7f3af94a4e93e2f811c86f1d9f1ac791617bb2351cade97e3295d7cee58b5336
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 28, 2026.
Transparency logRelease files / mcp_telegram_bot-0.1.0-py3-none-any.whl
| Download URL | mcp_telegram_bot-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a77925bd1e8fd6311c5a0f9bfff5710f0e94fa68cacadfb9040c23f188ec8f5a
|
|
BLAKE2b-256 checksum How to use checksums |
e6a9f180a0b60d01c5ad00b79aa5b0322cab7c45d29525f396bbc0176f243719
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 28, 2026.
Transparency logSecurity for mcp-telegram-bot 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for mcp_telegram_bot-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 28, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
