[](https://github.com/dealfluence/adeu) [![MCP
from $29/mo
Nothing to run from here
Telegram Bot is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
MCP server for Telegram Bot API — send messages, manage chats, webhooks, files, and more through 27 tools
Quickstart
# 1 — run it from where its publisher ships it
npx -y @node2flow/telegram-bot-mcp
# 2 — the plan is chosen at checkout, in the browser
# 3 — ask your agent something
> MCP server for Telegram Bot API — send messages, manage chats, webhooks, files, and more through 27 tools
Publishernot claimed
NOAll 6 servers
@node2flow6 servers
5 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Telegram Bot as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add telegram-bot-mcp -- npx -y @node2flow/telegram-bot-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
This is a paid listing, so the CLI has to be signed in and the licence has to be on your account — how the login works. Until then the install stops with the price rather than half-writing a config entry.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
27 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get basic information about the bot: id, username, first_name, can_join_groups, can_read_all_group_messages, supports_inline_queries.
Takes no parameters.
Example callreturns →
Set the list of bot commands shown in the Telegram chat menu. Each command has a
Takes no parameters.
Example callreturns →
Send a text message to a chat. Supports Markdown, MarkdownV2, and HTML formatting. Can include inline keyboards via reply_markup.
Takes no parameters.
Example callreturns →
Send a photo to a chat. Provide a URL or file_id from a previously uploaded photo.
Takes no parameters.
Example callreturns →
Send a document/file to a chat. Provide a URL or file_id. Max 50MB for bots.
Takes no parameters.
Example callreturns →
Send a video to a chat. Provide a URL or file_id. Supports MPEG4 format, max 50MB.
Takes no parameters.
Example callreturns →
Send an audio file to a chat. Displayed as a music player. Provide a URL or file_id. Max 50MB, MP3/M4A format.
Takes no parameters.
Example callreturns →
Send a geographic location point to a chat.
Takes no parameters.
Example callreturns →
Send a poll to a chat. Supports regular polls and quiz mode. For quiz mode, set type to
Takes no parameters.
Example callreturns →
Send a phone contact card to a chat.
Takes no parameters.
Example callreturns →
Edit the text of a previously sent message. The bot must be the author of the message.
Takes no parameters.
Example callreturns →
Edit the caption of a previously sent media message (photo, video, document, audio).
Takes no parameters.
Example callreturns →
Delete a message. Bot must have delete permission in group chats. Messages older than 48 hours cannot be deleted.
Takes no parameters.
Example callreturns →
Get detailed information about a chat: title, description, type, member count, permissions, pinned message, etc.
Takes no parameters.
Example callreturns →
Get the number of members in a chat.
Takes no parameters.
Example callreturns →
Get information about a specific member: status (creator, administrator, member, restricted, left, kicked), permissions, and custom title.
Takes no parameters.
Example callreturns →
Ban a user from a group, supergroup, or channel. The user will be unable to return unless unbanned. Bot must be admin with ban permission.
Takes no parameters.
Example callreturns →
Unban a previously banned user. The user is NOT added back automatically and must rejoin via invite link.
Takes no parameters.
Example callreturns →
Set a webhook URL for receiving Telegram updates. Telegram sends POST requests with JSON Update objects to this URL. Supported ports: 443, 80, 88, 8443.
Takes no parameters.
Example callreturns →
Remove the webhook integration. After this, you can use getUpdates for polling.
Takes no parameters.
Example callreturns →
Get current webhook status: URL, pending update count, last error date/message, max connections, and allowed update types.
Takes no parameters.
Example callreturns →
Answer a callback query from an inline keyboard button press. Must be called to stop the loading indicator on the button.
Takes no parameters.
Example callreturns →
Get file info and download URL. Returns file_id, file_size, file_path, and a ready-to-use download_url. Files up to 20MB.
Takes no parameters.
Example callreturns →
Get a list of profile photos for a user.
Takes no parameters.
Example callreturns →
Pin a message in a chat. Bot must have pin_messages admin permission in groups/supergroups.
Takes no parameters.
Example callreturns →
Unpin a message in a chat. If message_id is not provided, unpins the most recent pinned message.
Takes no parameters.
Example callreturns →
Create an additional invite link for a chat. Bot must be admin with invite_users permission.
Takes no parameters.
Example callreturns →
Standardmost installed
$19 / month
- 16,000 calls a month, included
- 192 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Pro
$69 / month
- 160,000 calls a month, included
- 1,920 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
No call is billed on its own, and this plan carries no monthly call limit. $19 a month covers every tool at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 99 / 100
Release 1.0.4 · scanned 25 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest92c9c226b4496df915b2a5231f30c69c69021d80b0ea20252624a6c8f58ace56
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest92c9c226b4496df9
Scanned2026-08-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 1.0.4 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
1.0.4
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Telegram Bot in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.