Telegram Channels
Provides access to public Telegram channels: retrieves channel profiles (title, username, verified status, description, subscriber count, photo/video/link counts) and recent posts with dates, text, view counts and media/link-preview indicators, with paging back through older posts via post id. Live and keyless, limited to what the public channel web preview shows.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
@pipeworx/telegram-channels
Public Telegram channels: profile (title, description, subscribers, media counts) and recent posts with date, text and view count. Live and keyless; public channels only.
Part of Pipeworx — an MCP gateway connecting AI agents to 2034+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
telegram_channel(channel)— title, username, verified flag, description, subscriber count, photo, video and link counts.telegram_channel_posts(channel, limit?, before_id?)— recent posts, newest first: post id and link, date, text, views, and whether it carries photo, video or a link preview. Page back withbefore_id.
Related MCP server: telegram-public-mcp-cloudflare
Auth
Keyless.
Data sources
Telegram, public channel web preview. Only what the public page shows to anyone without an account: no private channels, no groups, no member lists, no user profiles.
Gotchas: a name that is not a public channel (private, group, user, bot, missing) is reported as an error rather than an empty result. Counts such as "9.91M" are rounded by the source; the tool converts them to integers and they stay approximate. Each page carries about 20 posts; reactions and media files are not returned.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"telegram-channels": {
"url": "https://gateway.pipeworx.io/telegram-channels/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/telegram-channels/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 2034+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/telegram_channel \
-H 'Content-Type: application/json' \
-d '{"channel":"durov"}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/telegram_channel. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Run it from npm
@pipeworx/mcp-telegram-channels is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with npx, and it forwards every call to the same
https://gateway.pipeworx.io/telegram-channels/mcp endpoint shown above. It needs network access;
there is no offline mode.
{
"mcpServers": {
"telegram-channels": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-telegram-channels"]
}
}
}Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
"env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.
It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to
also list ask_pipeworx and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by
default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check
your Node version's documentation.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Telegram Channels data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Public Telegram channel posts, views, reactions, media and subscriber counts. No login needed.
Public Telegram channel posts without login: text, date, views, reactions, media; new-only option.
Live Telegram data: trending topics, channel profiles & metrics, post history incl. edits/deletions.
Public Telegram channel posts without login: text, views, reactions, media, exact subscribers.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables interaction with Telegram channels through the Bot API, supporting comprehensive messaging operations including sending text/photos, creating polls, managing reactions, and editing/deleting messages. Provides complete channel management capabilities for automated Telegram bot operations.7MIT
- AlicenseNot gradedqualityDmaintenanceReads public Telegram channel pages and exposes them as MCP tools over Streamable HTTP/JSON-RPC, enabling retrieval of channel info, latest posts, and search without Telegram API credentials.1MIT
- AlicenseNot gradedqualityCmaintenanceRead public Telegram channels from AI agents — channel metadata, posts, comments, and search. No MTProto, no Telethon, no api_id.1MIT
- FlicenseNot gradedqualityDmaintenanceRead-only MCP server for Telegram channels. Provides access to posts, comments, reactions, and aggregated statistics via MTProto.-