MCP server for Telegram Archive — search messages, browse chats, and access history
Runs on your machine from its package; the steps are below.
At most: only reads or looks up information.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y telegram-archive-mcp
MCP client config
{
"mcpServers": {
"telegram-archive": {
"command": "npx",
"args": [
"-y",
"telegram-archive-mcp"
]
}
}
}Run
docker run -i --rm drumsergio/telegram-archive-mcp:v0.3.1
MCP client config
{
"mcpServers": {
"telegram-archive": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"drumsergio/telegram-archive-mcp:v0.3.1"
]
}
}
}
An MCP server for any Telegram-Archive instance. LLMs use it to search messages, browse chats and read archived Telegram history.
telegram-archive://stats, telegram-archive://chats).get_messages_by_date).get_media)./api/login with TELEGRAM_ARCHIVE_USER and TELEGRAM_ARCHIVE_PASS./mcp) over HTTP, or stdio with TRANSPORT=stdio.MCP_AUTH_TOKEN adds bearer auth when you expose it.npx telegram-archive-mcp) and multi-arch Go binaries.npx telegram-archive-mcp
npx fetches the server and runs it on stdio, so your MCP client starts it for you. For Claude Desktop, Cursor or Claude Code, add:
{
"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"
}
}
}
}
Set the URL, user and password of your Telegram-Archive viewer. Docker Compose (HTTP on 127.0.0.1:8080) and local builds are in Getting started.
The full documentation is at geiserx.github.io/telegram-archive-mcp.