Skip to main content
Glama
ttrine

transcript-search

by ttrine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to transcript-search

No user-submitted related servers found.

    Related Servers

    • transcript-search-v2

      jsundquist
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that indexes local Claude Code transcripts and provides keyword, phrase, semantic, and date-range search, plus full context/session recall.
      -

    • engram-mcp

      lowbridgee
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables semantic and keyword search over Claude Code conversation history stored locally, using hybrid search, local embeddings, and time-decay scoring.
      10 npm
      MIT

    • Quaid

      SEEDO-Media-Ltd
      A
      license
      Not graded
      quality
      B
      maintenance
      Capture, index, and search your Claude Code conversation history. Provides an MCP server for Claude Code to query its own past conversations.
      6 npm
      1
      MIT

    • smart-fork

      recursive-vibe
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for Claude Code that enables semantic search of past session transcripts and intelligent session forking, allowing users to find and resume from relevant previous conversations with full context.
      13
      8
      MIT

    • memex

      dioniipereyraa
      A
      license
      A
      quality
      B
      maintenance
      MCP server that indexes Claude.ai chats and local Claude Code sessions, enabling semantic and keyword search across all your conversations with Claude.
      6
      6
      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/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one searches across transcripts, the other retrieves full session context. No overlap or ambiguity in their roles.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern using snake_case: search_transcripts and get_session_context. The naming is predictable and uniform.

    Tool Count4/5

    With only 2 tools, the set is minimal, but it is appropriately scoped for a narrow transcript search-and-retrieve workflow. Slightly on the thin side, though reasonable for the stated purpose.

    Completeness5/5

    The workflow is complete: search for relevant transcripts and then retrieve full session context. No obvious missing operations for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources