session-vault
Related Servers
Alternatives to session-vault
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to list, inspect, and export OpenCode AI coding sessions as HTML/JSON archives with secret redaction and token statistics.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables browsing, searching, and importing sessions from multiple coding agents into the current one, or reopening them in their native agent, all locally and read-only.3MIT
- AlicenseAqualityAmaintenanceLossless archive and search for AI agent sessions (Claude Code, Codex, opencode, pi and others), exposed to agents over MCP. Local-first, written in Rust.481Apache 2.0
- FlicenseNot gradedqualityCmaintenanceCaptures code build sessions and publishes them to a shared team knowledge base, making past work discoverable via semantic search.-
- AlicenseNot gradedqualityBmaintenanceEnables 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.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to discover, redact, and upload coding-agent traces, then earn USDC/USDT by selling access to those traces to researchers and model trainers.MIT
TDQS
Scored across 10 tools
Each tool targets a distinct resource-action pair (project, session, archive, remote_copy, tag), with no overlapping functionality. Agents can clearly differentiate between tools.
All tools follow a consistent snake_case pattern: 'session_vault_<resource>_<action>'. The naming convention is uniform and predictable.
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.
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.