What transport protocols does the server support?

It supports HTTP transport by default and can be configured to use stdio transport.

How do I secure access to the MCP server?

By default, it listens on localhost. To expose on a network, use a reverse proxy with authentication and set MCP_AUTH_TOKEN for bearer token auth.

What endpoints or tools are available?

Resources include stats, chats, folders, and health; tools include search_messages, get_messages, get_pinned_messages, get_messages_by_date, get_chat_stats, get_topics, and refresh_stats.

Is there a Docker image available?

Yes, an official Docker image is published and can be used with environment variables for configuration.

Telegram Archive MCP

Go-based MCP server to search, browse, and retrieve messages from a Telegram-Archive instance via JSON-RPC.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "geiserx-telegram-archive-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "telegram-archive-mcp"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Overview

This MCP server exposes a Telegram-Archive instance as an MCP endpoint, enabling language models and agents to access archived Telegram chat history. It supports browsing chats, folders, and archive statistics, as well as full-text message search and retrieval. The server communicates over a single JSON-RPC endpoint and can be run via Docker or npm with configurable authentication and transport options.

Use cases

Search Telegram messages with full-text queries

Browse archived Telegram chats and folders

Retrieve messages by chat, date, or pinned status

Inspect chat and archive statistics

Integrate Telegram archive data into AI agent workflows

Key features

Full-text search of Telegram messages

Read-only browsing of chats, folders, and stats

Multiple message retrieval tools (by date, pinned, chat)

Single JSON-RPC endpoint for all interactions

Supports HTTP and stdio transports

Docker image and npm package available for deployment

Capabilities & Tool Schemas

Inspect callable tools, capabilities, and parameters exposed to AI agents by Telegram Archive MCP.

Extracted Tool Capabilities

Full-text search of Telegram messages

Read-only browsing of chats, folders, and stats

Multiple message retrieval tools (by date, pinned, chat)

Single JSON-RPC endpoint for all interactions

Supports HTTP and stdio transports

Docker image and npm package available for deployment

Documentation Overview

Telegram-Archive-MCP

A tiny bridge that exposes any Telegram-Archive instance as an MCP server, enabling LLMs to search messages, browse chats, and access archived Telegram history.

What you get

Type	What for	MCP URI / Tool id
Resources	Browse archive stats, chats, and folders read-only	`telegram-archive://stats` `telegram-archive://chats` `telegram-archive://folders` `telegram-archive://health`
Tools	Search and retrieve messages (offset or keyset cursor paging; whole calendar days in a timezone), inspect chat statistics	`search_messages` `get_messages` `get_pinned_messages` `get_messages_by_date` `get_chat_stats` `get_topics` `refresh_stats`

Everything is exposed over a single JSON-RPC endpoint (/mcp). LLMs / Agents can: initialize -> readResource -> listTools -> callTool ... and so on.

Quick-start (Docker Compose)

docker-compose.yml

services:
  telegram-archive-mcp:
    image: drumsergio/telegram-archive-mcp:latest
    ports:
      - "127.0.0.1:8080:8080"
    environment:
      - TELEGRAM_ARCHIVE_URL=http://telegram-archive:3000
      - TELEGRAM_ARCHIVE_USER=your-username
      - TELEGRAM_ARCHIVE_PASS=your-password

Security note: The HTTP transport listens on 127.0.0.1:8080 by default. If you need to expose it on a network, place it behind a reverse proxy with authentication.

Install via npm (stdio transport)

Terminal

npx telegram-archive-mcp

Or install globally:

Terminal

npm install -g telegram-archive-mcp
telegram-archive-mcp

This downloads the pre-built Go binary from GitHub Releases for your platform and runs it with stdio transport. Requires at least one published release.

Local build

git clone https://github.com/GeiserX/telegram-archive-mcp
cd telegram-archive-mcp

# (optional) create .env from the sample
cp .env.example .env && $EDITOR .env

go run ./cmd/server

Configuration

Variable	Default	Description
`TELEGRAM_ARCHIVE_URL`	`http://localhost:3000`	Telegram-Archive instance URL (without trailing /)
`TELEGRAM_ARCHIVE_USER`	(empty)	Login username for session auth via `/api/login`
`TELEGRAM_ARCHIVE_PASS`	(empty)	Login password for session auth via `/api/login`
`LISTEN_ADDR`	`127.0.0.1:8080`	HTTP listen address (Docker sets `0.0.0.0:8080`)
`MCP_AUTH_TOKEN`	(empty)	Bearer token for HTTP auth (required if not loopback)
`TRANSPORT`	(empty = HTTP)	Set to `stdio` for stdio transport

Put them in a .env file (from .env.example) or set them in the environment.

Testing

Tested with Inspector and it is currently fully working. Before making a PR, make sure this MCP server behaves well via this medium.

Example configuration for client LLMs

config.json

{
  "schema_version": "v1",
  "name_for_human": "Telegram-Archive-MCP",
  "name_for_model": "telegram_archive_mcp",
  "description_for_human": "Search messages, browse chats, and access archived Telegram history.",
  "description_for_model": "Interact with a Telegram-Archive instance that stores archived Telegram messages. First call initialize, then reuse the returned session id in header \"Mcp-Session-Id\" for every other call. Use readResource to fetch URIs that begin with telegram-archive://. Use listTools to discover available actions and callTool to execute them.",
  "auth": {
    "type": "bearer",
    "token": "<your MCP_AUTH_TOKEN value>"
  },
  "api": {
    "type": "jsonrpc-mcp",
    "url":  "http://localhost:8080/mcp",
    "init_method": "initialize",
    "session_header": "Mcp-Session-Id"
  },
  "contact_email": "acsdesk@protonmail.com",
  "legal_info_url": "https://github.com/GeiserX/telegram-archive-mcp/blob/main/LICENSE"
}

Credits

Telegram-Archive -- Telegram message archival and search

MCP-GO -- modern MCP implementation

GoReleaser -- painless multi-arch releases

Maintainers

@GeiserX.

Contributing

Feel free to dive in! Open an issue or submit PRs.

Telegram-Archive-MCP follows the Contributor Covenant Code of Conduct.

Other MCP Servers by GeiserX

cashpilot-mcp — Passive income monitoring
duplicacy-mcp — Backup health monitoring
genieacs-mcp — TR-069 device management
lynxprompt-mcp — AI configuration blueprints
pumperly-mcp — Fuel and EV charging prices

Related Projects

Project	Description
Telegram-Archive	Automated, incremental Telegram backups with a local web viewer
telegram-delay-channel-cloner	Telegram bot that relays messages between channels with configurable delay
telegram-slskd-local-bot	Automated music discovery and download via Telegram bot with Soulseek
paperless-telegram-bot	Manage Paperless-NGX documents entirely through Telegram
n8n-nodes-telegram-archive	n8n community node for Telegram-Archive

Read the full README →View source on GitHub →

Related MCP Servers

View all in Communication View all alternatives

Adoption & maintenance

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

GitHub stars

Stargazers on the source repository.

npm downloads

225

Package downloads in the last 30 days.

Last commit

1mo ago

Most recent push to the default branch.

Reviews

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

Frequently Asked Questions about Telegram Archive MCP

It uses session authentication via username and password configured with TELEGRAM_ARCHIVE_USER and TELEGRAM_ARCHIVE_PASS environment variables.

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 Preview

Telegram 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>

Technical Specs & Signals

CategoryCommunication

51Quality signal: Good · 51/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools22/30

Adoption & activity6/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

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

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💬 Communication →Best MCP servers for Slack & Communication →Alternatives to Telegram Archive MCP →Install in Claude Desktop Install in Cursor Install in VS Code

Telegram Archive MCP

Go-based MCP server to search, browse, and retrieve messages from a Telegram-Archive instance via JSON-RPC.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "geiserx-telegram-archive-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "telegram-archive-mcp"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Overview

Use cases

Search Telegram messages with full-text queries

Browse archived Telegram chats and folders

Retrieve messages by chat, date, or pinned status

Inspect chat and archive statistics

Integrate Telegram archive data into AI agent workflows

Key features

Full-text search of Telegram messages

Read-only browsing of chats, folders, and stats

Multiple message retrieval tools (by date, pinned, chat)

Single JSON-RPC endpoint for all interactions

Supports HTTP and stdio transports

Docker image and npm package available for deployment

Capabilities & Tool Schemas

Inspect callable tools, capabilities, and parameters exposed to AI agents by Telegram Archive MCP.

Extracted Tool Capabilities

Full-text search of Telegram messages

Read-only browsing of chats, folders, and stats

Multiple message retrieval tools (by date, pinned, chat)

Single JSON-RPC endpoint for all interactions

Supports HTTP and stdio transports

Docker image and npm package available for deployment

Documentation Overview

Telegram-Archive-MCP

A tiny bridge that exposes any Telegram-Archive instance as an MCP server, enabling LLMs to search messages, browse chats, and access archived Telegram history.

What you get

Type	What for	MCP URI / Tool id
Resources	Browse archive stats, chats, and folders read-only	`telegram-archive://stats` `telegram-archive://chats` `telegram-archive://folders` `telegram-archive://health`
Tools	Search and retrieve messages (offset or keyset cursor paging; whole calendar days in a timezone), inspect chat statistics	`search_messages` `get_messages` `get_pinned_messages` `get_messages_by_date` `get_chat_stats` `get_topics` `refresh_stats`

Everything is exposed over a single JSON-RPC endpoint (/mcp). LLMs / Agents can: initialize -> readResource -> listTools -> callTool ... and so on.

Quick-start (Docker Compose)

docker-compose.yml

services:
  telegram-archive-mcp:
    image: drumsergio/telegram-archive-mcp:latest
    ports:
      - "127.0.0.1:8080:8080"
    environment:
      - TELEGRAM_ARCHIVE_URL=http://telegram-archive:3000
      - TELEGRAM_ARCHIVE_USER=your-username
      - TELEGRAM_ARCHIVE_PASS=your-password

Security note: The HTTP transport listens on 127.0.0.1:8080 by default. If you need to expose it on a network, place it behind a reverse proxy with authentication.

Install via npm (stdio transport)

Terminal

npx telegram-archive-mcp

Or install globally:

Terminal

npm install -g telegram-archive-mcp
telegram-archive-mcp

This downloads the pre-built Go binary from GitHub Releases for your platform and runs it with stdio transport. Requires at least one published release.

Local build

git clone https://github.com/GeiserX/telegram-archive-mcp
cd telegram-archive-mcp

# (optional) create .env from the sample
cp .env.example .env && $EDITOR .env

go run ./cmd/server

Configuration

Variable	Default	Description
`TELEGRAM_ARCHIVE_URL`	`http://localhost:3000`	Telegram-Archive instance URL (without trailing /)
`TELEGRAM_ARCHIVE_USER`	(empty)	Login username for session auth via `/api/login`
`TELEGRAM_ARCHIVE_PASS`	(empty)	Login password for session auth via `/api/login`
`LISTEN_ADDR`	`127.0.0.1:8080`	HTTP listen address (Docker sets `0.0.0.0:8080`)
`MCP_AUTH_TOKEN`	(empty)	Bearer token for HTTP auth (required if not loopback)
`TRANSPORT`	(empty = HTTP)	Set to `stdio` for stdio transport

Put them in a .env file (from .env.example) or set them in the environment.

Testing

Tested with Inspector and it is currently fully working. Before making a PR, make sure this MCP server behaves well via this medium.

Example configuration for client LLMs

config.json

{
  "schema_version": "v1",
  "name_for_human": "Telegram-Archive-MCP",
  "name_for_model": "telegram_archive_mcp",
  "description_for_human": "Search messages, browse chats, and access archived Telegram history.",
  "description_for_model": "Interact with a Telegram-Archive instance that stores archived Telegram messages. First call initialize, then reuse the returned session id in header \"Mcp-Session-Id\" for every other call. Use readResource to fetch URIs that begin with telegram-archive://. Use listTools to discover available actions and callTool to execute them.",
  "auth": {
    "type": "bearer",
    "token": "<your MCP_AUTH_TOKEN value>"
  },
  "api": {
    "type": "jsonrpc-mcp",
    "url":  "http://localhost:8080/mcp",
    "init_method": "initialize",
    "session_header": "Mcp-Session-Id"
  },
  "contact_email": "acsdesk@protonmail.com",
  "legal_info_url": "https://github.com/GeiserX/telegram-archive-mcp/blob/main/LICENSE"
}

Credits

Telegram-Archive -- Telegram message archival and search

MCP-GO -- modern MCP implementation

GoReleaser -- painless multi-arch releases

Maintainers

@GeiserX.

Contributing

Feel free to dive in! Open an issue or submit PRs.

Telegram-Archive-MCP follows the Contributor Covenant Code of Conduct.

Other MCP Servers by GeiserX

cashpilot-mcp — Passive income monitoring
duplicacy-mcp — Backup health monitoring
genieacs-mcp — TR-069 device management
lynxprompt-mcp — AI configuration blueprints
pumperly-mcp — Fuel and EV charging prices

Related Projects

Project	Description
Telegram-Archive	Automated, incremental Telegram backups with a local web viewer
telegram-delay-channel-cloner	Telegram bot that relays messages between channels with configurable delay
telegram-slskd-local-bot	Automated music discovery and download via Telegram bot with Soulseek
paperless-telegram-bot	Manage Paperless-NGX documents entirely through Telegram
n8n-nodes-telegram-archive	n8n community node for Telegram-Archive

Read the full README →View source on GitHub →

Related MCP Servers

View all in Communication View all alternatives

Adoption & maintenance

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

GitHub stars

Stargazers on the source repository.

npm downloads

225

Package downloads in the last 30 days.

Last commit

1mo ago

Most recent push to the default branch.

Reviews

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

Frequently Asked Questions about Telegram Archive MCP

It uses session authentication via username and password configured with TELEGRAM_ARCHIVE_USER and TELEGRAM_ARCHIVE_PASS environment variables.

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 Preview

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>

Technical Specs & Signals

CategoryCommunication

51Quality signal: Good · 51/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools22/30

Adoption & activity6/15

Community engagement0/10

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

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

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💬 Communication →Best MCP servers for Slack & Communication →Alternatives to Telegram Archive MCP →Install in Claude Desktop Install in Cursor Install in VS Code