Telegram Business MCP

io.github.OlegNickeshinPublished by GitHub account OlegNickeshinv0.1.0Updated Oct 24, 2026

Self-hosted Telegram Business MCP: search chats, read files and transcripts, optionally reply.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A self-hosted Telegram Business MCP server that lets an assistant search chats, read files and transcripts, and optionally send replies.

What you can do
Search Telegram Business chats and conversations by keyword or query, per the description's mention of chat search. Read files shared in chats and retrieve conversation transcripts. Optionally reply to chats when that capability is enabled. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Useful when an assistant should work with a Telegram Business account's conversations: finding past messages, pulling up shared files or transcripts, and drafting or sending replies. Best suited to people who can host the server themselves and want their own Telegram data accessible to an assistant.
Requirements
Runs as a self-hosted remote endpoint over streamable HTTP at a host you provide, so you need somewhere to deploy and run it. The manifest declares no authentication, environment variables, headers or packages, and no Telegram credentials are documented, so the setup details are not specified in the available information.
Before you install
It gives an assistant access to private Telegram Business conversations, files and transcripts, which are sent to the assistant and the server host. The optional reply capability can send messages to real people, so enable it deliberately. The manifest declares no authentication, so anyone who can reach the endpoint may be able to use it; secure the deployment before exposing it.

Installation

In SourceWeft

  1. Open Telegram Business MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 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 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 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.