v1.2 / DOCS

Connect, capture, recall — in plain language.

Public-facing docs cover the hosted beta flow, the REST API, the MCP server, and the current SDK/package boundary. Every example below points at repo-backed routes or package commands.

SIGN INSign in with Google

Google Identity Services for invited users. Server-side OIDC validation. Personal vault is created on first login.

BRIDGElore connect

Generates a one-time install token; supports Claude Code, Codex, Cursor, OpenCode. macOS Keychain stores the device token.

EXTENSIONChrome MV3 beta

Distribution-gated browser capture with per-domain authorization, pause/private mode, summary preview, and no raw transcript by default.

INBOXMemory Inbox

States: pending, approved, rejected, edited, duplicate, stale, sensitive, conflict, source-paused, deleted. Every action is audited.

RECALLEvidence Ledger

Every recall has a trace_id. Used, ignored, stale, conflicting, risky memories are labeled, not silently injected.

PRIVACYPause & delete

Pause a source, delete a memory, delete a vault. Audit logs keep metadata; content is hard-deleted with proof.

SELF-HOSTv0.6 alpha docs

Open-core material is preserved under /en/docs.html for operators who run Lore locally.

Quickstart

For hosted beta users, start in the app, then generate a connection token from the dashboard. For local operators, the public source path remains clone plus quickstart.

git clone https://github.com/Lore-Context/lore-context
cd lore-context
pnpm install
pnpm quickstart -- --dry-run --activation-report
pnpm openapi:check
pnpm smoke:mcp

REST API and OpenAPI

The canonical read path is POST /v1/context/query. Memory write, search, list, forget, export/import, governance, traces, Evidence Ledger, eval, cloud device pairing, connectors, source pause/resume, usage, and Memory Inbox routes are listed in the full API reference and /openapi.json.

export API=https://api.lorecontext.com
export AUTH="Authorization: Bearer $LORE_API_KEY"
curl -s "$API/v1/context/query"   -H "$AUTH" -H "content-type: application/json"   -d '{"query":"What auth flow did we approve?","include_sources":true}'

SDK/package status

The shipped package surface today is the MCP stdio server @lore-context/server. A separate typed application SDK is not marketed as generally available in v2.1.0; examples use REST, OpenAPI, and MCP so developers can verify them from the repo.

LORE_API_URL=http://127.0.0.1:3000 LORE_MCP_TRANSPORT=sdk npx -y @lore-context/[email protected]

MCP server

The MCP server proxies tools to a Lore API through LORE_API_URL and forwards LORE_API_KEY as a bearer token. Default tools include context_query, memory.recall, memory.add_candidate, memory.inbox_list, memory_write, memory_search, memory.suggest, source.pause, source.resume, and code-context tools. Advanced support tools such as memory_list, memory_export, eval_run, trace_get, and evidence.trace_get are opt-in through LORE_MCP_ADVANCED_TOOLS=1 for stdio or x-lore-mcp-advanced: 1 for hosted MCP.

LORE_HOSTED_MCP_URL=https://api.lorecontext.com/mcp LORE_API_KEY=lct_service_xxx LORE_MCP_TRANSPORT=sdk npx -y @lore-context/[email protected]

# Advanced support tools only:
LORE_MCP_ADVANCED_TOOLS=1 npx -y @lore-context/[email protected]

Docs are intentionally conservative: if a route, SDK, package, or hosted capability cannot be verified from this repository or the public API metadata, the page labels it beta, pending, or not generally available.