Sthayi MCP server

sthayi

AI memory you own.

A sovereign, local-first memory / skills / MCP-registry plane — so supported AI clients on your machine can read and write one shared local memory that you own.

sthayi (Sanskrit): permanent, enduring. The sthāyī bhāva is the enduring emotion

beneath transient states; the sthāyī in Hindustani music is the refrain a raga always

returns to. Pronounced "STAY-ee."

Your memory today can be scattered across Claude, ChatGPT, Gemini, Cursor, and CLI agents — multiple apps, multiple fragments, none of them yours. Sthayi is not another silo and not a replacement: it coexists with each app's built-in memory — in addition, not instead — as one shared local memory exposed to supported clients over MCP. There is no hosted Sthayi service and no Sthayi account — only the local MCP server running on your machine. Theirs stay theirs. This one is yours.

Quickstart

Prerequisite: Node.js 22 or 24

Sthayi v0.1.3 supports Node.js 22 and 24, with Node 24 LTS recommended, and requires npm. Check both before installing:

node --version
npm --version

node --version must begin with v22. or v24.. If Node is missing or reports any other major version—including Node 25—install Node 24 LTS from the official Node.js download page using the normal/default location offered for your operating system. npm is included with the standard Node.js distribution. Reopen your terminal afterward, then run both checks again. Sthayi refuses an unsupported Node major before loading its native SQLite dependency and explains this repair.

Node.js does not need to be installed inside Sthayi's prefix. Installing Node.js is a separate prerequisite and may require administrator approval, depending on the operating system and install method. Once Node.js and npm are available, the Sthayi installation below stays in user space and needs neither sudo nor administrator rights.

Install and initialize

Sthayi v0 uses a better-sqlite3-backed local store. The user-space command below first refuses

any Node major other than 22 or 24, then requests the npm latest tag explicitly and makes npm

enforce the package's engine declaration. Those two npm qualifiers prevent an unsupported Node

runtime from silently selecting an older compatible release. Do not substitute npx sthayi init.

Contributing from a source checkout instead? Use the Development workflow.

# macOS / Linux — bash or zsh
node -e "const m=Number(process.versions.node.split('.')[0]);if(m===22||m===24){}else{console.error('Sthayi requires Node.js 22 or 24 (24 LTS recommended). Detected '+process.version+'. Install Node.js 24 LTS: https://nodejs.org/en/download');process.exit(1)}" && npm install -g --prefix "$HOME/.local" --engine-strict sthayi@latest && "$HOME/.local/bin/sthayi" init

One line: install once somewhere durable, then detect your AI clients and wire them in one keystroke.

After the wizard completes, verify the default installation and state directory:

"$HOME/.local/bin/sthayi" doctor

This invokes the package from the durable install prefix; doctor reports the configured state directory, including a custom absolute STHAYI_HOME when one is set.

Shortened. The full README is on GitHub.