Recall By Polign

MCP文档知识

提供方 未标注

文档知识 未标注 API Key 社区 / 第三方 ClaudeCursorVS CodeCodex

用于记录会变化的事实的 Agent 记忆。更正会替换旧事实,答案会显示它替换了什么,历史记录和 as-of 读取会显示任意日期所认为的内容。本地,Apache 2.0。

一句话选型结论

按资料字段整理

Recall By Polign 属于文档知识类 MCP 服务器,传输方式未标注,API Key,可直接接入 Claude、Cursor、VS Code 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式未标注 鉴权API Key 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

未标注 API Key
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Recall By Polign当前 未标注 未标注 未标注 无 2026-11-20
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

13.5 KB
来自项目仓库与上游目录的原文,未做删改

Polign Recall

Recall gives an agent memory and state that survive the conversation and the
process. Memory is what the agent knows: facts a user stated, with every
correction kept, so the agent can say what it believes now, what it believed
before, and why. State is where the agent is: its progress, its notes to its
next instance, and the tool calls it had in flight, so a run that crashes or
moves machines resumes from its own records.

Recall is a Go library, a recall binary that serves the same operations as
MCP tools and as HTTP, and a Python client. It stores everything in a
database you run: polign_db, PostgreSQL, MongoDB or Qdrant. Apache 2.0.

One user over nine months, three homes, three employers, three work emails,
six questions, Claude Opus 5.5 extracting, answering and judging for all three
systems: Recall 18/18, mem0 18/18, Zep 12/18. Tokens to save one message:
Recall 3.0k, mem0 12.7k, Zep 14.7k.

The code to the Recall repository.

Install```sh

pip install polign-recall # the Python client, the recall binary, and the database it runs
brew install polign/tap/recall # the same for Homebrew
go install github.com/Polign/recall/cmd/recall@latest # the binary alone; it fetches the database on first use


Then give it to the agent you use:```sh
claude mcp add recall -- recall mcp -write      # Claude Code

Add to Cursor ·
Add to VS Code ·
any other MCP host: command recall, arguments mcp -write (details).

With nothing configured, memory lives in a local database in
~/.local/share/recall, started on first use and shared by every agent on the
machine. No model and no API key are needed to start. To keep memory in a
database you already run, see Backends.

What a correction looks like

Every change is kept. Three commands read the record:```text
$ recall history "which editor do I use"
user preferred editor
believed now: user preferred editor: zed
2026-09-01 10:00 stated, user_stated
+ user preferred editor: vim
2026-09-20 10:00 replaced, user_stated
- user preferred editor: vim
+ user preferred editor: emacs
2026-10-05 10:00 replaced, user_stated
- user preferred editor: emacs
+ user preferred editor: zed

$ recall ask -as-of 2026-09-25 "which editor do I use"
Believed as of 2026-09-25 00:00:
user preferred editor: emacs (since 2026-09-20)
replaced: vim (since 2026-09-01)

$ recall diff -from 2026-09-15 -to 2026-10-31
Changed between 2026-09-15 00:00 and 2026-10-31 00:00:
- user home city: Lisbon
+ user home city: Porto
- user preferred editor: vim
+ user preferred editor: zed


## Why Recall

- **Corrections are records, not overwrites.** A new value replaces the old
  one by a rule you can read, and every answer arrives with what it replaced.
- **Any moment is readable.** `as_of`, `history` and `diff` say what the agent
  believed then and when that changed.
- **Every answer has a source.** `recall explain` shows the message a fact came
  from, the rule that decided it, and its history.
- **Agents resume from records.** A crashed or moved agent gets its working
  state, recent turns and unfinished tool calls back, not a snapshot.
- **Your storage, your rules.** Memory lives in a database you already run, and
  the vocabulary of what gets remembered is yours to define or leave open.

## Quickstart

Python 3.10 or later. Save a preference, then correct it:```sh
pip install polign-recall
python - <<'PY'
from polign_recall import Client

with Client(local_dir="./recall-data", typed=True) as memory:
    memory.remember("user", "prefers_editor", "vim")
    memory.remember("user", "prefers_editor", "neovim")
PY

A second process reads the current value, the history, and what was believed
before the correction:```sh
python - <<'PY'
from polign_recall import Client

with Client(local_dir="./recall-data", typed=True) as memory:
print(memory.recall("user", "prefers_editor")[0].value) # neovim

events = memory.history(&quot;user&quot;, &quot;prefers_editor&quot;)
print([e.value for e in events])                           # [&#x27;vim&#x27;, &#x27;neovim&#x27;]

before = memory.recall(&quot;user&quot;, &quot;prefers_editor&quot;, as_of=events[0].observed_at)
print(before[0].value)                                      # vim

PY


The first client to open `./recall-data` starts a local database for it and
later clients share it; the memories stay there after the program exits. A
bare `Client()` uses `~/.local/share/recall`, the memory every agent on the
machine shares. The Python client guide covers the rest:
plain-text memory with a model, forgetting, history, and resuming an agent.

## How memory works

A memory is a **subject**, a **predicate** and a **typed value**: `user`,
`prefers_editor`, `neovim`. Predicates live in a registry that says what type
a value has, whether the predicate holds one value or many, and which
predicates it contradicts: `dislikes` excludes `likes`, `gave_away` excludes
`owns`. A single-valued predicate replaces its value on a new statement; a
multi-valued one accumulates. Forgetting records a withdrawal; nothing is
deleted. Recall ships starter registries
for coding, personal assistant, support, sales and voice agents, and you can
change a registry later without
touching what was already remembered.

You do not have to define predicates. With an
open vocabulary the first use of a
predicate defines it, and with a model configured the MCP tools take plain
text and no predicates appear anywhere:```sh
recall setup -extract-model anthropic:claude-haiku-4-5-20251001
``````text
remember(&quot;I switched from helix to zed last week&quot;)
recall(&quot;which editor do I use?&quot;)  -&gt;  &quot;user prefers editor: zed&quot; (before: helix)
forget(&quot;my editor&quot;)

The model decides how each statement is filed. Once filed, replacement follows
the predicate's rule, every filing is recorded, and a wrong filing is corrected
with one event that every later answer follows. No model reconciles memory on
its own: Recall applies the registry's rules, shows what may conflict, and
lets the agent confirm the rest, so every correction reads back to the rule or
statement that made it. recall mcp -typed serves the typed tools
(remember(subject, predicate, value)) instead. The
developer reference has the details and the
Memory API is the contract.

State

The second half of Recall, with its own contract,
docs/state-api-v1.md. An agent writes down where it is
as it works, and a new process resumes from those records instead of from a
snapshot:

  • Working state: goal, plan, progress, focus, decisions, open questions.
  • Turns, verbatim, and large tool outputs stored by reference.
  • Pointers to where the work lives: a branch, an object key, a process.
  • Actions: each tool call that touches the world, recorded before it runs
    and closed with its result, so a crash between the two is visible and the
    next resume lists the call as unconfirmed instead of repeating it.

Resume takes a lease on the agent id, so one process acts for an agent at a
time, rebuilds the context within a token budget, and renders it as one
briefing for the model:```go
agent, err := client.Resume(ctx, recall.ResumeRequest{AgentID: "coder-1", TokenBudget: 8000})
if err != nil {
return err
}
defer agent.Release(context.Background())

briefing := agent.Resumed().Briefing // hand this to the model


In Python, an agent remembers a fact and records where it is, the process is
killed, and a new process resumes from the records:```python
import os, signal
from polign_recall import Client

with Client(local_dir=&quot;./recall-data&quot;, agent=True, typed=True) as client:
    client.remember(&quot;user&quot;, &quot;project_constraint&quot;, &quot;deploy only on weekdays after 18:00 UTC&quot;)
    with client.resume(&quot;coder-1&quot;) as agent:
        agent.update_working_state(goal=&quot;Move billing to the v2 API&quot;,
                                   plan=[&quot;find call sites&quot;, &quot;migrate them&quot;, &quot;run the tests&quot;])
        agent.record_turn(&quot;user&quot;, &quot;Start with the charge endpoint.&quot;)
        agent.milestone(&quot;call sites found&quot;, progress=&quot;12 call sites listed&quot;)
        os.kill(os.getpid(), signal.SIGKILL)   # dies here, lease unreleased
``````python
import time
from polign_recall import Client

with Client(local_dir=&quot;./recall-data&quot;, agent=True, typed=True) as client:
    agent = client.resume(&quot;coder-1&quot;, token_budget=8000, defer_lease=True)
    print(agent.context.briefing)   # at once: the goal, plan, milestone, turn, and constraint
    while not agent.acquire():      # False until the dead process&#x27;s lease expires
        time.sleep(1)
    agent.record_turn(&quot;assistant&quot;, &quot;Picking up at the charge endpoint.&quot;)

Without defer_lease=True, resume raises lease_held until the crashed
process's lease expires (Python client guide).

The same operations are MCP tools (agent_resume, update_working_state,
record_turn, begin_action, ...) and, on recall serve, HTTP routes at
POST /v1/agent/. Over HTTP the server holds the lease between
requests: resume returns an epoch and every write carries it, so a stale
process cannot write over its successor. The State API is beta; the records it
writes are stable (STABILITY.md). The
resume example kills an agent mid-task and continues it in
a new process.

Serving many agents

recall mcp is one agent, one process. recall serve is the same memory and
state for many agents over HTTP, each inside the namespace its key names. The
server holds the database credentials; agents hold Recall keys.```sh
recall serve -backend polign -url http://polign:23000 -bootstrap-key-file admin.key
recall key create -backend polign -url http://polign:23000 -namespace acme:agent-7 -expires 168h


Each namespace gets its own collection, so nothing a caller sends can reach
another namespace&#x27;s records. `POST /mcp` is MCP over streamable HTTP;
`POST /v1/` takes a memory tool&#x27;s arguments as the body, and
`POST /v1/agent/` a state tool&#x27;s. Any stdio MCP client reaches the
server through `recall connect` with `RECALL_URL` and `RECALL_API_KEY` set.

On Kubernetes a pod needs no key at all. With `recall serve -kubernetes`, it
posts its projected service account token and gets a short-lived key fixed to
its own agent id, which `recall connect` and the Python client obtain and
renew by themselves. The Helm chart is `charts/recall` in
Polign/polign; the
agent-sandbox demo runs it on kind.

On Agent Substrate an actor
needs no key either. With `recall serve -substrate-issuer`, the actor&#x27;s egress
policy has Substrate&#x27;s gateway put a short-lived token for that actor in the
`Authorization` header, and the server gives each actor its own memory. The
agent-substrate example runs it on kind.

## Backends

| | local (default) | polign_db | PostgreSQL + pgvector | MongoDB | Qdrant |
| --- | --- | --- | --- | --- | --- |
| `RECALL_BACKEND` | `local` | `polign` | `pgvector` | `mongodb` | `qdrant` |
| `RECALL_BACKEND_URL` | a directory | `http://host:23000` | `postgres://user:pw@host/db` | `mongodb://user:pw@host/db` | `http://host:6333` |
| Memory, history, as-of | yes | yes | yes | yes | yes |
| Keyword search | yes | yes | yes | yes | no |
| Cached reads | yes | yes | yes | yes | no |
| State API (leases) | yes | yes | yes | yes | no |
```sh
export RECALL_BACKEND=pgvector RECALL_BACKEND_URL=postgres://user:password@localhost:5432/mydb
recall mcp -write

Three settings name the database for every command: -backend, -url and
-key, or the variables above. Everything else, including what each backend
needs and how to add one, is in docs/backends.md.

Benchmark

LongMemEval user-facts subset, 267 questions about a user's own facts,
preferences, updates and dates, with Claude Sonnet 5.5 as reader and judge
and the upstream prompts:

What the reader is given Score
Nothing 6.0
The full chat history 88.0
BM25 over sessions, top 10 89.9
Recall, built-in word search 88.8
Recall with a model embedder (OpenAI text-embedding-3-small, 512 dims) 92.9
Only the sessions that hold the answer 96.6

With word search Recall is even with BM25 overall and behind it on preference
questions (70.0 against 83.3); a model embedder puts it ahead. Recall handed
the reader about 28k tokens per question, against 44k for BM25 and 168k for
the full history. The harness is in eval/longmemeval.

Integrations

Python · pip install polign-recall, then the client guide.
Go · go get github.com/Polign/recall, then the Go library guide.
MCP · Connect any agent to remember, recall and forget.
Claude Code · The Recall plugin: memory across coding sessions.
LangGraph · pip install recall-langgraph to resume LangGraph agents.
LiveKit, Vapi · recall-livekit and recall-vapi for caller memory in voice agents.
Pydantic AI · pip install recall-pydantic-ai for memory tools in Pydantic AI agents.
Vercel AI SDK · The Next.js chat example, one click to deploy.
OpenClaw · @polign/openclaw-recall on npm, the OpenClaw plugin.

Documentation

Developer reference ·
Memory API contract ·
State API contract ·
Backends ·
Connecting through MCP ·
Caching memory reads ·
Exporting and replaying history ·
What is stable and what is beta ·
Development guide ·
Usage statistics

Usage statistics

Release builds send an anonymous heartbeat: version, platform, a random
install ID, and counts of memory operations. Nothing that is remembered is
ever sent. recall telemetry prints exactly what is sent, and
recall telemetry off, RECALL_TELEMETRY=0 or DO_NOT_TRACK=1 turns it
off. TELEMETRY.md lists every field.

Support the project

If Recall kept your agent from acting on a stale fact, a star on this
repository helps other people find it. Bugs, questions and ideas go in
issues.

License

Apache 2.0.

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Recall By Polign 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Recall By Polign 怎么在 Claude、Cursor、VS Code 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Recall By Polign 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Recall By Polign 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Recall By Polign 支持哪些客户端?

资料标注支持 Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Recall By Polign 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-20。