Skip to main content
Glama
Sign In
Fast MCP Telegram

Fast MCP Telegram

by leshchenko1979
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Fast MCP Telegram

No user-submitted related servers found.

    Related Servers

    • Telegram MCP Server

      alexeyleshchenko
      A
      license
      A
      quality
      C
      maintenance
      MCP server that acts as a gateway to Telegram, providing AI-optimized tools for messaging, search, and chat management via MTProto. Supports multi-user authentication with QR login and HTTP/stdio transports.
      8
      2
      MIT

    • mcp-telegram

      Prgebish
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects AI assistants to your real Telegram account via User API (MTProto). Features default-deny ACL with per-chat permissions, message search, file sending, forwarding, media downloads, and rate limiting.
      3
      MIT

    • Better Telegram MCP

      n24q02m
      A
      license
      Not graded
      quality
      A
      maintenance
      Production-grade MCP server for Telegram with dual-mode Bot API and MTProto. 6 composite tools covering messages, chats, media, contacts management with 3-tier token optimization.
      11
      Apache 2.0

    • Telegram Agent for Codex

      Frejixxx
      A
      license
      Not graded
      quality
      D
      maintenance
      Privacy-first Telegram MCP server enabling maintainers to triage chats, inspect context, search messages, draft replies, and send authorized messages locally without a cloud relay.
      57 npm
      1
      MIT

    • Telegram MCP

      salto-agancy
      A
      license
      A
      quality
      B
      maintenance
      Gives MCP clients controlled access to a Telegram user account, letting them search and read messages, inspect chats, and fetch media, with sending or editing messages available only after explicit opt-in. It runs self-hosted over FastMCP and Telethon with strict read-only defaults, OAuth or bearer authentication, and an outbound-only Cloudflare Tunnel.
      11
      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.1/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool has a fairly distinct role: reading (get_messages, get_chat_info), searching (search_messages_globally, find_chats), writing (send_message, edit_message), plus a phone-targeted send and an MTProto escape hatch. The only mild overlaps are find_chats vs get_chat_info (locate vs profile) and the two send_message variants, but names and descriptions make the intended split clear.

    Naming Consistency4/5

    All snake_case with a leading verb (get_, search_, send_, edit_, find_, invoke_), which is predictable. Minor deviations: qualifier suffixes on search_messages_globally and send_message_to_phone, and invoke_mtproto uses a protocol name rather than a resource noun.

    Tool Count5/5

    Eight tools is well within the 3-15 sweet spot for a Telegram client surface, and each tool covers a substantive capability rather than a thin variant. Nothing appears redundant or padded.

    Completeness4/5

    Read, search, send, edit, chat discovery and profile lookup are covered, and invoke_mtproto provides an escape hatch for the rest. However, common lifecycle operations like deleting messages, forwarding, or joining/leaving chats have no first-class tool, leaving agents to fall back on raw MTProto calls.

    Maintenance

    ActivityActive
    ResponsivenessLimited data

    Resources