Skip to main content
Glama
ads-telegram-mcp

ads-telegram-mcp

by Draniev

Related Servers

Alternatives to ads-telegram-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      B
      maintenance
      Enables AI agents to create, target, pause, and read stats for Telegram Ads campaigns through ads.telegram.org using a logged-in session, with tools for managing ads, creatives, targeting, and account settings.
      26
      4
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to create, edit, and manage Telegram Ads campaigns by preparing structured ad packages, uploading media, committing changes, and reading account statistics through a Chrome extension bridge.
      4
      -
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that lets AI agents read and manage Telegram Ads campaigns, including listing accounts and ads, reading stats and budgets, and creating/updating ads, CPM, status, and budget by driving the real ads.telegram.org web UI through Playwright with a reused cookie-based login session.
      11
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to operate a Telegram account through the same commands as the terminal client: messaging, chat management, voice transcription, calls, stickers, and privacy settings.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control a personal Telegram account for sending/reading messages, media, group management, and more via the MTProto API.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides typed tools for ads.telegram.org, enabling login via Playwright and a read-only watcher through a local stdio MCP server.
      MIT

    TDQS

    A3.9/5.0

    Scored across 11 tools

    Disambiguation4/5

    Account tools (current, related, by-id) and ad tools (create, list, by-id) have clearly distinct purposes. The stats family is mostly separable, though get_ads_stats (per-ad totals for an arbitrary window) and get_account_report (per-ad totals for a calendar month) overlap in intent, and get_ads_stats vs get_ad_stats differ only by plural and require reading descriptions to distinguish.

    Naming Consistency4/5

    Names follow a consistent snake_case verb_noun convention (get_*, list_*, create_*, upload_*). The singular/plural shifts (get_ad_stats vs get_ads_stats, get_accounts_by_id vs get_current_account) are semantically meaningful but make the surface slightly less predictable at a glance.

    Tool Count5/5

    Eleven tools is well within a comfortable range for a domain covering accounts, ads, stats, reporting, and media. Each tool maps to a distinct resource/action, so none feels redundant padding.

    Completeness3/5

    Read and create paths are solid (accounts, ad listing, ad creation, several stats views, media upload), but there is no update/pause/delete or edit operation for ads, so the lifecycle dead-ends after creation. Targeting appears only as a read flag (return_target), with no way to modify it, which will force agents into workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues