MCP Servers · Communication
GeiserX/telegram-archive-mcp
MCP Server for Telegram-Archive — search messages, browse chats, and access archived Telegram history via MCP
Our verdict
We have not reviewed GeiserX/telegram-archive-mcp yet
No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.
From the listing
About GeiserX/telegram-archive-mcp
GeiserX/telegram-archive-mcp is an MCP server written in Go that provides programmatic access to archived Telegram history. It allows searching messages and browsing chats through the Model Context Protocol, enabling AI agents to query Telegram archives.
Best for
Developers building AI tools that need to query archived Telegram data
Use cases
- Search messages in archived Telegram chats
- Browse chat history programmatically
- Integrate Telegram archive data with AI agents via MCP
Notes
4 stars on GitHub. Last updated 2026-05-27. Licensed GPL-3.0.
Pros
- Written in Go for good performance
- Open source with a permissive license
- Provides a standard MCP interface for AI tooling
Cons
- Low star count (4) indicates limited community adoption
- Requires a pre-existing Telegram Archive instance to function
- Documentation and examples may be sparse
Key facts
What we have checked
Not checked yet. Dated facts such as prices, releases and repository activity appear here once we have confirmed them from a source.
How to use
How to set it up
As the listing publishes it. We have not run this install.
Install
npx telegram-archive-mcpTools exposed
TELEGRAM_ARCHIVE_URLTELEGRAM_ARCHIVE_USERTELEGRAM_ARCHIVE_PASSLISTEN_ADDRMCP_AUTH_TOKEN
Clients the listing names (not checked here)
Cursor
Install
Add GeiserX/telegram-archive-mcp to your client
Our lab has not run this server yet. "Config checked" on a client means the recipe matches that client's documented config format; it does not mean we ran it.
Claude Code
Config checkedRun in your terminal (runs on your computer)
claude mcp add --env TELEGRAM_ARCHIVE_URL=YOUR_TELEGRAM_ARCHIVE_URL --transport stdio geiserx-telegram-archive-mcp -- npx -y telegram-archive-mcp@0.3.1Needs TELEGRAM_ARCHIVE_URL: replace each YOUR_ value with your own.
Claude Desktop
Config checkedAdd to claude_desktop_config.json (runs on your computer)
{
"mcpServers": {
"geiserx-telegram-archive-mcp": {
"command": "npx",
"args": [
"-y",
"telegram-archive-mcp@0.3.1"
],
"env": {
"TELEGRAM_ARCHIVE_URL": "YOUR_TELEGRAM_ARCHIVE_URL"
}
}
}
}Needs TELEGRAM_ARCHIVE_URL: replace each YOUR_ value with your own.
Cursor
Config checkedAdd to .cursor/mcp.json (runs on your computer)
{
"mcpServers": {
"geiserx-telegram-archive-mcp": {
"command": "npx",
"args": [
"-y",
"telegram-archive-mcp@0.3.1"
],
"env": {
"TELEGRAM_ARCHIVE_URL": "YOUR_TELEGRAM_ARCHIVE_URL"
}
}
}
}Needs TELEGRAM_ARCHIVE_URL: replace each YOUR_ value with your own.
VS Code
Config checkedAdd to .vscode/mcp.json (runs on your computer)
{
"inputs": [
{
"type": "promptString",
"id": "telegram-archive-url",
"description": "Telegram Archive instance URL (e.g. http://localhost:8000)",
"password": true
}
],
"servers": {
"geiserx-telegram-archive-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"telegram-archive-mcp@0.3.1"
],
"env": {
"TELEGRAM_ARCHIVE_URL": "${input:telegram-archive-url}"
}
}
}
}Needs TELEGRAM_ARCHIVE_URL: replace each YOUR_ value with your own.
Codex
Config checkedAdd to ~/.codex/config.toml (runs on your computer)
[mcp_servers.geiserx-telegram-archive-mcp]
command = "npx"
args = ["-y", "telegram-archive-mcp@0.3.1"]
env_vars = ["TELEGRAM_ARCHIVE_URL"]Needs TELEGRAM_ARCHIVE_URL: replace each YOUR_ value with your own.
- ChatGPT: ChatGPT connects only to remote servers that need no API key.
Recipes come from the server's entry in the official MCP registry. Check the package name before you run it, and keep keys out of shared files.
Works with
What GeiserX/telegram-archive-mcp connects to
5 clients, each with how we know and when we checked.
| Works with | Type | How we know | Checked |
|---|---|---|---|
| Claude Code | Client | Install recipe matches the client's documented formatRuns locally, version 0.3.1Config checked | Claude Code docs |
| Claude Desktop | Client | Install recipe matches the client's documented formatRuns locally, version 0.3.1Config checked | Claude Desktop docs |
| Cursor | Client | Install recipe matches the client's documented formatRuns locally, version 0.3.1Config checked | Cursor docs |
| VS Code | Client | Install recipe matches the client's documented formatRuns locally, version 0.3.1Config checked | VS Code docs |
| Codex | Client | Install recipe matches the client's documented formatRuns locally, version 0.3.1Config checked | Codex docs |
Sources
Where this comes from
No sources recorded yet. Each source we check is listed here with the date we checked it.
A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.
Changelog
What changed
No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.