MCP server for Telegram serverless bots (@tgcloud) — project lifecycle, deploys, migrations and webhooks through the tgcloud CLI
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
TGCLOUD_TOKENAPI keyoptionalCLI access token from @BotFather (form app<id>:<secret>), used instead of tgcloud login
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
run_handlerRuns a handler or an endpoint on the platform using local files, without publishing themRuns a handler or an endpoint on the platform using local files, without publishing them
No input schema was published for this tool.
migrateApplies schema.js changes to the database (tgcloud migrate). push never does this.Applies schema.js changes to the database (tgcloud migrate). push never does this.
No input schema was published for this tool.
create_projectScaffolds a serverless bot with `npm create @tgcloud/bot <name>` inside parent_dir.Scaffolds a serverless bot with `npm create @tgcloud/bot <name>` inside parent_dir.
No input schema was published for this tool.
init_projectScaffolds tgcloud into an existing directory (tgcloud init, offline): tgcloud/schema.js,Scaffolds tgcloud into an existing directory (tgcloud init, offline): tgcloud/schema.js,
No input schema was published for this tool.
login_botRuns `tgcloud login` with a CLI access token (app<id>:<secret> from @BotFather → your bot →Runs `tgcloud login` with a CLI access token (app<id>:<secret> from @BotFather → your bot →
No input schema was published for this tool.
add_moduleScaffolds a module with `tgcloud add <target>` (tgcloud/ layout).Scaffolds a module with `tgcloud add <target>` (tgcloud/ layout).
No input schema was published for this tool.
upgradeOne-time move of schema.js, handlers/, and lib/ from the project root into tgcloud/One-time move of schema.js, handlers/, and lib/ from the project root into tgcloud/
No input schema was published for this tool.
statusShows local changes against the deployed snapshot (tgcloud status). Offline.Shows local changes against the deployed snapshot (tgcloud status). Offline.
No input schema was published for this tool.
diffLine-by-line diff of the local project against the deployed snapshot (tgcloud diff). Offline.Line-by-line diff of the local project against the deployed snapshot (tgcloud diff). Offline.
No input schema was published for this tool.
pushUploads changed modules in one atomic batch (tgcloud push). Without files, mirrors theUploads changed modules in one atomic batch (tgcloud push). Without files, mirrors the
No input schema was published for this tool.
pullMakes the local project match the cloud: updates the snapshot and working files (tgcloud pull).Makes the local project match the cloud: updates the snapshot and working files (tgcloud pull).
No input schema was published for this tool.
fetchUpdates the local snapshot of what is deployed without touching working files (tgcloud fetch).Updates the local snapshot of what is deployed without touching working files (tgcloud fetch).
No input schema was published for this tool.
resetDESTRUCTIVE: discards local module edits and restores the working tree from the last knownDESTRUCTIVE: discards local module edits and restores the working tree from the last known
No input schema was published for this tool.
deployRuns `npm run build` when package.json has a build script, then `tgcloud push`.Runs `npm run build` when package.json has a build script, then `tgcloud push`.
No input schema was published for this tool.
webhook_statusShows the platform-managed webhook (tgcloud webhook): URL, allowed_updates, pendingShows the platform-managed webhook (tgcloud webhook): URL, allowed_updates, pending
No input schema was published for this tool.
webhook_syncPoints the webhook at the platform and rebuilds allowed_updates from deployed handlersPoints the webhook at the platform and rebuilds allowed_updates from deployed handlers
No input schema was published for this tool.
16 of 16 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for Telegram serverless bots (@tgcloud) — project lifecycle, deploys, migrations and webhooks through the tgcloud CLI
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.