Practical overview
When it fits
Use Papervault when you want an encrypted, offline-oriented paper recovery kit for sensitive information and need control over how many separate key shares are required to unlock it. Choose self-hosting or the standalone build when a local workflow is important; choose the CLI or integrations when secrets originate in scripts or another application.
Who it is for
- People preserving passwords, 2FA recovery codes or disk-encryption keys in an offline recovery kit.
- Digital-asset holders who want printed key-backup materials.
- Teams or individuals arranging recovery across separate vault-page and key-share holders.
- Developers integrating vault creation into another tool or using the command-line or MCP interfaces.
Documented uses
- Encrypt foundational secrets for offline storage.
- Create a configurable set of key shares with a chosen unlock threshold, such as three shares out of five.
- Print vault and key-share documents or save them to digital media.
- Arrange recovery by storing the vault page separately from the shares.
- Use the CLI to import secrets from .env or JSON, Azure Key Vault, or interactive entry.
Requirements & limits
The project describes itself as free and open source and provides a browser app, self-hosted setup, standalone builds and other integration routes. The repository is licensed under MIT.
- A vault requires both the vault page and enough key shares; distributing shares alone does not provide the complete recovery material.
- The README says the vault format is identical across the documented entry points, including the web app and self-hosted instance.
- The project describes the app as client-side and offline-capable after installation; its README recommends self-hosting, ideally air-gapped, for maximum security.
- The CLI accepts .env and JSON files, Azure Key Vault, or interactive input; the browser app is documented as a static React bundle.
- The repository lists JavaScript as its primary language and MIT as its license.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Start a self-hosted web app
Run the PaperVault web app locally using the repository’s documented setup steps.
Before you start
- Git
- Node.js and npm, as required by the documented npm installation steps
Steps
Clone the repository: git clone https://github.com/boazeb/papervault.git
Change into the papervault directory.
Install dependencies with npm install.
Start the app with npm start and open http://localhost:3000.
Expected outcome
A locally served PaperVault web app, which the README says can be run on an air-gapped machine.
Guide limitations
- The README recommends self-hosting for maximum security but does not provide independent security verification.
- These setup steps do not cover creating or recovering a vault.
Configure the PaperVault MCP server for Claude Code
Add PaperVault’s MCP server to Claude Code and load it in a new session.
Before you start
- Claude Code
- Node.js/npm access for the documented npx command
Steps
Run claude mcp add -s user papervault -- npx -y @papervault/mcp.
Restart Claude Code or start a new conversation so the MCP server loads.
Expected outcome
The PaperVault MCP server is configured for Claude Code; the README describes agent-triggered paper backups before risky operations.
Guide limitations
- The documented setup does not show a backup operation or its result.
- The README describes the agent workflow as backing up secrets without agents seeing secret values; this guide does not independently verify that claim.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 8 October 2026
- Original website title
- boazeb/papervault · Official homepage title · retained in its source language