Telegram Archive MCP logo

Telegram Archive MCP

by GeiserX

Search, browse, and inspect archived Telegram chats through an MCP server connected to Telegram-Archive.

Install Telegram Archive MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "geiserx-telegram-archive-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "telegram-archive-mcp"
      ],
      "env": {
        "TELEGRAM_ARCHIVE_URL": "YOUR_VALUE_HERE",
        "TELEGRAM_ARCHIVE_USER": "YOUR_VALUE_HERE",
        "TELEGRAM_ARCHIVE_PASS": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

GeiserX/telegram-archive-mcp connects AI clients to a Telegram-Archive instance for searching messages, browsing chats, and reading archived history. It provides read-only archive resources plus tools for message paging, date-based retrieval, pinned messages, forum topics, chat statistics, and attached photos. The server supports stdio for client-managed processes and HTTP at /mcp, with Telegram-Archive credentials supplied through environment variables. Use it when an agent needs to investigate or summarize an existing Telegram archive without modifying it.

Use cases

  • Search archived Telegram discussions for specific terms
  • Browse chats and retrieve historical messages
  • Review messages from a particular calendar day
  • Inspect pinned messages and forum topics
  • Analyze photos attached to archived messages

Key features

  • Full-text message search
  • Offset and keyset-cursor pagination
  • Calendar-day retrieval with timezone support
  • Read-only archive resources
  • Attached photo retrieval for model viewing
  • Stdio and HTTP JSON-RPC transports

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

6/6 checks healthy over the last 81d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · telegram-archive-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars7Stargazers on the source repository.
npm downloads232Package downloads in the last 30 days.
Last commit8d agoMost recent push to the default branch.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Telegram Archive MCP works

What GeiserX/telegram-archive-mcp does

GeiserX/telegram-archive-mcp exposes an existing Telegram-Archive installation to MCP-compatible AI clients. Its focus is read access: an agent can discover available chats, search archived messages, inspect conversation history, and retrieve related metadata. The archive remains the source of truth; this server provides an MCP interface rather than importing or storing Telegram data itself.

The server exposes four read-only resources covering archive statistics, chat listings, folders, and health information. It also provides ten tools for operations such as searching messages, retrieving messages in pages, reading messages from a complete calendar day, viewing pinned messages, examining forum topics, and checking statistics for an individual chat. Message photos can be returned as images for model inspection.

How it works

At startup, the server uses the configured Telegram-Archive URL and viewer credentials to sign in through the archive's /api/login endpoint. MCP clients can then communicate with it through one JSON-RPC endpoint at /mcp over HTTP, or launch it directly over standard input and output.

Message retrieval supports both offset-based and keyset-cursor paging. Date queries operate on whole calendar days in a specified timezone, which is useful when an investigation is organized around local dates rather than message offsets. Media retrieval handles the photo attached to a message and scales larger images to 1568 pixels before returning them to the model.

Setup and configuration

The npm package can be started with npx telegram-archive-mcp. In a stdio client configuration, set the archive URL, viewer username, and viewer password in the server's environment. Claude Desktop, Cursor, and Claude Code can start the package with npx -y telegram-archive-mcp.

The primary connection variables are TELEGRAM_ARCHIVE_URL, TELEGRAM_ARCHIVE_USER, and TELEGRAM_ARCHIVE_PASS. Set TRANSPORT=stdio to select stdio explicitly; HTTP is available through /mcp. Docker images, Docker Compose configuration, and multi-architecture Go binaries are also available. The default listener is restricted to loopback. When exposing the HTTP endpoint beyond that boundary, MCP_AUTH_TOKEN enables bearer-token authentication.

Tools and capabilities

  • Search archived Telegram messages with full-text search.
  • List chats and browse archived conversation history.
  • Retrieve messages using offset or keyset-cursor pagination.
  • Read all messages from a calendar day in a chosen timezone with get_messages_by_date.
  • Inspect pinned messages, forum topics, and per-chat statistics.
  • Retrieve an attached photo with get_media for model analysis.
  • Read archive statistics, chats, folders, and health through MCP resources.

Limitations and notes

The interface is read-only, so it is intended for finding and examining archived content rather than sending messages or changing chats. Access depends on a reachable Telegram-Archive instance and valid viewer credentials. The server is designed around archived Telegram data; it does not provide direct live Telegram access. HTTP deployments should account for the loopback default and configure bearer authentication when the endpoint is exposed.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Telegram Archive MCP

GeiserX/telegram-archive-mcp is an MCP server that connects AI clients to a Telegram-Archive instance. Its main tools search messages, browse chats, retrieve paged or date-based history, inspect pinned messages and forum topics, view chat statistics, and return attached photos for model analysis.

Install it by running `npx telegram-archive-mcp`, or launch it from Docker, a local build, or a downloaded Go binary. For an MCP client, use `npx -y telegram-archive-mcp` and configure the Telegram-Archive URL, username, and password as environment variables.

Set `TELEGRAM_ARCHIVE_URL`, `TELEGRAM_ARCHIVE_USER`, and `TELEGRAM_ARCHIVE_PASS`. The server uses these values to sign in to the archive through `/api/login` before handling MCP requests.

Yes, it works with Cursor through a stdio configuration. Add the server with `npx -y telegram-archive-mcp` as the command and provide the Telegram-Archive URL, viewer username, and viewer password in the environment.

Use its JSON-RPC endpoint at `/mcp` over HTTP. The listener uses loopback by default; set `MCP_AUTH_TOKEN` to add bearer authentication when exposing the endpoint beyond the local machine.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTelegram Archive MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/geiserx-telegram-archive-mcp?style=directory)](https://allmcps.com/mcp/geiserx-telegram-archive-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/geiserx-telegram-archive-mcp"><img src="https://allmcps.com/api/badge/geiserx-telegram-archive-mcp?style=directory" alt="Telegram Archive MCP on AllMCPs" /></a>