Skip to main content
Glama
ParthJadhav

Telegram Notify MCP

by ParthJadhav
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Telegram Notify MCP

No user-submitted related servers found.

    Related Servers

    • telegram-bot-mcp

      tingkai-c
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for sending and receiving Telegram messages via a bot, enabling AI assistants to interact directly through Telegram by sending messages, reading recent messages, and sending photos.
      24 npm
      MIT

    • MCP AgentChat

      Lynricsy
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server enabling AI agents to interact with users via Telegram, supporting message and image sending, inline quick replies, and waiting for user responses.
      1 npm
      MIT

    • Telegram MCP Server

      BrainDAO
      F
      license
      A
      quality
      D
      maintenance
      An MCP server for interacting with Telegram bots and channels using the Telegraf library. It allows AI agents to send messages, manage channels, forward content, and intelligently respond to Telegram conversations.
      5
      23 npm
      8
      -

    • herald

      ZenonEl
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that allows AI assistants to send formatted text, files, and updates to Telegram topics, and to capture incoming messages from work chats into a local inbox for retrieval.
      10
      AGPL 3.0

    • telegram-commandcode

      qrak
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Telegram integration with Command Code, enabling AI agents to send messages, photos, files, and read updates via Telegram.
      2
      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.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct content type: text, photo, or document. There is no overlap in purpose, making them easily distinguishable.

    Naming Consistency5/5

    All tool names follow a consistent 'send_' prefix followed by the content type (message, photo, document), forming a clear and predictable pattern.

    Tool Count5/5

    Three tools cover the essential notification actions (text, photo, document) without unnecessary extras, perfectly scoped for a notification server.

    Completeness4/5

    The set covers the most common message types. Minor gaps like video or audio are absent, but for a basic notify server this is not a significant omission.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources