Telegram Channel Scraper

io.github.brenton-kellerPublished by GitHub account brenton-kellerv0.1.0Updated Oct 7, 2026

Public Telegram channel posts, views, reactions, media and subscriber counts. No login needed.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingCommunication & Collaboration

Overview

AI-generated overview

A remote Apify-hosted MCP server that lets an assistant pull public Telegram channel posts, views, reactions, media and subscriber counts without logging in.

What you can do
Retrieve posts from public Telegram channels, including views, reactions and media attached to each post. Read subscriber counts for public channels. Collect this public channel data without a Telegram login. No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Useful when you want an assistant to gather or summarize public Telegram channel content and engagement signals, such as posts, views, reactions and subscriber numbers, without signing in to Telegram.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP. The manifest declares no authentication, environment variables or headers, but the provider is Apify, so an Apify account or token may be involved in practice.
Before you install
It collects data from public Telegram channels and sends it to a third-party service (Apify); consider whether that content and any personal data in it should leave your environment. No login is needed, but confirm any Apify account or billing terms before relying on it.

Installation

In SourceWeft

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

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.brenton-keller%2Ftelegram-channel-scraper/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "telegram-channel-scraper": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=brenton8907/telegram-channel-scraper"
    }
  }
}

Tools

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

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

28% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.