{
  "name": "Multi-account Telegram MCP comparison matrix, 2026",
  "description": "The row-level evidence matrix behind Entergram's 2026 comparison of Telegram MCP options for multiple accounts.",
  "methodology": "Options are ordered by the fit described in the guide, not by a universal numeric score. Account-routing models, best-fit summaries and trade-offs were checked against official product pages or project repositories. No vendor paid for placement.",
  "checked_on": "2026-08-30",
  "guide_url": "https://www.entergram.com/blog/best-telegram-mcp-multiple-accounts-2026",
  "columns": ["rank", "option", "category", "best_for", "connection_or_account_model", "primary_tradeoff", "official_source", "source_type", "checked_on"],
  "rows": [
    {"rank": 1, "option": "Entergram", "category": "Hosted unified router", "best_for": "Business teams, sales and support", "connection_or_account_model": "Several real accounts behind one endpoint with stable account IDs", "primary_tradeoff": "Paid seat and workspace model may be more structure than a solo user needs", "official_source": "https://www.entergram.com/telegram-mcp", "source_type": "vendor-page", "checked_on": "2026-08-30"},
    {"rank": 2, "option": "TeleBoost", "category": "Hosted workspace router", "best_for": "Outreach teams and campaigns", "connection_or_account_model": "Shared account and workspace context behind one hosted endpoint", "primary_tradeoff": "Shared team operation requires the Business plan", "official_source": "https://teleboost.app/telegram-mcp", "source_type": "vendor-page", "checked_on": "2026-08-30"},
    {"rank": 3, "option": "tolboy/telegram-mcp-tdlib", "category": "Isolated self-hosted router", "best_for": "Production-oriented internal platforms", "connection_or_account_model": "Independent TDLib state with mandatory account selection", "primary_tradeoff": "Heavier service to deploy and monitor", "official_source": "https://github.com/tolboy/telegram-mcp-tdlib", "source_type": "repository", "checked_on": "2026-08-30"},
    {"rank": 4, "option": "chigwell/telegram-mcp", "category": "Broad self-hosted router", "best_for": "Developers needing broad Telegram control", "connection_or_account_model": "Labelled sessions with account-aware writes", "primary_tradeoff": "Operator owns powerful sessions, hosting and incident response", "official_source": "https://github.com/chigwell/telegram-mcp", "source_type": "repository", "checked_on": "2026-08-30"},
    {"rank": 5, "option": "mcp-telegram/mcp-telegram", "category": "Named-instance pattern", "best_for": "Two or three clearly separated accounts", "connection_or_account_model": "Separate session path and MCP entry per account", "primary_tradeoff": "No unified account router", "official_source": "https://github.com/mcp-telegram/mcp-telegram", "source_type": "repository", "checked_on": "2026-08-30"},
    {"rank": 6, "option": "DmitryKhali/telegram-mcp", "category": "Keyring-isolated instances", "best_for": "Small safety-first personal setups", "connection_or_account_model": "Separate keyring namespace and server process per account", "primary_tradeoff": "Client naming and orchestration become part of the safety boundary", "official_source": "https://github.com/DmitryKhali/telegram-mcp", "source_type": "repository", "checked_on": "2026-08-30"},
    {"rank": 7, "option": "dataz.md", "category": "Hosted read-only profiles", "best_for": "Read-only cross-account research", "connection_or_account_model": "Separate profile or hosted VM per provider account", "primary_tradeoff": "Not a unified cross-account write router", "official_source": "https://dataz.md/", "source_type": "vendor-page", "checked_on": "2026-08-30"}
  ]
}