Skip to main content
Glama
draiqw

tg-mcp

by draiqw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to tg-mcp

No user-submitted related servers found.

    Related Servers

    • Telegram MCP Server

      tolboy
      A
      license
      Not graded
      quality
      A
      maintenance
      A safe-by-default MCP server for real Telegram accounts powered by TDLib, enabling AI agents to read and act on your account with read-only mode and human approval for destructive actions.
      5
      Apache 2.0

    • tgmcp

      watzon
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that automates a single Telegram user account via the Telegram user API, enabling chat listing, reading/sending messages, searching, and additional actions through natural language.
      12
      MIT

    • mcp-telegram

      beautyfree
      A
      license
      B
      quality
      D
      maintenance
      A Telegram MCP server that connects agents to a real Telegram user account via MTProto, enabling reading, searching, sending, moderating, and managing Telegram chats through natural language or automated tool calls.
      100
      77
      29
      MIT

    • mcp-telegram

      Prgebish
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects AI assistants to your real Telegram account via User API (MTProto). Features default-deny ACL with per-chat permissions, message search, file sending, forwarding, media downloads, and rate limiting.
      3
      MIT

    • telegram-mcp-server

      Dmitrii-ive
      A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server that lets AI agents read personal Telegram chats from an allowlist of folders, with no send/edit/delete capability.
      33
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 79 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action, and the close pairs (tg_download vs tg_download_many, tg_pin vs tg_pin_message, tg_mute vs tg_notify, tg_unread vs tg_pending) are explicitly cross-referenced to draw their boundaries. Despite 79 tools, none would cause genuine misselection.

    Naming Consistency4/5

    All tools share the tg_ prefix and snake_case, and families are internally consistent (send_*, *_edit, *_info, *_batch). However, the verb/noun ordering flips between forms like tg_create_group and tg_topic_create, or tg_pin_message and tg_chat_edit, so parallel operations do not always share a pattern.

    Tool Count2/5

    79 tools far exceeds the 25+ 'too many' threshold and creates a heavy selection burden for an agent. The Telegram domain is genuinely broad and every tool has a distinct function, which keeps this from being an extreme mismatch, but the surface is far larger than typical MCP servers.

    Completeness5/5

    CRUD/lifecycle coverage is complete across messages, chats, drafts, scheduled messages, folders, topics and contacts, and every read tool feeds a documented follow-up (tg_media to tg_download_many, tg_topics to tg_history, tg_saved_tags to tg_search). Only niche operations like sharing a contact card or voting in a poll are absent, and none leave dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources