노션이 지원하는 AI 메모리.

로어는 AI 비서에게 지속적이고 공유된 기억을 제공합니다: 저장합니다 대화, 결정, 후속 업무, 그리고 노션으로서의 지속적인 관계 어떤 팀원이나 에이전트 세션도 읽을 수 있는 페이지들. 당신이 사용하는 모든 것들 모델 컨텍스트 프로토콜(Claude 코드, Codex, Cursor, OMP 및 기타 MCP 호스트)는 호출, 저장, 그리고 추론할 수 있습니다. 같은 볼트이므로 문맥은 /clear, 새로운 분기, 그리고 핸드오프 사이에 남아 있습니다 사람들.

로어는 볼트를 다섯 개의 핵심 노션 데이터베이스로 조직합니다: 프로젝트, 주제, 메모리, 엔터티(정규 핸들 해석), 그리고 사실입니다. 동일한 도메인 서비스가 세 가지 표면을 구동합니다: MCP 서버, AI 어시스턴트, 인간용 CLI, 그리고 자동으로 배선되는 훅 명령 등이 있습니다 지원 호스트에 대한 컨텍스트 로딩 및 세션 저장.

퀵 스타트

1. 설정 설치

npm에서 설치하세요 (권장)

공개 NPM은 레지스트리 설정이나 패키지 토큰이 필요하지 않습니다.

소스 기반 빌드

npm link는 복제본에서 PATH에서 lore를 전 세계적으로 사용할 수 있게 합니다. lore --version를 실행하여 설치 경로 중 하나를 확인한 후 다음 다음 아래 2단계.

Lore

AI memory backed by Notion.

Lore gives your AI assistants a persistent, shared memory: it stores conversations, decisions, follow-up tasks, and durable relationships as Notion pages that any teammate or agent session can read back. Anything you use with the Model Context Protocol (Claude Code, Codex, Cursor, OMP, and other MCP hosts) can recall, save, and reason over the same vault, so context survives /clear, new branches, and handoffs between people.

Under the hood, Lore organizes a vault into five core Notion databases: Projects, Topics, Memories, Entities (canonical-handle resolution), and Facts. The same domain services power three surfaces: an MCP server for AI assistants, a CLI for humans, and hook commands that wire automatic context loading and session saving into supported hosts.

Quick Start

1. Install Lore

Install from npm (recommended)

npm install -g @notionhq/lore
# or
npm install -D @notionhq/lore

Public npm requires no registry configuration or package token.

Build from source

git clone https://github.com/makenotion/lore.git
cd lore && npm install && npm run build && npm link

npm link makes lore available globally on your PATH from the clone. Run lore --version to confirm either installation route, then continue with step 2 below.

For project-local installs, run npx lore from inside the project or add a lore script to package.json. See docs/dev-dependency-install.md for the Yarn PnP wiring and path-portable setup teams use to share assistant config across a repo.

2. Join an Existing Shared Vault

Most operators should join an already initialized shared vault. A Lore vault is a Notion page that already contains the five databases (Projects, Topics, Memories, Entities, Facts). Joining that vault means pointing your local .lore.yaml at the shared vault.pageId; do not run database initialization against a shared page that your team lead has already bootstrapped.

.lore.yaml is local-only. Keep it out of version control, and distribute shared values such as vault.pageId through onboarding docs instead of committing config. This is the current policy even for credential-free shared vault config and supersedes older changelog notes that allowed intentional committed config.

Notion page IDs are access locators, not bearer credentials: knowing a page ID does not grant access unless the caller’s Notion token can already read that page. Even so, keep vault.pageId out of version control so external clones of a public repo don’t auto-target a maintainer’s vault. If a personal or accidental page ID lands in git history, scrub the working tree and decide with the page owner whether to replace the page or rewrite history.

Internal Notion engineer + shared vault

Use Lore’s ntn-backed auth flow. It auto-installs ntn when needed, runs