1AIVault
1AIVault is a local-first desktop app that acts as a portable memory vault for AI tools. It stores your memories, decisions, preferences, and reusable skills in a local SQLite database and exposes them to your AI clients through this Model Context Protocol (MCP) server — so what you tell Claude Desktop is available in Cursor, Claude Code, Cline, and more. No cloud, no account, no data leaving your machine.
Website & download: https://1aivault.com
Why
Every AI tool has its own memory silo. Context you build up in one is invisible to the next. 1AIVault gives you one vault that all your AI clients read and write through a single MCP server — a shared, portable brain you own, stored on your own disk.
🧠 Cross-tool memory — save in Claude Desktop, recall in Cursor
🔒 Local-first — a single SQLite DB at
~/.1aivault/vault.db, WAL mode, never uploaded🕸️ Knowledge graph — link entries, traverse related context, auto-extract topics across sources
🧩 Reusable skills — save AI instructions once, load them by name anywhere
⚡ Zero-config install — the app writes the MCP config for each client in one click
Related MCP server: CozoDB Memory MCP Server
Install
1AIVault is a desktop app that bundles this MCP server — there is nothing to npx or clone.
Download the app for your OS from https://1aivault.com (macOS · Windows · Linux)
Open 1AIVault
Go to Connect and click Install next to your AI client — 1AIVault writes the MCP config automatically
Supported AI clients
Client | Auto-install |
Claude Desktop | ✅ |
Claude Code | ✅ |
Cursor | ✅ |
Cline (VS Code) | ✅ |
Codex CLI | ✅ |
Gemini CLI | ✅ |
OpenCode | ✅ |
Antigravity CLI | ✅ |
ChatGPT Desktop | ✅ |
Any MCP-compatible client that supports stdio servers can also be pointed at it manually (see How it works).
Tools
The server exposes 20 tools over stdio. Your AI client calls them automatically as you work.
Tool | What it does |
| Save a memory, decision, preference, or fact to the persistent vault |
| Full-text search the vault — supports |
| List recently saved entries, chronologically |
| Fetch entries by tag |
| Edit or rename an existing entry |
| List all tags with counts |
| Fetch one entry by ID (full content) |
| Archive the current conversation as a summary + full text |
| Load a user-defined skill (reusable AI instructions) by name |
| List saved skills (name + description) |
| Link two entries with a named relationship (knowledge-graph edge) |
| Walk the knowledge graph from an entry (up to 3 hops) |
| Keyword search + graph traversal to surface richer connected context |
| Run auto-linking / pattern extraction over entries |
| Fetch entries not yet classified into topics |
| Assign entries to cross-source topics (and update digests) |
| List cross-source topics with entry counts and digest previews |
| Get a topic's cross-source summary, aliases, and entries |
| Full-text search across topics |
| Declare typed relationships between topics |
How it works
Three processes share one SQLite database (~/.1aivault/vault.db, WAL mode) — no HTTP bridge, WAL handles
cross-process concurrency:
Main (Electron) ─┐ ┌─ MCP server subprocesses
├── ~/.1aivault/vault.db (WAL) ──┤ (spawned by Claude Desktop,
Renderer (UI) ───┘ └─ Cursor, Claude Code, Cline, …)Each AI client spawns its own copy of the MCP server as a stdio subprocess. On a packaged install, the server runs through the app's own runtime (so it shares the exact native-module ABI shipped with the app), and 1AIVault writes a config like this for you — you don't edit it by hand:
{
"mcpServers": {
"1aivault": {
"command": "/Applications/1AIVault.app/Contents/MacOS/1AIVault",
"args": [
".../app.asar.unpacked/dist/main/main/mcp/server.js",
"--source", "claude_desktop",
"--db", "/Users/you/.1aivault/vault.db"
],
"env": {
"ELECTRON_RUN_AS_NODE": "1",
"NODE_PATH": ".../app.asar.unpacked/node_modules"
}
}
}
}Paths are resolved per-machine by the app. The --source tag records which client wrote an entry; --db
points at your vault.
Privacy
100% local. Your vault is a file on your disk. Nothing is sent to any server by the MCP layer.
You own the data. Curate, export, and move it between machines from the desktop app.
No account required to use the vault or the MCP server.
Links
🌐 Website & download — https://1aivault.com
🏢 Made by StoicSoft
📨 Support — hello@stoicsoft.com
1AIVault is commercial software. This repository is documentation for the bundled MCP server; the app source is not open source. © StoicSoft.
This server cannot be deployed
Maintenance
Related MCP Connectors
Persistent AI memory shared across Claude, ChatGPT, coding agents, and compatible MCP clients.
Persistent memory for Claude Code and Cursor. Stop re-explaining your project every session.
- mcpOAuthai.butlerbrain
Persistent memory for AI assistants. Save once; recall from Claude, ChatGPT, or any MCP client.
Shared memory for AI coding agents. Save once, reuse from Cursor, Claude Code, Codex.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceLocal-first, file-based memory layer for AI agents — one shared Markdown vault across Claude, Codex, Gemini, Cursor and any MCP client. Provides read/write memory tools with an audit trail, per-agent trust levels, and Git sync; no cloud and no lock-in.2MIT
- AlicenseNot gradedqualityDmaintenanceLocal-first memory for Claude & AI agents with hybrid search, Graph-RAG, and time-travel, runs entirely on your machine.42 npm1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceLocal-first memory for your AI agent. One SQLite file you own — offline, no API key. Plugs straight into Claude Code.Apache 2.0
- AlicenseNot gradedqualityAmaintenancePersistent, local-first memory for your AI chats. Save context in one chat, load it in another — across Claude web, Claude Code, Cursor, Cline, and Claude Desktop. One store, on your own disk, reachable from every tool via MCP, CLI, REST, or SDK.1,095 npmApache 2.0