Renor MCP server

Renor

Renor is memory for coding agents. You keep notes as Markdown files in a folder on your machine. Renor indexes them and serves them to any MCP client (Claude Code, Codex and others), so an agent can recall what you already decided instead of asking you to paste the same context again.

Try it. After the install and index steps below, stop node dist/cli.js mcp if you left it running (Claude Code starts its own), then, in the same terminal and from this directory, with Node 22 as the node on your PATH, add Renor to Claude Code over MCP:

claude mcp add --scope local renor-local -e VAULT_PATH="$VAULT_PATH" -e EMBEDDING_PROVIDER=eval-hash -e RENOR_EVIDENCE_MODE=off -- node "$PWD/dist/cli.js" mcp

Then start Claude Code in this directory (restart it if it was already running) and /mcp should list renor-local. Claude Code can then search your notes, save facts, and recall them in later sessions. The quickstart vault is a temporary folder, and the cleanup step at the end of "Verify it" below deletes it. For notes you want to keep, point VAULT_PATH at a permanent folder, run node dist/cli.js index, then claude mcp remove renor-local and the command above again.

A hosted version with no install is at .

The problem. Every new session starts from zero. You re-explain the project, the decision you made last week and why, the thing you corrected twice. Renor keeps that context in files you own and hands the relevant part back when an agent asks.

What it does. It indexes your Markdown notes into a local SQLite database, ranks them with embeddings plus keyword and entity signals, and exposes search, recall and remember tools over MCP. Two servers ship here: a command-line server on stdin/stdout, and an HTTP server with OAuth sign-in.

Who it is for. People who run coding agents every day and are willing to run a Node service. It is a single-owner engine: one person's notes, one set of agents. It is not a multi-user product.

Run it offline or hosted. After dependencies are installed, the ten-minute path's runtime indexing and search use no paid model and no network: eval-hash and none are offline embedding settings that exist so you can try it, not a quality claim. If you would rather not run this yourself, a hosted service is at .

License. AGPL-3.0-only for Renor's work (LICENSE); imported upstream files remain ISC (NOTICE). Contributing: CONTRIBUTING.md. Security reports: SECURITY.md. Agent instructions, including the self-hosted setup, are in skill/SKILL.md.

Run everything below in the directory that contains this file and package.json.

Before you install: Node 22 and npm packages

Installation requires internet access to the npm registry, or a populated npm cache that can satisfy npm ci and npm rebuild. Runtime indexing and search in the ten-minute path are offline after those dependencies are installed.

Renor is tested on Node 22 (.nvmrc and mise.toml pin it). Run node -v and check it prints v22.x. better-sqlite3 and sqlite-vec are native modules compiled for one Node major; on a different major a native module can fail at node dist/cli.js index with:

Error: The module '.../better_sqlite3.node' was compiled against a different Node.js version using NODE_MODULE_VERSION 127. This version of Node.js requires NODE_MODULE_VERSION 131.

(The two numbers depend on the versions involved.) The simplest fix is to switch to Node 22 and reinstall:

nvm use            # or: mise use node@22
node -v            # v22.x
rm -rf node_modules
npm ci
npm rebuild better-sqlite3 --ignore-scripts=false

Shortened. The full README is on GitHub.