Read-only MCP server that exposes curated Telegram groups to Claude Code and other MCP clients
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"arbling-telegram-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# arbling-telegram-mcp A read-only MCP (Model Context Protocol) server that gives Claude Code, Cowork, and any other MCP client access to a curated set of Telegram groups via your own Telegram account (MTProto). It reads only the groups you explicitly list in a hand-edited YAML config — not your full Telegram history, not DMs, not unlisted groups. All data stays local on your machine. ## Privacy This server is read-only. It cannot send messages, join or leave groups, react, or delete anything. It never accesses your DMs or private conversations. It only reads the groups you explicitly add to `curated-groups.yaml`. Your Telegram session file stays on your machine — it is never transmitted or logged. Your phone number is masked in all output. There is no telemetry, analytics, or any outbound network traffic beyond the Telegram API itself. ## 5-step onboarding ```sh # 1. Get Telegram API credentials (one-time, free) # Go to https://my.telegram.org → "API development tools" # Create an app, save api_id and api_hash to your password manager. # 2. Install the package pip install arbling-telegram-mcp # or via uvx (no install needed): # uvx arbling-telegram-mcp auth # 3. Authenticate (one-time interactive — needs your phone for the SMS code) TELEGRAM_API_ID=<your_id> TELEGRAM_API_HASH=<your_hash> arbling-telegram-mcp auth # 4. Discover your groups and create the curated config TELEGRAM_API_ID=<your_id> TELEGRAM_API_HASH=<your_hash> \ arbling-telegram-mcp list-groups > ~/.arbling-telegram-mcp/curated-groups.yaml # Edit the YAML: move groups you care about into tech_news / investor / tech_mentors # Delete any groups you don't want the MCP to read. # 5. Add to your MCP client config — see "Claude Code config" below ``` ## Claude Code config (`~/.claude.json`) ```json { "mcpServers": { "telegram": { "command": "arbling-telegram-mcp", "env": { "TELEGRAM_API_ID": "<your_id>", "TELEGRAM_API_HASH": "<your_hash>" } } …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.