GeiserX/telegram-archive-mcp
MCP Server for Telegram-Archive — search messages, browse chats, and access archived Telegram history via MCP
Platform-specific configuration:
{
"mcpServers": {
"telegram-archive-mcp": {
"command": "npx",
"args": [
"-y",
"telegram-archive-mcp"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
<h1 align="center">Telegram-Archive-MCP</h1>
<p align="center"> <a href="https://www.npmjs.com/package/telegram-archive-mcp"></a> <a href="https://hub.docker.com/r/drumsergio/telegram-archive-mcp"></a> <a href="https://github.com/GeiserX/telegram-archive-mcp/stargazers"></a> <a href="https://github.com/GeiserX/telegram-archive-mcp/blob/main/LICENSE"></a> </p>
<p align="center"><strong>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.</strong></p>
---
| Type | What for | MCP URI / Tool id | |---------------|----------------------------------------------------------------|----------------------------------| | Resources | Browse archive stats, chats, and folders read-only | telegram-archive://stats<br>telegram-archive://chats<br>telegram-archive://folders<br>telegram-archive://health | | Tools | Search and retrieve messages, inspect chat statistics | search_messages<br>get_messages<br>get_pinned_messages<br>get_messages_by_date<br>get_chat_stats<br>get_topics<br>refresh_stats |
Everything is exposed over a single JSON-RPC endpoint (/mcp). LLMs / Agents can: initialize -> readResource -> listTools -> callTool ... and so on.
---
Loading reviews...