| FMRS | 50 / 100 · D | 70 / 100 · B |
|---|
| Reliability | 5 / 20 | 9 / 20 |
|---|
| Security and permissions | 10 / 20 | 16 / 20 |
|---|
| Maintenance | 13 / 20 | 14 / 20 |
|---|
| Documentation | 14 / 20 | 17 / 20 |
|---|
| Setup experience | 8 / 20 | 14 / 20 |
|---|
| Best for | - Users who want a desktop-grade AI agent that can directly operate local files, terminal, and browser workflows
- Users who want to remotely trigger desktop Agent tasks via WeChat, Feishu, DingTalk, Telegram, or similar IM channels
- Users needing office automation for documents, spreadsheets, slides, video, and web research
- Developers comfortable with Electron/React/TypeScript who want to build from source or use official installers
| - Developers who want to integrate Telegram into MCP clients like Claude
- Automation scenarios that need to manage multiple Telegram accounts
- Building custom Telegram bots or workflows
- Scenarios that require secure file operation path restrictions
|
|---|
| Not for | - Users who need an MCP server that a standard MCP client (e.g. Claude Desktop) can connect to directly — no such server manifest or tool definitions are provided in this repository
- Users needing a headless or server-side deployment — this project only ships as a macOS/Windows desktop application
- Users who want a narrow, single-purpose tool integration without granting broad file, terminal, and network permissions
| - Use cases requiring official Bot API features (this server uses a user client)
- Non-technical users who want a fully managed solution
- Multiple processes using the same session without lock management
|
|---|
| Required permissions | - Local file system read/write
- Terminal command execution
- Browser automation
- Network access
- IM channel binding and messaging (WeChat, WeCom, DingTalk, Feishu/Lark, QQ, Telegram, Discord, NetEase IM, NetEase Bee, POPO, email)
- Local SQLite storage (lobsterai.sqlite under Electron userData)
| - Requires Telegram API ID and API Hash
- Requires the user's Telegram session string (equivalent to account access)
- Can send messages, media, contacts, and settings to any allowed chat
- Can create or modify groups, channels, and chat settings
- Can access and operate on the user's media files and contacts
|
|---|
| Risks and side effects | - The app requires broad, sensitive permissions (file operations, terminal, network); the README notes sensitive actions are permission-gated and logged, but users must still review approval prompts carefully to avoid data loss or exposure
- Remote control via IM channels means commands can trigger desktop actions from linked messaging accounts — compromise of a bound account/channel could lead to unauthorized local execution
- Packaging bundles the OpenClaw runtime and, on Windows, a portable Python runtime, expanding the local attack surface
- This project is not maintained by the MCP protocol owner and is not a conventional MCP server; anyone wanting standard MCP-protocol integration should verify exposed behavior directly, as the source material gives no such details
| - Session string leakage could lead to account compromise
- Sending messages may raise privacy or security concerns
- Prompt injection: Telegram content may be maliciously crafted, so precautions are needed
- Risk of using unofficial PyPI package name; avoid pip install telegram-mcp
- Concurrent clients using the same session may cause AuthKeyDuplicatedError
|
|---|
| Supported clients | | Claude Desktop, Cursor, Claude Code, Codex |
|---|
| Tools | 0 | 76 |
|---|