Skip to main content
Glama
makarworld

claude-telegram-interactive-mcp

by makarworld
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to claude-telegram-interactive-mcp

No user-submitted related servers found.

    Related Servers

    • Telegram MCP Server

      archetyx
      A
      license
      A
      quality
      D
      maintenance
      Enables remote control of AI coding assistants (Claude Code/Codex) via Telegram, allowing you to manage long-running tasks, send commands, and receive notifications from anywhere. Supports unattended mode with smart polling for up to 7 days and multi-session management.
      8
      30
      MIT

    • Telegram Notify MCP Server

      NobufumiMurata
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects VS Code Copilot to Telegram for mobile notifications, interactive approval workflows, and remote command input. Enables users to monitor AI agents, approve sensitive operations, and provide follow-up instructions from their smartphone.
      MIT

    • telegram-bridge

      Itrych
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Cursor agents to ask questions and send notifications to a user via Telegram, and to require Allow/Deny approval for dangerous shell commands through Cursor hooks.
      1
      MIT

    • Telegram MCP Server

      StoyPenny
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with users via Telegram to request decisions, approvals, or specific input through text and clickable buttons. This facilitates a human-in-the-loop workflow where the AI can pause for feedback or send status notifications during long-running tasks.
      3
      -
    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/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: sending different media types, sending text, asking for interactive input, and fetching updates. No overlapping functionality causes confusion; the boundaries are clear.

    Naming Consistency5/5

    All tools use snake_case with a verb-first pattern (send_*, ask_*, fetch_*). Even the longer 'send_markdown_message_as_telegram_bot' follows the same convention, making the set predictable and easy to scan.

    Tool Count5/5

    With 6 tools, the server is well-scoped for Telegram bot interaction. Each tool covers a core operation without redundancy, and the count is neither sparse nor overwhelming.

    Completeness4/5

    The set covers sending text, documents, photos, videos, interactive confirmations, and fetching updates. It lacks some capabilities like editing messages or sending audio, but the core lifecycle of sending and receiving is fully covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources