| FMRS | 51 / 100 · D | 74 / 100 · B | 72 / 100 · B |
|---|
| Reliability | 8 / 20 | 11 / 20 | 10 / 20 |
|---|
| Security and permissions | 11 / 20 | 15 / 20 | 15 / 20 |
|---|
| Maintenance | 8 / 20 | 17 / 20 | 16 / 20 |
|---|
| Documentation | 11 / 20 | 17 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 14 / 20 | 14 / 20 |
|---|
| Best for | - LLM-driven Telegram bot development where natural-language prompts trigger Bot API calls.
- Integrations requiring a comprehensive, validated set of Telegram Bot API methods.
- Longer AI conversations where meta-mode reduces context token consumption.
- Projects needing built-in rate limiting and fault tolerance in Bot API calls.
| - 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.
|
|---|
| Not for | - Users not working with Telegram or without Telegram bot needs.
- Users needing SSE or HTTP transport, as this server supports only stdio.
- Those wanting an officially maintained MCP server; this is a community implementation.
- Edge-case use cases that require no external dependencies and full official support.
| - 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).
|
|---|
| Required permissions | - Full access to the Telegram Bot API tied to the provided token.
- Ability to send and receive messages, files, and media in chats, groups, and channels where the bot is a member.
- The server communicates only with `api.telegram.org`; no other external network calls are made.
- The token is masked and never exposed in responses or error messages.
| - 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).
|
|---|
| Risks and side effects | - Token leakage could lead to misuse of the bot account.
- Potential security risks if file uploads are exposed in untrusted environments.
- Rate limiting and circuit breaker behaviors may interact unusually under load.
- The server's code and content may contain bugs, with no official support.
| - 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.
|
|---|
| Supported clients | Claude Desktop | Claude Desktop, Claude Code | Claude Desktop, Claude Code, Codex CLI, Cursor, VS Code, ChatGPT, Obsidian |
|---|
| Tools | 30 | 2 | 21 |
|---|