Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Search and read your archived Telegram chats and messages
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
TELEGRAM_ARCHIVE_URL, TELEGRAM_ARCHIVE_USER, TELEGRAM_ARCHIVE_PASS, READ_ONLYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"telegram-archive": {
"command": "npx",
"args": [
"-y",
"telegram-archive-mcp"
],
"env": {
"TELEGRAM_ARCHIVE_URL": "your-value",
"TELEGRAM_ARCHIVE_USER": "your-value",
"TELEGRAM_ARCHIVE_PASS": "your-value",
"READ_ONLY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add telegram-archive --env TELEGRAM_ARCHIVE_URL=your-value --env TELEGRAM_ARCHIVE_USER=your-value --env TELEGRAM_ARCHIVE_PASS=your-value --env READ_ONLY=your-value -- npx -y telegram-archive-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"telegram-archive": {
"command": "npx",
"args": [
"-y",
"telegram-archive-mcp"
],
"env": {
"TELEGRAM_ARCHIVE_URL": "your-value",
"TELEGRAM_ARCHIVE_USER": "your-value",
"TELEGRAM_ARCHIVE_PASS": "your-value",
"READ_ONLY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"telegram-archive": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"telegram-archive-mcp"
],
"env": {
"TELEGRAM_ARCHIVE_URL": "your-value",
"TELEGRAM_ARCHIVE_USER": "your-value",
"TELEGRAM_ARCHIVE_PASS": "your-value",
"READ_ONLY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
TELEGRAM_ARCHIVE_USER envREAD_ONLY envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account GeiserX, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: TELEGRAM_ARCHIVE_URL, TELEGRAM_ARCHIVE_PASS
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.4.1) reached the registry 10 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: Vexa, emailmd, MCP WhatsApp Cloud
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
telegram-archive-mcp
An MCP server for any Telegram-Archive instance. LLMs use it to search messages, browse chats and read archived Telegram history.
initialize handshake work unchanged.get_media).refresh_stats; READ_ONLY=1 hides that one too./api/login with TELEGRAM_ARCHIVE_USER and TELEGRAM_ARCHIVE_PASS.Origin, caps request bodies, and requires MCP_AUTH_TOKEN on any other address.Every client below runs the server over stdio. Set the URL, user and password of your Telegram-Archive viewer.
Claude Code
claude mcp add --env TELEGRAM_ARCHIVE_URL=http://localhost:8000 \
--env TELEGRAM_ARCHIVE_USER=admin --env TELEGRAM_ARCHIVE_PASS=your-viewer-password \ --transport stdio telegram-archive -- npx -y telegram-archive-mcp
Claude Desktop (claude_desktop_config.json) and Cursor (~/.cursor/mcp.json)
{
"mcpServers": { "telegram-archive": { "command": "npx", "args": ["-y", "telegram-archive-mcp"], "env": { "TELEGRAM_ARCHIVE_URL": "http://localhost:8000", "TELEGRAM_ARCHIVE_USER": "admin", "TELEGRAM_ARCHIVE_PASS": "your-viewer-password" } } } }
VS Code (.vscode/mcp.json, asks for the password once)
{
"inputs": [ { "type": "promptString", "id": "tg-pass", "description": "Telegram-Archive viewer password", "password": true } ], "servers": { "telegram-archive": { "type": "stdio", "command": "npx", "args": ["-y", "telegram-archive-mcp"], "env": { "TELEGRAM_ARCHIVE_URL": "http://localhost:8000", "TELEGRAM_ARCHIVE_USER": "admin", "TELEGRAM_ARCHIVE_PASS": "${input:tg-pass}" } } } }
Codex (~/.codex/config.toml)
[mcp_servers.telegram-archive]
command = "npx" args = ["-y", "telegram-archive-mcp"] env = { TELEGRAM_ARCHIVE_URL = "http://localhost:8000", TELEGRAM_ARCHIVE_USER = "admin", TELEGRAM_ARCHIVE_PASS = "your-viewer-password" }
Docker, for any client above: use docker as the command with these arguments, and a release tag from the releases page, never latest:
docker run -i --rm -e TELEGRAM_ARCHIVE_URL -e TELEGRAM_ARCHIVE_USER -e TELEGRAM_ARCHIVE_PASS drumsergio/telegram-archive-mcp:vX.Y.Z
The npm package downloads the release binary on first start and checks it against the checksums published with the package, so it also works with npm 12, which skips install scripts. A long-running HTTP server (Docker Compose) and local builds are in Getting started.
| Tool | What it does |
|---|---|
list_chats | Lists chats, most recent first; filter by search (name), archived or folder_id. Each chat's ref is the chat_id the other tools take. |
list_folders | Lists your Telegram folders and their ids. |
search_all_chats | Searches message text in every chat at once. |
search_messages | Searches one chat, optionally one forum topic. |
get_messages | Reads a chat newest first, by offset or keyset cursor, optionally one forum topic. |
get_message_context | Returns one message with the messages before and after it. |
get_messages_by_date | Returns every message of one calendar day in a timezone. |
get_pinned_messages | Returns a chat's pinned messages. |
get_topics | Lists a forum group's topics; their ids feed topic_id. |
get_chat_stats | Message and media counts and size of one chat. |
get_media | The photo attached to a message, as an image, or the file's details. |
refresh_stats | Makes the viewer recalculate archive-wide statistics. Hidden with READ_ONLY=1. |
Every tool returns structured content with an output schema, alongside the same JSON as text. Arguments and defaults are on Usage.
The full documentation is at geiserx.github.io/telegram-archive-mcp.