| FMRS | 74 / 100 · B | 72 / 100 · B | 70 / 100 · B |
|---|
| Reliability | 11 / 20 | 10 / 20 | 9 / 20 |
|---|
| Security and permissions | 15 / 20 | 15 / 20 | 16 / 20 |
|---|
| Maintenance | 17 / 20 | 16 / 20 | 14 / 20 |
|---|
| Documentation | 17 / 20 | 17 / 20 | 17 / 20 |
|---|
| Setup experience | 14 / 20 | 14 / 20 | 14 / 20 |
|---|
| Best for | - Developers needing quick, API-key-free web search capabilities
- Privacy-conscious users who prefer local search execution
- AI application development with Claude Desktop or Claude Code
| - Privacy-conscious developers who want local data storage.
- Researchers who need AI-assisted management of large note collections.
- Users of Markdown editors like Obsidian.
| - 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 | - Enterprise applications requiring high-scale, reliable search APIs
- Users needing advanced search features like custom ranking or filters
- Accessing sites blocked by TLS fingerprinting without installing the optional browser backend
| - Users needing cloud sync and mobile access (unless using the paid cloud service).
- Minimalists who want zero configuration.
- Scenarios requiring large-scale vector databases and complex retrieval (local SQLite may be insufficient).
| - 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 | - Outbound network access to DuckDuckGo and other websites
- Reads environment variables for SafeSearch, region, and CA certificates
- Optionally reads a CA certificate file (for TLS-intercepting proxies)
| - Read and write to the local filesystem (default: ~/basic-memory).
- Perform file and directory operations (create, edit, delete).
- Access local SQLite database (or Postgres/Milvus if configured).
| - 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 | - Search endpoints may occasionally return empty results or errors, especially when blocked
- Content fetching may be subject to SSRF protection, blocking private or loopback addresses by default
- Misuse could lead to rate limiting or IP blocking
| - Tools have write operations that may unintentionally modify or delete notes.
- Edit operations may overwrite existing content, though there are protections.
- Semantic search and reranking features may require model downloads, adding latency.
- Local data backups are the user's responsibility.
| - 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, Claude Code | Claude Desktop, Claude Code, Codex CLI, Cursor, VS Code, ChatGPT, Obsidian | Claude Desktop, Cursor, Claude Code, Codex |
|---|
| Tools | 2 | 21 | 76 |
|---|