Skip to main content
Glama
archetyx

Telegram MCP Server

by archetyx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Telegram MCP Server

No user-submitted related servers found.

    Related Servers

    • Claude Code Telegram Bridge

      Swigler
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables remote control of Claude Code through Telegram, letting users start or resume sessions, review tool calls with approve/deny buttons, and manage long-running work from a phone.
      14 npm
      MIT

    • Claude Telegram Supercharged

      MattiaHall
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables users to run Claude Code remotely through Telegram, with voice-note transcription and spoken replies, persistent memory, scheduled reminders and calendar access, permission approvals, and live tool-call progress. It also supports daemonized 24/7 operation and a session/subagent dashboard.
      MIT

    • Claude Telegram Supercharged

      morales296
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables running Claude Code continuously from Telegram, with two-way voice notes, persistent memory across restarts, a self-restarting daemon, and live visibility into every tool call. It lets users drive coding sessions, approve permission prompts, schedule messages, and manage Google Calendar directly from chat.
      MIT

    • tsgram-mcp

      areweai
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude Code sessions to Telegram, enabling AI-powered code assistance and file management directly from Telegram chats.
      88
      MIT

    • Claude Telegram Supercharged

      takashif667
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables running Claude Code around the clock from Telegram, with transcribed and spoken voice messages both ways, persistent memory and history across restarts, scheduled messages and calendar access, and live visibility into every tool call and session. A self-healing daemon keeps it running unattended, and permission prompts, long answers, and multi-agent boards are all handled from chat.
      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

    A4.4/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have distinct purposes: get_context_info for session info, notify for structured notifications, send for free messages, send_code for code snippets, send_file for files, send_image for images, unattended_mode for task loops, and wait_reply for blocking replies. However, send and notify could be confused as both send messages, though descriptions clarify notify is preferred for structured content.

    Naming Consistency5/5

    All tools follow a consistent 'telegram_' prefix with snake_case naming (e.g., telegram_get_context_info, telegram_notify). The verb-noun pattern is clear and uniform across all eight tools, making them easily identifiable and predictable.

    Tool Count5/5

    With 8 tools, the set is well-scoped for a Telegram integration server. It covers core functionalities like sending messages, files, images, and code, plus advanced features like context retrieval and unattended modes, without being overwhelming or lacking essential operations.

    Completeness4/5

    The toolset provides comprehensive coverage for Telegram communication, including sending various content types, receiving replies, and managing sessions. A minor gap is the lack of tools for managing Telegram-specific entities like chats or users, but the focus on agent notification workflows is well-covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources