{"id":"sparfenyuk-mcp-telegram","name":"mcp-telegram","homepage":null,"repo_url":"https://github.com/sparfenyuk/mcp-telegram","category":"communication","subcategories":[],"tags":["mcp","telegram","telethon","python","ai-assistant-integration","messaging"],"what_it_does":"An MCP (Model Context Protocol) server that provides read-only access to the Telegram API (via MTProto/Telethon), exposing tools for listing dialogs (chats/channels/groups) and fetching unread messages from a given dialog.","use_cases":["Summarizing unread Telegram messages for an AI assistant","Reviewing message context from specific chats/channels/groups","Building workflows that periodically scan unread messages and generate digests"],"not_for":["Writing/modifying Telegram data (e.g., marking chats as read, drafting/sending messages)","Downloading media files (not implemented as of README)","Retrieving historical messages by date/time (not implemented as of README)","Compliance-sensitive deployments that require strong assurances about data handling and retention (README provides limited details)"],"best_when":"You want an AI assistant to read and summarize unread Telegram messages from your own account, and you control the runtime environment where the MCP server stores/authenticates with Telegram.","avoid_when":"You need full Telegram functionality (read/unread state changes, message history search, media downloads) or you require clearly documented operational guarantees (rate limits, retries/idempotency semantics, and security posture).","alternatives":["Direct Telegram client/API integration (Telethon) in your own application","Other MCP servers/sources that expose messaging/email functionality (if available in your ecosystem)","Telegram Bots API (if your use case can be implemented with bot capabilities rather than MTProto)"],"af_score":42.8,"security_score":57.8,"reliability_score":28.8,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T13:39:42.361214+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":["Telegram MTProto sign-in using API ID/hash and user phone-number verification code (CLI command: mcp-telegram sign-in)","Environment variables in client runtime (TELEGRAM_API_ID, TELEGRAM_API_HASH) for Claude Desktop/Inspector usage"],"oauth":false,"scopes":false,"notes":"Auth is tied to Telegram user session/MTProto access rather than app-bot permissions. README warns that API hash is secret and should not be posted. No fine-grained permission/scopes concept is documented at the MCP layer."},"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 is provided; this appears to be an open-source tool where costs are primarily your Telegram API/usage and hosting/runtime."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":42.8,"security_score":57.8,"reliability_score":28.8,"mcp_server_quality":55.0,"documentation_accuracy":55.0,"error_message_quality":0.0,"error_message_notes":"README only mentions one generic connection troubleshooting message (\"Could not connect to MCP server mcp-telegram\"). No examples of MCP error payloads or tool-level error codes are provided in the README excerpt.","auth_complexity":45.0,"rate_limit_clarity":10.0,"tls_enforcement":80.0,"auth_strength":70.0,"scope_granularity":20.0,"dependency_hygiene":55.0,"secret_handling":60.0,"security_notes":"Uses Telegram MTProto authentication (API ID/hash + user sign-in code). README advises not to post the API hash. However, the excerpt provides limited details about local session storage, secret persistence/rotation, audit logs, and how tool outputs might be handled. No MCP-level fine-grained scope model is documented; access effectively maps to the user's Telegram data access.","uptime_documented":0.0,"version_stability":40.0,"breaking_changes_history":50.0,"error_recovery":25.0,"idempotency_support":"false","idempotency_notes":"Operations described are read-only, but the README does not document idempotency semantics for each tool call or how retries behave under transient failures.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["MCP server connectivity failures may occur if Claude Desktop is misconfigured (including uv binary path).","Environment variables TELEGRAM_API_ID / TELEGRAM_API_HASH must be set in the MCP runtime (e.g., Inspector).","Server is read-only as of README; some expected Telegram actions are not implemented."]}}