Open source · npm
The dev layer is on npm.
Everything you need to build on Mnemosyne OS is published under the @mnemosyne_os scope, MIT-licensed. The packages talk to the memory on the user’s machine — nothing here phones a cloud.
Start here
One command scaffolds a working cartridge:
npm create @mnemosyne_os/appThe packages
@mnemosyne_os/sdk
The flagship. Build cartridges against the local memory runtime — ingest, query, ask, under FGAC, over WebSocket or IPC.
npm i @mnemosyne_os/sdk View on npm ↗ @mnemosyne_os/create-app
One command, a running cartridge — the official scaffold.
npm i @mnemosyne_os/create-app View on npm ↗ @mnemosyne_os/cartridge-sdk
The secure bridge for embedded cartridges — sandboxed postMessage for iframe widgets.
npm i @mnemosyne_os/cartridge-sdk View on npm ↗ @mnemosyne_os/mcp
The MCP server — gives your AI agents access to vault memory, resonances and git context.
npm i @mnemosyne_os/mcp View on npm ↗ @mnemosyne_os/forge
The MnemoForge CLI — scaffold sovereign modules for the ecosystem in one command.
npm i @mnemosyne_os/forge View on npm ↗ @mnemosyne_os/design-sdk
Custom UI skins for Mnemosyne OS in pure JSON — zero TypeScript required.
npm i @mnemosyne_os/design-sdk View on npm ↗ @mnemosyne_os/public-contracts
Public types, Zod schemas and interfaces — the official integration surface, no business logic.
npm i @mnemosyne_os/public-contracts View on npm ↗ What is not there
Open-core, stated plainly.
The dev layer is public and MIT. The memory core — the engine itself — is sealed inside the app, on purpose: you build on the SDK, and the memory stays on the user’s machine, governed by them.
@mnemosyne_os/sync reserves the name of the P2P layer to come. Today it is a placeholder, not the library — we’d rather tell you than let you npm-install a promise.