@ao_zorin/zocket
v1.4.0
Published
Local encrypted vault + web panel + MCP server for AI agent workflows
Readme
zocket
Local encrypted vault + web panel + MCP server for AI agent workflows.
What zocket provides
- encrypted secret vault across projects/sessions
- local web panel (
127.0.0.1:18001) - MCP server:
- stdio
- SSE (
127.0.0.1:18002/sse) for Claude Code - streamable HTTP (
127.0.0.1:18003/mcp) for Codex
- EN/RU UI and CLI
- first-run web setup:
- set your own password
- generate strong password
- continue without password (with explicit warning)
- project-to-folder mapping with folder picker
- audit log, backup/restore, key rotation
- Linux hardened system services (
zocketd)
Install (instant)
npm i -g @ao_zorin/zocket
zocket initor global from git:
npm i -g github:aozorin/zocket
zocket initQuick start
zocket init
zocket start --host 127.0.0.1 --web-port 18001 --mcp-port 18002 --mcp-stream-port 18003 --mode adminOpen http://127.0.0.1:18001.
MCP-only (no web panel):
zocket server --host 127.0.0.1 --mcp-port 18002 --mcp-stream-port 18003 --mode adminCLI / TUI
Full CLI management:
zocket projects list
zocket projects create myproj --description \"demo\"
zocket secrets set myproj API_KEY abc123 --description \"example\"Interactive TUI:
zocket tuiDocs
- installation (Windows/Linux/macOS):
docs/INSTALL.md - MCP clients (Codex/Claude Code):
docs/CLIENTS_MCP.md - local models (Ollama/Hugging Face):
docs/LOCAL_MODELS.md - AI one-file auto-deploy playbook:
docs/AI_AUTODEPLOY.md - git + npm + pypi release flow:
docs/GIT_NPM_RELEASE.md - external source links:
docs/SOURCES.md
Security defaults
- keep MCP in
metadatamode unless admin tools are required - bind web/MCP to loopback
- on Linux production use:
sudo env ZOCKET_HOME=/var/lib/zocket zocket harden install-linux-system \ --service-user zocketd \ --zocket-home /var/lib/zocket \ --web-port 18001 \ --mcp-host 127.0.0.1 \ --mcp-port 18002 \ --mcp-mode metadata
Development
npm install
npm run build
npm testLicense
MIT, see LICENSE.
