Tgden — Telegram Catalog & Search

tgden — Telegram catalog as an MCP server + free API

A live index of what exists on Telegram: 1.2M+ channels, 245k+ group chats, 160k+ bots, 4.9M+ indexed posts. No Telegram account. No API key. No install. CORS enabled — it runs from a browser tab as happily as from a server.

• MCP endpoint — https://tgden.com/api/mcp
• REST API — https://tgden.com/api/catalog
• Human UI — tgden.com · Docs — tgden.com/en/api-docs

Why another Telegram MCP server?

Every other Telegram MCP server connects to your Telegram account — you hand it an API hash, a phone number or a bot token, and it reads your dialogs, sends your messages, manages your groups. Useful, but it can only ever see what you already have access to.

This one is the opposite. It's a public catalog, so it answers the question none of the others can:

"What Telegram channels and groups exist about X, and which are worth joining?"

Because it never touches an account, there's nothing to leak and nothing to get banned.

Quick start

Claude Code

claude mcp add --transport http tgden https://tgden.com/api/mcp

Listed in the official MCP Registry as io.github.JustJuice55/telegram-catalog — clients that browse the registry find it under telegram.

Claude Desktop · Cursor · any MCP client — add to your MCP config:

{
  "mcpServers": {
    "tgden": {
      "type": "http",
      "url": "https://tgden.com/api/mcp"
    }
  }
}

That's the entire setup: streamable HTTP transport, stateless, no auth handshake.

Check it by hand:

curl -s https://tgden.com/api/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | jq '.result.tools[].name'

Tools

Resources

Free REST API (no key either)

Telegram has no official public search. Finding a channel, a live discussion group or a bot by topic means guessing usernames or trusting closed directories. If you don't speak MCP, the same catalog is plain HTTP.

GET /api/catalog — search

curl "https://tgden.com/api/catalog?q=crypto&type=channel&limit=3"

{
  "items": [
    {
      "id": "6ec0407a-4f5e-4a86-9154-f42481bc9413",
      "telegram_id": 2075341442,
      "username": "hamster_kombat",
      "title": "Hamster Kombat Announcement",
      "is_private": false,
      "avatar_url": "https://cdn4.telesco.pe/file/…"
    }
  ]
}

Call it from the browser

Access-Control-Allow-Origin: * is set on both read-only endpoints, so there is no proxy step: paste this into any page's devtools console (or a CodePen) and it answers.

const r = await fetch("https://tgden.com/api/catalog?q=crypto&type=channel&limit=3");
console.table((await r.json()).items);

Rate limit is shared and fair-use (~200 requests / 10s per IP). No key, no signup, no CORS proxy, no Access-Control-Allow-Credentials — nothing of yours is ever sent.

GET /api/suggest — instant autocomplete

Grouped, ranked suggestions as-you-type. Good for search boxes and agent tool-use.

curl "https://tgden.com/api/suggest?q=btc"

{
  "groups": [
    {
      "key": "chats",
      "label": { "en": "live chats", "ru": "живые чаты" },
      "items": [
        { "label": "BTC Times Discussion", "sub": "221 members",
          "href": "/en/chat/thebtctimes", "kind": "chat", "username": "thebtctimes" }
      ]
    }
  ]
}

Runnable examples: shell · Python · JavaScript.

Limits — published, because hidden limits are worse than low ones

Verified search-engine and AI crawlers are excluded from the shared limit.

We treat these as a contract: when they change, we announce it here and in the docs. No silent throttling. Need guaranteed throughput or a bulk export for something real? Open an issue, or reach us via @tgden_bot.

About the data

Parsed continuously from Telegram's public surfaces — fresher than any LLM training set, which is most of the point of exposing it over MCP.

Census 06.08.2026. The MCP server reports these totals live, so what your agent sees is current — not whatever was true when this file was written.

Public data only: channels, groups and bots that are already publicly listed or linked. No private groups, no archives from closed communities, no personal data.

Use cases

• Agent tool-use — give an agent real Telegram discovery in one config line.
• Research — map communities, track niches, study the open Telegram graph.
• Discovery bots — recommend channels and chats by topic.
• Market intel — what's being rented, sold and offered in regional Telegram economies.

Machine-readable site summary for AI crawlers: https://tgden.com/llms.txt

License

MIT — do what you want, no warranty. Data is public Telegram metadata.

Maintained by tgden.com. Not affiliated with Telegram FZ-LLC. Indexes public t.me links only.