{"id":"dryeab-mcp-telegram","name":"mcp-telegram","af_score":46.0,"security_score":50.5,"reliability_score":32.5,"what_it_does":"Provides an MCP server/CLI that connects LLM agents to Telegram via Telethon (MTProto), enabling sending/editing/deleting messages, searching dialogs, managing drafts, and downloading media through MCP tools.","best_when":"You need local/on-prem style Telegram access for an MCP-enabled agent and can run the CLI/MCP server securely with a dedicated session.","avoid_when":"You need OAuth-style app authorization, fine-grained per-tenant permissions, or a documented, standardized error contract for programmatic retries.","last_evaluated":"2026-03-30T13:35:58.874248+00:00","has_mcp":true,"has_api":false,"auth_methods":["Interactive login using Telegram API ID/hash + phone number + verification code (+ optional 2FA)","Session-file based authentication"],"has_free_tier":false,"known_gotchas":["Use of multiple concurrent mcp-telegram instances with the same session file can trigger Telethon SQLite 'database is locked' errors.","Authentication is interactive (login prompts) and relies on a locally stored session; agents will need pre-authenticated setup or scripted environment provisioning.","The README does not document tool parameter schemas or structured error codes, so robust agent-side handling may require inspection of runtime behavior."],"error_quality":0.0}