Skip to main content
Glama
ZenonEl

herald

by ZenonEl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to herald

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

      zhigang1992
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables interaction with Telegram to send, read, and search messages across chats and dialogs. It supports waiting for incoming messages and retrieving conversation history through natural language commands.
      4 npm
      3
      MIT

    • tg-mcp

      draiqw
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that gives AI agents full access to a personal Telegram account via MTProto, enabling chat reading, history search, messaging, media handling, and automations.
      79
      MIT

    • 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.6/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, with send_update, send_text, and send_client_copy all serving different messaging contexts. However, send_update and send_client_copy could be confused as both produce client-ready copy, though their descriptions clarify the structured update vs topic-based copy distinction.

    Naming Consistency3/5

    The send_*, list_*, and notify_* tools follow a consistent verb_noun pattern, but the inbox_* family breaks this with noun-first names like inbox_status, inbox_fetch, inbox_done, and inbox_export, mixing nouns, verbs, and an adjective. This creates noticeable inconsistency.

    Tool Count5/5

    With 10 tools, the set is well-scoped for the server's purpose of Telegram messaging and inbox management. Each tool serves a distinct function and none feel redundant or unnecessary.

    Completeness4/5

    The inbox lifecycle is well covered with status, fetch, export, and done, and the sending tools handle various message types. A minor gap exists in managing destinations or allowed projects, but those are likely configured externally, so core workflows are complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources