tgden — Telegram catalog as an MCP server + free API
MCP serverSearchThis gives your AI a searchable catalog of Telegram channels, chats, and bots. Once added, it can look up matches across 1.2M+ channels, 245k+ chats, and 160k+ bots whenever you ask. No account or key is needed to search.
Use tgden — Telegram catalog as an MCP server + free API in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add tgden — Telegram catalog as an MCP server + free API and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use tgden to search telegram
No key or account is asked for. Not verified by us yet: Ahel has not run a call through it.
Details
Available today. Use it from your connected AI after setup.
No key or account is asked for. Not verified by us yet: Ahel has not run a call through it.
After adding it, ask your AI to find Telegram channels, chats, or bots on a topic or name you have in mind. It will search the catalog and report back what it finds.
What your AI can do with it
- Search a catalog of 1.2M+ Telegram channels
- Look up chats from 245k+ listings
- Find bots among 160k+ entries
- Search without creating an account or using a key
Install tgden — Telegram catalog as an MCP server + free API
The server’s own address, for the clients that take one directly. Or connect Ahel once and every client you use reads it from one address, with the account kept on Ahel rather than in each client’s config.
Claude Code
claude mcp add --transport http --scope user tgden-telegram-catalog-as-an-mcp 'https://tgden.com/api/mcp'Run it once in your project, then open /mcp to approve any sign-in the server asks for.
Claude Desktop
https://tgden.com/api/mcpAdd a custom connector in Settings, paste this address, and approve the sign-in.
Cursor
cursor://anysphere.cursor-deeplink/mcp/install?name=tgden-telegram-catalog-as-an-mcp&config=eyJ1cmwiOiJodHRwczovL3RnZGVuLmNvbS9hcGkvbWNwIn0=Open the link and Cursor adds the server at that address.
ChatGPT
https://tgden.com/api/mcpIn Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.
Codex
codex mcp add tgden-telegram-catalog-as-an-mcp --url 'https://tgden.com/api/mcp'Run it once, then sign in with codex mcp login tgden-telegram-catalog-as-an-mcp if the server asks for an account.
From the project's README
As published by justjuice55/tgden-api in README.md.
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?"
| account-based Telegram MCP | tgden MCP | |
|---|---|---|
| Credentials required | API ID/hash, phone or bot token | none |
| Install | local process (Python/Go/Node) | none — a hosted HTTP URL |
| Can see | chats you already joined | 1.6M+ public entities you haven't |
| Answers "what exists?" | no | yes |
| Can act on your account | yes | no — read-only by design |
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
| Tool | What it answers |
|---|---|
search_telegram | Full-text search across channels, group chats and bots — with subscriber/member counts, categories and trust scores. |
best_channels_by_category | "Best Telegram channels for crypto / AI / news / gaming…" — ranked by subscribers. |
channel_stats | Everything known about one channel, by @username. |
search_posts | Full-text search over recent posts — what channels actually said, not just their bio. |
market_listings | Real classified listings (rent, sale, services, jobs) parsed from regional Telegram groups across 🇦🇪 🇹🇷 🇹🇭 🇻🇳 🇬🇪 🇺🇸. |
market_stats | Listing totals by country and type. |
Resources
| URI | Contents |
|---|---|
tgden://catalog/top-channels | Top-100 channels by subscribers. |
tgden://catalog/categories | Full category taxonomy with channel counts. |
tgden://market/listings-latest | The 100 freshest marketplace listings. |
tgden://market/stats | Marketplace totals by country and type. |
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
| Param | Type | Default | Notes |
|---|---|---|---|
q | string | — | Free-text query (title, username, topic) |
limit | int | 20 | Max results to return |
type | string | all | channel · chat · bot (omit for everything) |
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
| Surface | Limit |
|---|---|
REST (/api/catalog, /api/suggest) | ~200 requests / 10s per IP, shared fair-use |
MCP (/api/mcp) | 240 calls / hour per IP |
| Auth | none — no key, no signup, no email |
| Cost | free |
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.
| Channels | 1,298,868 |
| Group chats | 282,719 |
| Bots | 157,909 |
| Indexed posts | 4,955,162 |
| Marketplace listings | 34,862 |
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.
Tools it offers (6)
What this server listed when Ahel dialed its public endpoint in Sep 2026, with no key and no account of yours. The names are the server’s own.
search_telegramchannel_statssearch_postsmarket_listingsmarket_statsbest_channels_by_category
Signals
- GitHub stars
- 1
- Last commit
- Aug 2026
Ahel review
S4info
community integration, published by justjuice55, not telegram
Automated review, not a security audit. Ruleset v1.
Advanced
- Delivery
- telegram-catalog MCP server → your Ahel connector (mcp.ahel.ai) → your AI.
- Item type
- mcp-server
- Key
io-github-justjuice55-telegram-catalog- Source
- github.com/justjuice55/tgden-api
- Hosted endpoint
https://tgden.com/api/mcp
github.com/justjuice55/tgden-api