Telegram Archive runs on your own machine — the client starts it, so there is no endpoint to ping. 656 installs a week from npm. Last commit 28 Oct 2026.
Search and read your archived Telegram chats and messages
What the code does
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
postinstall: node postinstall.js
execFileSync(tar, ["-xf", archive, "-C", work, BIN_NAME], { stdio: ["ignore", "ignore", "inherit"] });
const archive = path.join(work, assetName);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add telegram-archive-mcp -e 'TELEGRAM_ARCHIVE_URL=<TELEGRAM_ARCHIVE_URL>' -- npx -y telegram-archive-mcp{
"mcpServers": {
"telegram-archive-mcp": {
"command": "npx",
"args": [
"-y",
"telegram-archive-mcp"
],
"env": {
"TELEGRAM_ARCHIVE_URL": "<TELEGRAM_ARCHIVE_URL>"
}
}
}
}[mcp_servers.telegram-archive-mcp]
command = "npx"
args = ["-y", "telegram-archive-mcp"]
env = { TELEGRAM_ARCHIVE_URL = "<TELEGRAM_ARCHIVE_URL>" }{
"mcpServers": {
"telegram-archive-mcp": {
"command": "npx",
"args": [
"-y",
"telegram-archive-mcp"
],
"env": {
"TELEGRAM_ARCHIVE_URL": "<TELEGRAM_ARCHIVE_URL>"
}
}
}
}{
"servers": {
"telegram-archive-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"telegram-archive-mcp"
],
"env": {
"TELEGRAM_ARCHIVE_URL": "<TELEGRAM_ARCHIVE_URL>"
}
}
}
}Put your own value in place of
<TELEGRAM_ARCHIVE_URL> (Telegram Archive instance URL (e.g. http://localhost:8000)).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
TELEGRAM_ARCHIVE_USER (Telegram Archive login username), TELEGRAM_ARCHIVE_PASS (Telegram Archive login password), READ_ONLY (Set to true to hide refresh_stats, the one tool that asks the viewer to do work).
Alternatives to Telegram Archive
same job, measured the same wayTelegram MCP server: read, send, and search messages and manage chats via your account.
Your Telegram account for agents: read, search and send messages. Sign in with the tg CLI first.
Telegram personal-account MCP (MTProto user-auth). Read DMs, send messages, search across chats.
AI-native Microsoft Teams integration — read chats, send messages, search people
Search, read and reply to your Telegram Business chats, transcribed voice included.
Read and reply to your personal Telegram chats and all your Slack workspaces.
Let Claude or ChatGPT search, read and send your WhatsApp messages over MCP. OAuth sign-in.
Unofficial Telegram MCP server — read, search, reply and react in your own Telegram account.
Telegram Archive — questions
Answers built from our own checks of this server.