Skip to main content
Glama
Rerowros

tg-recall-mcp

by Rerowros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to tg-recall-mcp

No user-submitted related servers found.

    Related Servers

    • letopis-mcp

      Toligrim
      F
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server that exposes retrieval tools over a Telegram chat archive, including archive overview, full-text search with Russian morphology, aggregates, message retrieval, and local context. It lets LLM agents answer questions from chat history without syncing Telegram, downloading files, or modifying the index.
      -

    • telegram-notes-mcp

      RaspizDIYs
      A
      license
      A
      quality
      C
      maintenance
      A local MCP server that enables full-text and semantic search over your own Telegram chats using your personal MTProto login, with everything running locally.
      7
      MIT

    • 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.
      32 npm
      1
      MIT

    • telegram-mcp

      davidphc
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that connects to a Telegram group chat, persists messages to a local SQLite database, and exposes tools to search, retrieve, and send messages via SSE.
      -
    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

    C2.9/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools are distinct in purpose: search/research tools (search_messages, retrieve_evidence, ask_archive, query_knowledge_catalog, inspect_research_session) vs. retrieval/expansion (get_message_context, expand_cited_sources) vs. admin listing (list_allowed_chats, list_scopes). However, there is notable overlap between search_messages, retrieve_evidence, ask_archive, and query_knowledge_catalog — all involve retrieving or searching cited/local content, making it ambiguous which to select for a research query.

    Naming Consistency3/5

    Names follow a loose pattern but mix verb styles: sometimes verb-first (get_, ask_, list_, search_, retrieve_, expand_, inspect_) and sometimes query_knowledge_catalog breaks the pattern by using noun-first ordering. Most use snake_case but the verb prefixes are inconsistent (get vs retrieve vs search vs ask vs query all for similar retrieval actions).

    Tool Count4/5

    9 tools is a reasonable, well-scoped count for a Telegram archive/recall MCP server. The count feels appropriate given the mix of admin/config tools, search tools, and session/catalog inspection tools. Not overly heavy or thin for the domain.

    Completeness3/5

    The server covers search, retrieval, context expansion, chat/scope listing, and research session inspection. However, there are notable gaps: no tool to add/configure sync scopes (only list_sync_scopes), no tool to manage allowed chats (only list), and no evident way to trigger or manage syncing/indexing. The surface is read-oriented and administratively incomplete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources