Skip to main content
Glama
vkruglikov

telegram-mcp

by vkruglikov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to telegram-mcp

No user-submitted related servers found.

    Related Servers

    • telegram-mcp-http

      mrvolkomorov
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables users to interact with their own Telegram account through MTProto, supporting chat listing, message reading and searching, sending messages, and fetching contacts via MCP tools.
      -

    • telegram-mcp

      bssth
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to operate a Telegram account as a userbot, providing tools for reading and sending messages, searching chats and contacts, managing media, and performing other account actions via MTProto with a locally encrypted session.
      28
      MIT

    • codex-telegram

      briejhxh
      A
      license
      A
      quality
      C
      maintenance
      Enables local, privacy-first control of a personal Telegram account through MCP, using TDLib to read chats, send and reply to messages, search, transfer files, and interact with approved inline buttons.
      20
      MIT

    • telegram-mcp

      draiqw
      F
      license
      B
      quality
      B
      maintenance
      Provides full access to a personal Telegram account via MTProto, enabling MCP clients to read chats, send messages, manage media, and more.
      70
      -

    • Telegram MCP Server

      KiaroSama
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to drive a real Telegram account, exposing chats, messages, media, secret chats, admin rights, invite links, Mini Apps, and multi-account routing as callable tools.
      8
      GPL 3.0

    • Telegram Userbot MCP Server

      sdaveas
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables an agent to drive your own Telegram account over MTProto without a browser, listing and searching chats, reading history, sending messages, media and stickers, reacting to and forwarding messages. It performs no summarising or decision-making itself, acting purely as transport that an MCP client controls.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool has a distinct purpose: account identity, chat listing/searching by scope, messaging, file/media operations, read status, and style profiling. No two tools overlap in function; searching is divided by scope (own chats, public channels, public posts) to avoid ambiguity.

    Naming Consistency4/5

    Most tools follow verb_noun snake_case pattern (list_chats, search_messages, send_file). 'whoami' is a minor deviation as a single word command. Overall consistent and predictable.

    Tool Count4/5

    With 16 tools, the set covers the core Telegram operations without being overly large. The count is slightly above the typical 3-15 range but still well-scoped for a messaging server that includes a style profiling subsystem.

    Completeness3/5

    The tool surface covers listing, searching, sending, reading, and style profiling. However, common CRUD operations like message editing, deletion, reactions, and chat management (create/leave/mute) are missing, which agents might need.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources