Skip to main content
Glama
abdwhb-png

pi-session-recall

by abdwhb-png
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to pi-session-recall

No user-submitted related servers found.

    Related Servers

    • logbook

      olly-styles
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides full-text search and retrieval of archived Claude Code session transcripts, enabling agents to inspect past sessions without loading entire transcripts.
      1
      MIT

    • transcripts-mcp

      Stormix
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables searching and reading local Cursor, Claude Code, and Codex session transcripts from any MCP client, with fuzzy, regex, and full-text search, plus optional semantic search.
      12
      MIT

    • session-recall

      AbsoluteMode
      A
      license
      B
      quality
      C
      maintenance
      Provides local, agentic semantic recall over Claude Code session history, enabling the agent to search past discussions semantically, expand turns, and grep transcripts.
      5
      12
      MIT

    • MCP Memory

      PascalNoisette
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to Kilo Code and Opencode conversation history stored in a local SQLite database, allowing users to list projects and sessions, read messages, and perform full-text keyword searches across all messages.
      -

    • ai-r

      pro-target
      A
      license
      A
      quality
      B
      maintenance
      Provides a read-only interface to audit and continue coding agent sessions by extracting plans, intents, and edit authorship from history across multiple agents (Claude, Codex, OpenCode, Antigravity, Pi) via MCP, CLI, and Python SDK.
      18
      3
      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.9/5.0

    Scored across 4 tools

    Disambiguation4/5

    Search vs find overlap slightly since search also recognizes UUIDs, but the descriptions explicitly direct UUID lookups to pi_session_find. Context vs search also share retrieval intent, but context is clearly framed as deterministic lexical context for a question, keeping boundaries workable.

    Naming Consistency4/5

    All four tools share the pi_session_ prefix and are mostly verb-suffixed (search, find, read), which reads predictably. pi_session_context deviates by using a noun rather than a verb, a minor inconsistency.

    Tool Count4/5

    Four tools cover the natural read-only recall surface (text search, ID lookup, contextual retrieval, paged reading) without redundancy. Scope is slightly thin but each tool earns its place.

    Completeness4/5

    As a read-only session recall server, it covers search, direct lookup, contextual retrieval, and paged reading with scope and raw-mode options. No obvious gaps for retrieval, though write/export operations are absent (appropriately so for a recall tool).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources