Telegram Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.1.0Updated Oct 27, 2026

Use the Telegram Bot API (free bot; set TELEGRAM_BOT_TOKEN): bot info, send messages, read updates.

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

Local MCP server that connects an assistant to a Telegram bot via the Bot API to send messages and read updates.

What you can do
  • Retrieve bot information for the configured Telegram bot
  • Send messages through the bot
  • Read incoming updates from the bot
When to use it
Useful when you want an assistant to post messages to Telegram chats or pull recent bot updates during a session, for example for notifications or simple chat-driven workflows.
Requirements
Runs as a local stdio process, installed from the npm package @mrfentmen/telegram-mcp (Node.js runtime). Needs a Telegram bot and its token supplied through the TELEGRAM_BOT_TOKEN environment variable; the manifest declares no environment variables, so this must be configured yourself. Network access to the Telegram Bot API.
Before you install
Requires a Telegram bot token (TELEGRAM_BOT_TOKEN), a secret that grants control of the bot; keep it out of shared configs. The server can send messages on your behalf, so review what the assistant sends. Message content and updates pass through Telegram's servers.

Installation

In SourceWeft

  1. Open Telegram 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. v1.1.0LatestOct 17, 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.