{"id":"dryeab-mcp-telegram","name":"mcp-telegram","homepage":"https://x.com/dryeab/status/1912187620131487999","repo_url":"https://github.com/dryeab/mcp-telegram","category":"communication","subcategories":[],"tags":["mcp","model-context-protocol","telegram","telethon","mtproto","messaging","python","ai-agents","tooling","cli"],"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.","use_cases":["Letting an AI assistant send messages to Telegram users/chats","AI-assisted moderation workflows (e.g., delete/edit messages) with human review","Retrieving and summarizing Telegram message history via search/history tools","Media retrieval workflows (download photos/videos/documents) for downstream analysis"],"not_for":["Automated bulk spam or abusive messaging","Use without understanding Telegram Terms of Service and user/device consent","Use where strong enterprise compliance/audit controls are required without additional hardening"],"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.","alternatives":["Telegram Bot API (server-side bots)","MTProto-based libraries (Telethon) directly in your own backend","Other MCP Telegram integrations (if available)","Using a bot + REST webhook pipeline instead of agent-controlled MTProto"],"af_score":46.0,"security_score":50.5,"reliability_score":32.5,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T13:35:58.874248+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Interactive login using Telegram API ID/hash + phone number + verification code (+ optional 2FA)","Session-file based authentication"],"oauth":false,"scopes":false,"notes":"Authentication is session-based (Telethon SQLite session). No OAuth or explicit scopes are documented; access is effectively governed by possession of the session/credential storage configured via env/session files."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided; it appears to be an open-source CLI package."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":46.0,"security_score":50.5,"reliability_score":32.5,"mcp_server_quality":62.0,"documentation_accuracy":72.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":55.0,"rate_limit_clarity":20.0,"tls_enforcement":70.0,"auth_strength":50.0,"scope_granularity":20.0,"dependency_hygiene":60.0,"secret_handling":55.0,"security_notes":"Uses Telegram MTProto via Telethon; transport security is expected over HTTPS/TCP, but the README does not explicitly state TLS requirements. Auth is based on Telegram API credentials plus a stored session file; no OAuth/scopes are documented, so access control is coarse. README warns to keep API credentials private and mentions stored session data. Multiple-instance use of the same session file may cause SQLite locking issues (reliability/security-adjacent operational concern). No security hardening (encryption of session file, audit logging, explicit redaction behavior) is documented in the provided text.","uptime_documented":0.0,"version_stability":55.0,"breaking_changes_history":40.0,"error_recovery":35.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_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."]}}