MCP server for Telegram Archive — search and browse Telegram chat history via the Model Context Protocol
MCP server for Telegram Archive — search and browse Telegram chat history via the Model Context Protocol. That is what the telegram archive mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
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.
The server publishes 11 tools. What each one is for:
Type — What forResources — Browse archive stats, chats, and folders read-onlyTools — Search and retrieve messages, inspect chat statisticsVariable — DefaultTELEGRAM_ARCHIVE_URL — http://localhost:3000TELEGRAM_ARCHIVE_USER — (empty)TELEGRAM_ARCHIVE_PASS — (empty)LISTEN_ADDR — 127.0.0.1:8080MCP_AUTH_TOKEN — (empty)TRANSPORT — (empty = HTTP)Project — DescriptionThe server ships on npm as telegram-archive-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Configuration is passed through the environment: TELEGRAM_ARCHIVE_URL, MCP_AUTH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Telegram Archive MCP's toolset — Type, Resources, Tools and 8 more — is a fair guide to whether it matches your workflow. It is maintained by geiserx; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Telegram Archive MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Type | What for |
| Resources | Browse archive stats, chats, and folders read-only |
| Tools | Search and retrieve messages, inspect chat statistics |
| Variable | Default |
| TELEGRAM_ARCHIVE_URL | http://localhost:3000 |
| TELEGRAM_ARCHIVE_USER | _(empty)_ |
| TELEGRAM_ARCHIVE_PASS | _(empty)_ |
| LISTEN_ADDR | 127.0.0.1:8080 |
| MCP_AUTH_TOKEN | _(empty)_ |
| TRANSPORT | _(empty = HTTP)_ |
| Project | Description |
{
"mcpServers": {
"telegram-archive": {
"command": "npx",
"args": ["-y", "telegram-archive-mcp"],
"env": {
"TELEGRAM_ARCHIVE_URL": "your-value",
"MCP_AUTH_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| TELEGRAM_ARCHIVE_URL | Endpoint or connection string the server talks to. | Yes |
| MCP_AUTH_TOKEN | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.