Skip to main content
Glama
Mobiss11

tg-mcp

by Mobiss11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to tg-mcp

No user-submitted related servers found.

    Related Servers

    • tg-account-mcp

      Mesteriis
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to work with Telegram through explicitly selected user accounts and bots, supporting search, reading, sending, and message management with consent-based access.
      Apache 2.0

    • NetGram

      dm1tryG
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to scoped, permissioned access to Telegram chats with per-chat read/write levels and human approval for sending messages.
      1
      MIT

    • Telegram MCP

      zai-one
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to read Telegram conversations, search messages, retrieve chat context, resolve recipients, and send messages with delivery status.
      1
      -

    • TeleMCP

      charlesmmorais
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search and act on Telegram conversations, groups, channels, files, and links, with semantic search, AI-powered knowledge extraction, human-in-the-loop approvals, and PostgreSQL/pgvector persistence.
      Apache 2.0

    • telegram-business-bridge

      AndyShaman
      A
      license
      A
      quality
      B
      maintenance
      Connect any AI agent to your personal Telegram messages through the official Business API, enabling message history search and draft replies with optional manual approval.
      7
      18
      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 15 tools

    Disambiguation4/5

    Most tools are clearly separated by action (chat_info vs list_chats, get_messages vs search_messages vs semantic_search), but draft_message/draft_edit/draft_delete and outbox_cancel/outbox_list/outbox_status could cause some confusion for agents, though descriptions clarify the distinctions.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (list_chats, get_messages, search_messages, draft_message, outbox_list). Minor deviations like chat_info and message_context use noun phrases instead of verb_noun, but the pattern is mostly predictable.

    Tool Count5/5

    15 tools is within the well-scoped range for a Telegram MCP server covering chat browsing, search, media processing, and message drafting. Each tool serves a distinct function in the workflow.

    Completeness4/5

    The server covers chat listing, message retrieval, search, semantic search, backfill, media fetching, and the full draft/send/edit/delete lifecycle. Minor gaps like sending direct messages without owner confirmation or managing chats are absent, but the core domain is well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources