Oort
概览
作者提供的说明(英文原文)
Memory for AI agents that stays correct as facts change.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i3 项中通过 3 项依据公开信息检查;尚未扫描代码
- 使用情况i正在增长↓ 3342/周 · ★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 电脑或云端
- 传输方式: stdio, Streamable HTTP
- 分类: 搜索与 AI 记忆
- 你需要填写:OORT_API_KEY, VOYAGE_API_KEY, TYPESAFE_API_KEY, ANTHROPIC_API_KEY
安装
选择你使用的 AI 应用,然后复制设置。
安装之前
- 基础检查:3 项中通过 3 项
- 在作者的服务器上运行:你向它提出的内容会经过他们的服务器。
- 需要你自己填写:
OORT_HOME,OORT_API_KEY,VOYAGE_API_KEY,TYPESAFE_API_KEY,ANTHROPIC_API_KEY
标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
- 打开 Settings → Connectors
- 点击 Add custom connector
- 粘贴下面的地址,然后点击 Add
- 如果要求登录,请登录作者的服务
https://mcp.oortcloud.dev/mcp或者在你的电脑上运行
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"oort": {
"command": "npx",
"args": [
"-y",
"oortmem",
"mcp"
],
"env": {
"OORT_HOME": "your-value",
"OORT_API_KEY": "your-value",
"VOYAGE_API_KEY": "your-value",
"TYPESAFE_API_KEY": "your-value",
"ANTHROPIC_API_KEY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http oort https://mcp.oortcloud.dev/mcp或者在你的电脑上运行
claude mcp add oort --env OORT_HOME=your-value --env OORT_API_KEY=your-value --env VOYAGE_API_KEY=your-value --env TYPESAFE_API_KEY=your-value --env ANTHROPIC_API_KEY=your-value -- npx -y oortmem mcp运行前请先填写空着的值。
或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"oort": {
"url": "https://mcp.oortcloud.dev/mcp"
}
}
}或者在你的电脑上运行
或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"oort": {
"command": "npx",
"args": [
"-y",
"oortmem",
"mcp"
],
"env": {
"OORT_HOME": "your-value",
"OORT_API_KEY": "your-value",
"VOYAGE_API_KEY": "your-value",
"TYPESAFE_API_KEY": "your-value",
"ANTHROPIC_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"oort": {
"type": "http",
"url": "https://mcp.oortcloud.dev/mcp"
}
}
}或者在你的电脑上运行
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"oort": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"oortmem",
"mcp"
],
"env": {
"OORT_HOME": "your-value",
"OORT_API_KEY": "your-value",
"VOYAGE_API_KEY": "your-value",
"TYPESAFE_API_KEY": "your-value",
"ANTHROPIC_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
- 打开网页版 ChatGPT → Settings → Connectors (Apps)
- 点击 Create 或 Add(部分套餐需要先在 Advanced 中开启 Developer mode)
- 粘贴下面的地址,起个名字,然后保存
- 如果要求登录,请登录作者的服务
https://mcp.oortcloud.dev/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
需要你填写的值
OORT_HOMEenvWhere Oort keeps your memories. Defaults to ~/.oort, shared with the oort command line.- Oort Pro key. With it you need no other keys.
- Voyage AI key, for search by meaning. Leave empty to use Oort Pro, or keyword search only.
- TypeSafe key, for deciding what to keep when saving. Leave empty to use Oort Pro.
- Anthropic key, for writing saved facts. Leave empty to use Oort Pro.
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它能做什么
服务器要求先登录,才会列出它的工具。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 oortmem 验证,该账户拥有此仓库
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- ✓ 通过
端点有响应
在 241 毫秒内响应(HTTP 401)
- ✓ 通过
使用 OAuth 登录
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
- … 尚未检查
工具描述中没有隐藏指令
尚未检查;我们会在检查端点时读取工具列表
与“搜索与 AI 记忆”中的其他服务器比较i
- 星标数多于此分类中其他 5756 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 5756 个服务器的 98% 更新
- 基础检查结果等于或优于此分类中其他 5756 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Oort 安全吗?
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
你需要填写:OORT_API_KEY, VOYAGE_API_KEY, TYPESAFE_API_KEY, ANTHROPIC_API_KEY
它在我的电脑上运行还是在云端?
两种方式都可以:安装在你的电脑上,或者连接云端版本。
它还在维护吗?
GitHub 仓库最后更新于–,最新版本(0.7.1)于今天进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
有什么可以替代它?
同一分类中有:Context7, Codebase Memory, Exa
替代选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Codebase Memory
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Exa
Connect AI agents to Exa for web search, content fetching, and multi-step research.
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Open-source memory for AI agents.
Old facts are closed out, not overwritten. Old history moves to cheap storage.
Every recall can explain why it was picked.
Why Oort
Agents forget between sessions, and the usual fix is a vector store that only grows. That has two problems. Stale facts keep winning ("lives in Berlin" outranks "moved to Lisbon"), and the bill grows with every message you ever stored.
Oort keeps memory the way a solar system keeps matter:
| Tier | Name | What lives there | Recall |
|---|---|---|---|
| Hot | Photosphere | What just happened, and anything pinned | Instant, never searched for |
| Warm | Kuiper Belt | Short distilled facts from past sessions, fully indexed | A few milliseconds |
| Cold | Oort Cloud | Older history, zstd-compressed. The text stays, the heavy vector goes. | Comes back when it matters again |
When a fact changes, the old one is marked superseded and kept for history; a fact found wrong is marked corrected. Recall returns what is true now, unless you ask for --as-of a date, the --history of a fact, or what was --known-at a time (or just ask "what did we use in March").
Quickstart
Install the CLI (Node 22.15 or newer), then connect your agent. oort setup detects your agents, asks how you want to provide keys, connects them and runs a quick check. Every step can be skipped.
npm install -g oortmem
oort setup also installs the managed copy in ~/.oort/cli (npm i -g --prefix ~/.oort/cli oortmem), the one your agents run, so their hooks and MCP entries keep working when you switch Node versions with nvm, fnm, Volta or asdf. More.
To update later, run oort update: it updates every copy here (the managed copy the Claude Code hooks run included), migrates the store and restarts oort serve.
oort setup
oort recall "where does the user live" oort explain "where does the user live" # each stage's rank and score
Every command and flag is in docs/cli.md. To use Oort from your own code (import { createOort } from 'oortmem'): SDK: docs/sdk.md · reference: docs/sdk-reference.md · examples/. To build from source instead: git clone https://github.com/oortmem/oort && cd oort && pnpm install && pnpm build && cd packages/cli && pnpm add -g . (pnpm 12).
Works with
Claude Code (hooks, plus the MCP server), Claude Desktop, Codex, Cursor, Gemini CLI, VS Code, and any MCP client over stdio. oort connect writes the config, backs up the old file and prints the diff. Claude Code guide.
Build with Oort using your coding agent
The oort-sdk skill teaches your coding agent to build Oort into your own apps and agent frameworks: the TypeScript SDK (createOort from oortmem), multi-user apps, the Vercel AI SDK, LangGraph.js and OpenAI Agents JS, serverless, the native Python client (from oortmem import Oort), and the CLI's JSON for other languages. Every code block in it is a tested example. It is a separate plugin, oort-dev, so "help me build with Oort" installs without "memory for my own sessions" (the oort plugin), and the other way round.
Claude Code:
claude plugin marketplace add oortmem/oort
claude plugin install oort-dev@oortmem
(or, in a session, /plugin marketplace add oortmem/oort and /plugin install oort-dev@oortmem)
Codex:
codex plugin marketplace add oortmem/oort
codex plugin add oort-dev@oortmem
(or /plugins in Codex)
Any other agent that reads SKILL.md (Cursor, Gemini CLI, GitHub Copilot, OpenCode and more): copy skills/oort-sdk into its skills folder, for example .agents/skills/oort-sdk in your repository, or run npx skills add oortmem/oort --skill oort-sdk. Details for each tool: skills/README.md.
How it works
flowchart LR
T[Agent turn] --> S[Scrub secrets] S --> W[Writer: distil short facts] W --> G{Decide: add, update, supersede or skip} G --> H[(Photosphere hot)] H -- consolidate --> K[(Kuiper Belt warm)] K -- age out --> C[(Oort Cloud cold, zstd)] Q[Recall query] --> F[Lexical + vector validity filter] F --> R[Fuse and rerank, freshness breaks ties] K --> F C -- stub and entities --> F C -. hydrated when returned .-> A R --> A[Memory block for the prompt]
- Write path. Every turn is scrubbed of secrets first. A small writer model distils it into short facts, and a decision model compares each fact with what is already stored: add it, update it, supersede the old one, or skip it.
- Read path. Keyword (SQLite FTS5) and vector (sqlite-vec) search run together. Facts that are no longer valid are filtered out before ranking. Results are fused, reranked when it helps, and freshness only breaks ties, so a newer fact never beats a better match.
- Local first. Everything lives in
~/.oorton your machine, in one SQLite file plus compressed cold blobs. Nothing is hosted unless you choose Oort Cloud. With no API keys and no Oort Pro login, the local commands make no network call at all (recall falls back to keyword search), and a test runs them with every socket blocked. The one exception is a once-a-day check for a new release, a single request to npm's registry that sends nothing about you;OORT_NO_UPDATE_CHECK=1turns it off (details).
Packages
| Package | What it does |
|---|---|
oortmem | The oort command line (setup, connectors, the local MCP server, recall, import and export), and the TypeScript SDK (docs/sdk.md) |
@oortmem/core | The engine: secret scrubbing, the write gate, hybrid recall, fusion, tiering and project scope |
@oortmem/store-sqlite | Storage on SQLite with FTS5 and sqlite-vec, and zstd cold blobs |
@oortmem/writer | Turns conversation turns into short, self-contained facts |
@oortmem/decide-jev | Add, update, supersede or skip decisions, using TypeSafe Jev |
@oortmem/embed-voyage | Embeddings through Voyage AI |
@oortmem/rerank-voyage | Reranking through Voyage AI |
@oortmem/local-models | Embeddings and reranking on your CPU (ONNX Runtime): no keys, no account |
@oortmem/claude-code | Claude Code hooks and transcript import |
@oortmem/mcp | The MCP tools, schemas, instructions and skill, served over any memory backend |
oortmem on PyPI | The native Python client (Oort, AsyncOort; docs/python.md) and a launcher for the oort command |
Install bundles for Claude Desktop, Claude Code, Codex, Cursor and Gemini CLI are in distribution/.
This repo is the open-source engine and CLI only. The hosted side (oortcloud.dev, Oort Cloud and the Oort Pro relay) is a separate service; the engine and CLI reach it only over HTTPS when you use Oort Pro.
Keys, or Oort Pro
Oort calls three model services: Voyage AI (embeddings and rerank), TypeSafe (decisions) and Anthropic (the writer). Bring your own keys with oort keys set. They stay in the macOS Keychain, or in a 0600 credentials file on Linux and Windows.
Or run with no keys and no account: npm i -g @oortmem/local-models && oort models pull downloads small embedding and rerank models (58 MB, MIT and Apache-2.0) and runs them on your CPU, offline. Saving new memories still needs the decision and writer models. Local models.
Or use Oort Pro: $19/month, VAT included where applicable. No API keys needed. Run oort login, then oort cloud use to keep your memories in Oort Cloud in the EU, with a dashboard, a star map and a connector for claude.ai and ChatGPT. You can export or delete them at any time, or keep them on your machine and use only the relay, which stores no content. Pricing.
Projects and trust
Memories are scoped to a project. By default its id comes from the main repository root, so a git worktree shares memories with its main checkout. A project.id in a repo's oort.config.json is ignored until you run oort project link, because a cloned repo could otherwise use it to read another project's memories. Details in docs/cli.md.
Develop
pnpm install
pnpm verify # public-repo and copy checks, format, lint, build, typecheck and every test
The export format is documented in docs/export-format.md.
Security
Please report vulnerabilities to security@oortcloud.dev, not in a public issue.
License
Apache 2.0. Made in Gothenburg, Sweden.