Skip to main content
Glama
aralroca

Telegram MCP Bridge

by aralroca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Telegram MCP Bridge

No user-submitted related servers found.

    Related Servers

    • vantagate-mcp-server

      Aderix
      A
      license
      Not graded
      quality
      D
      maintenance
      Human-in-the-Loop authorization gateway for AI Agents. Securely pause MCP workflows and route high-risk actions to human approvers via Slack or Email.
      64 npm
      1
      MIT

    • call-a-human-mcp

      nishantmodak
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that enables AI agents to pause and request human approval or information via Slack, Telegram, or macOS dialogs before proceeding with actions.
      2
      15
      Apache 2.0

    • consentgate-mcp

      jessepetersondev
      A
      license
      A
      quality
      D
      maintenance
      Enables MCP-capable agents to gate their actions behind human consent, checking consent rules and requesting approval via Telegram before proceeding with high-stakes operations.
      2
      18 npm
      MIT

    • MTM - MCP Telegram MORE

      v0idhrt
      A
      license
      Not graded
      quality
      C
      maintenance
      A Telegram-integrated MCP server that enables remote control of Claude sessions through a Telegram bot, including chat, tool approvals, task tracking, and workspace management. It provides a MiniApp interface for real-time monitoring and control of Claude's activities from mobile devices.
      90 npm
      4
      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.
      5 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/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose—sending a yes/no confirmation question via Telegram—is clearly distinct by default.

    Naming Consistency5/5

    A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'ask_telegram_confirmation' follows a clear verb_noun pattern.

    Tool Count2/5

    One tool is too few for a server named 'Telegram MCP Bridge,' which implies broader Telegram functionality. This feels thin and incomplete for the apparent scope of bridging Telegram interactions.

    Completeness1/5

    The tool set is severely incomplete for a Telegram bridge. It lacks basic operations like sending messages, receiving updates, managing chats, or handling files, leaving major gaps in the domain coverage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources