Skip to main content
Glama
Zhuchen00123

session-vault

by Zhuchen00123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to session-vault

No user-submitted related servers found.

    Related Servers

    • opencode-export

      ZelinZhou-THU
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to list, inspect, and export OpenCode AI coding sessions as HTML/JSON archives with secret redaction and token statistics.
      1
      MIT

    • pond

      tenequm
      A
      license
      A
      quality
      A
      maintenance
      Lossless archive and search for AI agent sessions (Claude Code, Codex, opencode, pi and others), exposed to agents over MCP. Local-first, written in Rust.
      4
      72
      Apache 2.0

    • pacifico

      emersoftware
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables local archiving and searchable recall of AI coding sessions from Claude Code, Codex, Pi, and OpenCode via MCP, allowing agents to access past conversations as context.
      MIT

    • Wisp FigureFree

      Yu-Qiao-sjtu
      A
      license
      B
      quality
      B
      maintenance
      Enables users to import scientific figures together with their code, review and publish them as immutable releases into one user-chosen local library, then search, preview and materialize an exact confirmed template into any project from Claude Science, Cursor, Codex or other stdio MCP hosts. It keeps the catalog on disk and never executes plotting code, so the host agent inspects files while the server hashes, versions, gates and publishes them.
      65
      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

    C2/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair (project, session, archive, remote_copy, tag), with no overlapping functionality. Agents can clearly differentiate between tools.

    Naming Consistency5/5

    All tools follow a consistent snake_case pattern: 'session_vault_<resource>_<action>'. The naming convention is uniform and predictable.

    Tool Count5/5

    With 10 tools covering multiple resources (projects, sessions, archives, remote copies, tags), the count is well-scoped and appropriate for a focused session vault management server.

    Completeness2/5

    The tool set lacks essential CRUD operations for core resources. Projects and sessions only have list functionality, and archives are missing update/delete. These gaps hinder full lifecycle management.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources