Dynamic Telegram Bot Api Mcp

io.github.patricktobias86Published by GitHub account patricktobias86v10.3.3Updated Oct 26, 2026

A dynamic, self-refreshing MCP gateway for the complete Telegram Bot API

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

Local MCP gateway that exposes the full Telegram Bot API to an assistant, refreshing its tool set dynamically as the API changes.

What you can do
  • Provide access to the complete Telegram Bot API through a single MCP gateway.
  • Refresh its exposed tools dynamically so the available operations track the API.
  • Let an assistant act on a Telegram bot's chats, messages and other bot features, as far as the Bot API covers them.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth adding when you want an assistant to drive a Telegram bot through the Bot API from your own machine, for example to send or manage bot messages and other bot operations, and you prefer a gateway that keeps itself up to date rather than a fixed tool list.
Requirements
Runs as a local stdio process installed from the npm package dynamic-telegram-bot-api-mcp, so a Node.js runtime is needed. Requires a Telegram Bot API token from @BotFather, supplied through the TELEGRAM_BOT_TOKEN environment variable. Desktop only; network access to Telegram is implied.
Before you install
The bot token is a secret that grants full control of the bot; keep it out of logs and shared configs. Actions taken through the Bot API can send, edit or delete messages and change bot settings, so review what the assistant is allowed to do. Because the tool set refreshes dynamically, the operations available may change without notice.

Installation

In SourceWeft

  1. Open Dynamic Telegram Bot Api Mcp in the dashboard and add it to a workspace.
  2. 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

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v10.3.3LatestSep 16, 2026

Score

25% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.