telegram-mcp

Telegram MCP server powered by Telethon to let MCP clients read chats, manage groups, and send/modify messages, media, contacts, and settings.

Runs with mockssource: GitHubPythonApache-2.0commit 81ad14bd076d

Python, Apache-2.0 licensed. The project labels itself: admin, api, chat management, contacts, groups, mcp, media and messaging.

telegram-mcp runs, with stand-ins for the services it depends on. An Argusic agent installed it in 1 minute and hit no errors on a clean machine with no GPU, and the whole session was recorded.

All 791 unit tests pass with 91%+ coverage covering runtime, sanitize, session generation, transcription, chat allowlist, aliases, file path security, reactions, media, and other modules.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
2
last tested
stars
2,060
forks
525
open issues
44
watchers
8
size
3 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Install time
1 minutes
Cold machine to finish
2 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
pytest tests/ exited 0, 791 passed, 91%+ code coverage
Model tokens used
35,550
Exact commit tested
81ad14bd076d
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

 succeeded in 0ms:
Install steps took approximately:
- venv creation: ~4s
- pip install -r requirements.txt: ~10s
- pip install -e .: ~1s
- pip install pytest: ~2s
- all tests pass: 791 passed in ~7s
Total install time: <1 minute
All observations are in. Let me compile the final report.
tokens used
35,550
All observations are in. Let me compile the final report.

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 1 minute, faster than the median of the 9 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.

Of the 10 admin projects Argusic has installed and timed, telegram-mcp was the 1st fastest to reach a running state, and 8 of 10 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.02
Argusic Runner1/3Runs with mocks92.000.05

Topics (from GitHub)

adminapichat-managementcontactsgroupsmcpmediamessagingsearchtelegramtelegram-apitelegram-clienttelethon

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/telegram-mcp.svg)](https://argusic.com/subject/telegram-mcp)

Questions

Does telegram-mcp run?
telegram-mcp runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test telegram-mcp?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 81ad14bd076d. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test telegram-mcp?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does telegram-mcp take to install?
1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does telegram-mcp need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing telegram-mcp?
Nothing did, in the recorded run: zero errors between clone and running.
How does telegram-mcp compare with the alternatives?
Of the 10 admin projects Argusic has installed and timed, telegram-mcp was the 1st fastest to reach a running state, and 8 of 10 reached one at all.
Where is the evidence for telegram-mcp?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion