Telegram Channel Scraper Mcp

io.github.khadinakbaronlinePublished by GitHub account khadinakbaronlinev1.0.0Updated Oct 24, 2026

Scrape messages, extract leads from public Telegram channels. No login required.

Overview

AI-generated overview

A local MCP server that lets an assistant scrape messages and extract leads from public Telegram channels without logging in.

What you can do
Scrape messages from public Telegram channels and pass them to the assistant for review or processing. Extract lead information from the collected channel content. No tool list is published, so the exact operations are not documented beyond scraping and lead extraction.
When to use it
Useful when you want an assistant to gather content or contact-style leads from public Telegram channels as part of research, outreach or monitoring work, and you prefer a local process over a hosted service.
Requirements
Runs as a local process over stdio, installed from the npm package telegram-channel-scraper-mcp-server, so Node.js and npm are needed on the machine. No login, environment variables or headers are declared. It is desktop-only and needs network access to reach Telegram.
Before you install
It collects data from third-party public channels, so consider privacy, copyright and Telegram's terms before storing or reusing scraped messages or leads. Scraping may be rate-limited or blocked. No credentials are declared, but review the package before running it locally.

Installation

In SourceWeft

  1. Open Telegram Channel Scraper 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.0.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 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.