What is io.github.GeiserX/telegram-archive-mcp?

MCP server for Telegram Archive — search messages, browse chats, and access history

How do I install io.github.GeiserX/telegram-archive-mcp?

Clone io.github.GeiserX/telegram-archive-mcp from https://github.com/GeiserX/telegram-archive-mcp and configure it as an MCP server in your client (Claude Desktop, Cursor, or VS Code).

Is io.github.GeiserX/telegram-archive-mcp open source?

Yes, io.github.GeiserX/telegram-archive-mcp is open source under the GPL-3.0 license. Source code is available at https://github.com/GeiserX/telegram-archive-mcp.

What category does io.github.GeiserX/telegram-archive-mcp belong to?

io.github.GeiserX/telegram-archive-mcp is listed under Developer Tools MCP servers on MCPFind.

io.github.GeiserX/telegram-archive-mcp — MCP Server for Developer Tools

Features

Read-only resources for archive stats, chats, folders and health (telegram-archive://stats, telegram-archive://chats).
Message search, message paging by offset or keyset cursor, and whole calendar days in a timezone (get_messages_by_date).
Pinned messages, forum topics and per-chat statistics.
Signs in to Telegram-Archive through /api/login with TELEGRAM_ARCHIVE_USER and TELEGRAM_ARCHIVE_PASS.
One JSON-RPC endpoint (/mcp) over HTTP, or stdio with TRANSPORT=stdio.
Listens on loopback by default; MCP_AUTH_TOKEN adds bearer auth when you expose it.
Ships as a Docker image, an npm package (npx telegram-archive-mcp) and multi-arch Go binaries.

Quick start

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.

Documentation

The full documentation is at geiserx.github.io/telegram-archive-mcp.

Getting started: npm, Docker Compose, local build
Configuration: environment variables and client configuration
Usage: the 4 resources and 9 tools, paging, reading one day at a time
Development: testing, contributing, credits
Related projects: Telegram Archive, other MCP servers, where this one is listed

License

GPL-3.0-or-later

Set up in your AI client

AI clientOperating system

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json

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

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Compatible MCP Clients

io.github.GeiserX/telegram-archive-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.

Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.

VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.

Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.

Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

io.github.GeiserX/telegram-archive-mcp