Skip to main content
Glama
Sign In
telegram-mcp-connector

telegram-mcp-connector

by nitatsuu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to telegram-mcp-connector

No user-submitted related servers found.

    Related Servers

    • Telegram MCP Server

      goncaloreis
      F
      license
      Not graded
      quality
      F
      maintenance
      Enables Claude to interact with your Telegram account, including reading messages, searching conversations, and sending messages.
      -

    • mcp_mtproto

      vredin
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to access a personal Telegram account via MTProto, supporting chat and channel history, message search, media downloads, participant lists, and bot interactions.
      3
      MIT

    • telegram-mcp-server

      tamnys
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to interact with Telegram, including listing chats, reading messages, sending messages, searching, and managing contacts.
      1
      -

    • mcp-telegram-local

      pokkop280
      A
      license
      Not graded
      quality
      D
      maintenance
      Connect Claude to your personal Telegram account via MTProto to read messages, search chats, send replies, forward files, and more using your real account.
      6 npm
      3
      MIT

    • Telegram Read-Only MCP Server

      julijakvetna
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets Claude Desktop inspect selected chats and forum topics, retrieve recent messages, and search message history from a personal Telegram account while preventing sending or modification.
      MIT

    • tdl-mcp

      rixile9999
      A
      license
      A
      quality
      B
      maintenance
      Read-only Telegram access for Claude and other MCP hosts. Provides tools to list chats, read recent messages, and download media from your own Telegram account without needing an api_id/api_hash.
      5
      66 npm
      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

    B3.3/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools target clearly distinct needs (account identity, chat listing, message listing, search, unread aggregation, chat metadata). The closest overlap is get_messages vs get_message_context vs get_unread, but descriptions clarify that one pages through a chat, one shows a window around a message, and one aggregates unread across chats.

    Naming Consistency4/5

    Six of seven tools follow a predictable verb_noun pattern (list_chats, get_messages, get_message_context, search_messages, get_unread, get_chat_info). The lone 'whoami' is a conventional but inconsistent exception that breaks the pattern slightly.

    Tool Count4/5

    Seven tools is a reasonable, well-scoped surface for a read-oriented Telegram connector, with no obviously redundant entries. It sits comfortably in the typical 3-15 range and each tool maps to a distinct read operation.

    Completeness2/5

    The surface is entirely read-only: there is no send_message, reply, or mark-as-read operation, which are core Telegram actions an agent would expect from a connector. Reading is well covered (list, page, search, context, unread, metadata), but the missing write side is a significant gap that will cause agent failures for common tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources