Skip to main content
Glama
nullnumber1

Telegram Community MCP

by nullnumber1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Telegram Community MCP

No user-submitted related servers found.

    Related Servers

    • cowork-history

      egoughnour
      A
      license
      B
      quality
      C
      maintenance
      Enables searching and browsing of Claude conversation history with hybrid search combining full-text, Spotlight, and optional vector embeddings.
      10
      1
      MIT

    • Telegram MCP Server

      kamalbuilds
      A
      license
      A
      quality
      D
      maintenance
      Enables reading and searching Telegram channel/group/DM messages from Claude Code using MTProto for full message history access.
      5
      29 npm
      MIT

    • quarry

      punt-labs
      A
      license
      A
      quality
      A
      maintenance
      Enables local semantic search over documents and code for Claude Code and Claude Desktop, running entirely offline with local embeddings and vector storage.
      14
      92 PyPI
      5
      MIT

    • 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
    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.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct operation: sync ingests messages, get_stats reports index metrics, search queries messages, get_context expands a thread, and list_chats enumerates chats. Search and get_context both retrieve messages but are clearly differentiated (query vs. thread expansion around a known message). No meaningful overlap.

    Naming Consistency4/5

    Three tools follow a clean verb_noun pattern (get_stats, get_context, list_chats), while sync and search are bare verbs. This is a minor deviation but still readable and consistent in spirit (all lowercase snake_case).

    Tool Count5/5

    Five tools is well within the ideal 3-15 range and each earns its place in the ingest-search-context lifecycle. Nothing is redundant or superfluous.

    Completeness4/5

    The read/index domain is well covered: sync, stats, search, thread context, and chat listing form a coherent lifecycle. Minor gaps exist (no fetch-by-message-ID, no chat add/remove or re-index management), but agents can work around these via search and list_chats.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources