convez.ai
MCP ServerIntegração & APIsIntermediário
GeiserX

Telegram Archive MCP

GeiserX/telegram-archive-mcp

Bridge MCP para buscar e navegar histórico Telegram arquivado

Ver no GitHub
BomPluginScore · de 0 a 100

Servidor MCP que expõe uma instância Telegram-Archive, permitindo que LLMs busquem mensagens, naveguem chats e acessem histórico arquivado via protocolo MCP. Implementado em Go com suporte a Docker e recursos read-only de estatísticas e pastas.

Instalação

$npx convez-ai GeiserX/telegram-archive-mcp

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
15
Forks
2
Acompanhando
1
Saúde
57%
Último commit
há 1 semana
Versão
v0.4.2
Issues abertas
0
Contribuidores
2

Casos de uso

  • Pesquisa e recuperação de mensagens em histórico Telegram arquivado
  • Análise de estatísticas de chats e tópicos via LLMs
  • Navegação de pastas e estrutura de arquivo de forma automatizada

Veredito

Ferramenta bem-mantida e listada em registros oficiais MCP. Útil para integrar histórico Telegram com agentes IA, mas requer instância Telegram-Archive prévia configurada e conhecimento de MCP.

README

A tradução para o português deste README ainda está na fila.


What you get

TypeWhat forMCP URI / Tool id
ResourcesBrowse archive stats, chats, and folders read-onlytelegram-archive://statstelegram-archive://chatstelegram-archive://folderstelegram-archive://health
ToolsSearch and retrieve messages, inspect chat statisticssearch_messagesget_messagesget_pinned_messagesget_messages_by_dateget_chat_statsget_topicsrefresh_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)

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)

npx telegram-archive-mcp

Or install globally:

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

VariableDefaultDescription
TELEGRAM_ARCHIVE_URLhttp://localhost:3000Telegram-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_ADDR127.0.0.1:8080HTTP 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

{
  "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

Related Projects

ProjectDescription
Telegram-ArchiveAutomated, incremental Telegram backups with a local web viewer
telegram-delay-channel-clonerTelegram bot that relays messages between channels with configurable delay
telegram-slskd-local-botAutomated music discovery and download via Telegram bot with Soulseek
paperless-telegram-botManage Paperless-NGX documents entirely through Telegram
n8n-nodes-telegram-archiven8n community node for Telegram-Archive
Ver o original no GitHub

Bom para

Relacionados