1AIVault

by stoicsoft

318 downloads
Not rated
GitHub

About

Portable AI memory vault — save memories, skills, and configs to a local database and share them across Claude Desktop, Claude Code, Cursor, Cline, and more.

Details

Author
stoicsoft
Downloads
318
Categories
AI, Developer Tools

- Local-first: all data stored on your machine
- Single SQLite file with WAL mode
- No cloud, no account required
- 20 MCP tools for memories, decisions, and skills
- Knowledge graph to link and traverse related context
- Automatic cross-source topic classification

Download the 1AIVault desktop app, then click "Install" next to your chosen AI client; the app automatically writes the necessary MCP configuration. The server provides 20 tools covering saving and searching entries, a knowledge graph (link and traverse related context), reusable skills, and automatic cross-source topic classification.

Your portable AI memory vault — memories, skills & configs, shared across every AI tool.

1AIVault is a local-first desktop app that acts as aportable 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 thisModel 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

Every AI tool has its own memory silo. Context you build up in one is invisible to the next. 1AIVault gives youone vaultthat 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

1AIVault is a desktop app thatbundlesthis MCP server — there is nothing tonpxor clone.
- Downloadthe app for your OS from
https://1aivault.com(macOS · Windows · Linux)
- Open1AIVault
- Go toConnectand clickInstallnext to your AI client — 1AIVault writes the MCP config automatically

Any MCP-compatible client that supportsstdioservers can also be pointed at it manually (seeHow it works).

The server exposes20 toolsover stdio. Your AI client calls them automatically as you work.

Three processes shareoneSQLite 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--sourcetag records which client wrote an entry;--dbpoints at your vault.

- 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 requiredto use the vault or the MCP server.

- 🌐 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.

Local-first agent memory: a plain-Markdown Obsidian vault is the source of truth, with a rebuildable DuckDB index for hybrid BM25 + vector + graph recall.

Persistent memory and semantic search for AI coding assistants across sessions

Give your agent a memory: shared, cited, tenant-isolated knowledge-graph memory for any MCP host. Grounded answers from a local-first June endpoint — abstains rather than guesses.

Decentralized persistent memory for AI agents — encrypted vault storage built on Walrus and Sui.

Persistent memory for AI assistants and coding agents across ChatGPT, Claude, Cursor, and other MCP-compatible tools.

Local Work Model for AI agents that learns from real outcomes.

Adaptive MCP memory system for AI applications. Learns which retrieval strategies work for your data, scores results using cognitive science models, builds a knowledge graph automatically, and validates every parameter change against real query history before adopting it. Patent pending.

Auditable, self-improving knowledge & memory for AI agents over MCP — citation-enforced answers and a replayable why-trace, self-hosted on Postgres.

Turns your task manager into agent memory: hybrid (RRF) retrieval over TickTick or an Obsidian vault via an adapter contract. MCP server + CLI, no vector DB to maintain.

MCP-native memory layer for Claude Code, Cursor, Cline, Continue, and 16 other AI tools. Hybrid search (BM25 + pgvector + graph), self-hosted on Supabase + Vercel, 100% MIT, no paywall.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.