Fraise

MCP文档知识

提供方 未标注

文档知识 stdio · 本地进程 会话登录 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

面向AI代理的内存知识存储

一句话选型结论

按资料字段整理

Fraise 属于文档知识类 MCP 服务器,stdio · 本地进程,会话登录,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

支持客户端

适用场景

记忆

安装与配置

stdio · 本地进程 会话登录
客户端在本机拉起子进程,数据不出本机
docker run -p 127.0.0.1:9876:9876 ghcr.io/fraisehq/fraise:latest

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

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

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

知识库读写

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

内容整理

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

选择建议

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

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Fraise当前 未标注 stdio · 本地进程 本地部署 有 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

服务器档案

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

详细介绍

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

Fraise

Docs
Discord
Query language

Fraise is a memory database for AI agents. One they query directly, in a language built for tokens, not humans.```text
remember 'acme moved to annual billing' topic:billing entity:acme

recall billing entity:acme since:30d top:5


Two verbs. One binary. No infrastructure to run.

## Install```sh
brew install fraisehq/tap/fraise
brew services start fraise
curl -X POST localhost:9876/api/v1/q -H 'content-type: application/json' \
  -d "{\"query\": \"remember 'the parrot is turquoise' topic:color\"}"

Linux packages, Docker, go install and signed release binaries are all in Get Started below.

> Read Durability before you deploy. Persistence is issue #171 and the next major piece of work.

How it compares

Measured on LoCoMo — 10 multi-session conversations, 1,986 questions — with every system ingesting the same conversations, using the same extraction model and the same embedding model, and answering the same questions. k=10, full data, latest run per system as of 2026-10-11.

system retrieval recall p50 search memory tokens
fraise 0.3.3 0.910 0.185 s 7,453,109
hindsight 0.9.2 0.913 5.836 s 1,688,873
everos 1.2.3 0.897 0.376 s 10,030,966
letta 0.16.8 0.897 0.349 s 226,854
mem0 2.0.18 0.886 0.576 s 4,120,078
memos 2.0.33 0.865 0.307 s 4,000,552
graphiti 0.30.2 0.828 0.290 s 9,861,973
cognee 1.5.3 0.790 6.273 s 8,526,019
langmem 0.0.30 0.783 0.227 s 1,078,110

Fraise comes within 0.003 of the best recall, 31× faster than the one system that reaches it. Near enough the same evidence, in a fraction of the time. The token column is the price of that recall: the extractor (fraise-sdk 0.2.0) reads each message beside what the graph already holds, and that context is where the recall came from.

These come from agent-memory-benchmarks, an open harness — precision, recall and F1 across k ∈ {1, 3, 5, 10}, per category, every run tagged and reproducible from the tag. The full tables are in its RESULTS.md.

Why Fraise

  • A query language agents can actually write. FQL has two verbs — remember and recall — and one way to say each thing. Fewer degrees of freedom means fewer ways for a model to get it wrong, and fewer tokens spent saying it.
  • Hybrid retrieval. Facts are indexed for full-text, graph, and (optionally) vector search. One query, ranked across all three.
  • Temporal by default. Recent memories outrank older ones, so recall is recency-aware without asking for it.
  • The fastest system measured. 0.185 s p50 on LoCoMo, ahead of every other system and 31× faster than the one with matching recall. Remember and recall mid-step, while the user waits.
  • No infrastructure. A single binary. No database to provision, no service to stand up beside it.
  • Open source, MIT.

Status

v0.3.3. The core loop works end to end and the install paths are verified on clean machines. The benchmark row above was produced from this release. 0.4.0 (late October) changes the scorer and adds explain and describe; 0.5.0 (November) is persistence and forget.

Good for building agent memory today. Not yet for long term production use.

How it works

Fraise stores knowledge as a temporal memory graph built from three kinds of node:

  • facts — the things you remember, one statement each
  • entities — who or what a fact mentions
  • topics — what a fact is about

Edges connect facts to the entities they mention and the topics they're about, so a query can start from either side. A recall finds seed facts by text and, optionally, by vector similarity; a recall that names only topics or entities starts from the facts filed under them. With depth:1 or depth:2, a named topic or entity whose facts matched better than its size predicts passes that evidence on to the rest of its facts. Results are ranked by relevance and recency, and the best top come back.

Ranking is not a black box: a fact's score folds its own match strength with what it receives through anchors carrying more mass than their size would predict, each measured against the facts the recall could return. The background rate that "more" is measured against is estimated per query, from the part of the graph the query touched, so there is no relevance constant to tune. Hybrid retrieval has the full model.

A single Fraise instance holds several independent memory graphs (8 by default), addressed with @N — one per user, per session, per agent, however you like.

Get Started

Fraise is a single binary — no database to provision, nothing to configure. Every route below leaves you with a server listening on port 9876, at localhost:9876.

With Homebrew```sh

brew install fraisehq/tap/fraise
brew services start fraise


The service survives crashes and restarts on login (`keep_alive`), logs to `$(brew --prefix)/var/log/fraise.log`, and reads its config from `$(brew --prefix)/etc/fraise/fraise.config.toml` — installed with every setting commented at its default, and never overwritten on upgrade.

### With Docker```sh
docker run -p 127.0.0.1:9876:9876 ghcr.io/fraisehq/fraise:latest

Published tags: one per release, latest for the newest stable, edge for the tip of main, and an immutable full-commit-SHA tag for every merge that touches the server.

Images are built with SLSA provenance, verifiable without pulling:```sh
gh attestation verify oci://ghcr.io/fraisehq/fraise:latest --repo FraiseHQ/fraise


### With Go```sh
go install github.com/FraiseHQ/fraise/cmd/server@latest
"$(go env GOPATH)/bin/server"

The binary installs as server, after its package path — rename it to fraise if that reads better.

Nothing further is needed to trust this: the Go toolchain checks every module download against the public checksum transparency log, and your own machine compiles the result.

Linux packages

.deb and .rpm packages ship with every release, with a systemd user unit:```sh
VERSION=0.3.0
ARCH=$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/')
curl -sSfLO "https://github.com/FraiseHQ/fraise/releases/download/v${VERSION}/fraise_${VERSION}linux${ARCH}.deb"
sudo dpkg -i "fraise_${VERSION}linux${ARCH}.deb"
systemctl --user enable --now fraise


Logs go to the journal (`journalctl --user -u fraise -f`), and the unit reads `~/.config/fraise/fraise.config.toml` when present — a shipped default with every setting commented lives at `/etc/fraise/fraise.config.toml` to copy from. For agents that outlive your login session, let the user manager keep running: `loginctl enable-linger $USER`. A system-level (shared server) variant of the unit is described in Running as a managed service.

### From a release binary```sh
VERSION=0.3.0
OS=$(uname -s | tr '[:upper:]' '[:lower:]')                # linux | darwin
ARCH=$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/')  # amd64 | arm64
ASSET="fraise_${VERSION}_${OS}_${ARCH}.tar.gz"
BASE="https://github.com/FraiseHQ/fraise/releases/download/v${VERSION}"

curl -sSfLO "${BASE}/${ASSET}"
tar xzf "$ASSET"
./fraise

Windows builds ship as .zip under the same naming scheme.

Verify a release

Releases carry a cosign signature over checksums.txt, using the same VERSION and BASE as above:```sh
curl -sSfLO "${BASE}/checksums.txt"
curl -sSfLO "${BASE}/checksums.txt.sigstore.json"

1. the bundle proves checksums.txt came from this repo's release workflow

cosign verify-blob \
--bundle checksums.txt.sigstore.json \
--certificate-identity-regexp 'https://github.com/FraiseHQ/fraise/.github/workflows/go.yaml@refs/tags/v.*' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
checksums.txt

2. checksums.txt proves your archive is the one it covers

sha256sum --ignore-missing -c checksums.txt # macOS: shasum -a 256 --ignore-missing -c


### Run from source```sh
git clone https://github.com/FraiseHQ/fraise
cd fraise
make dev

Your first memory```sh

curl -X POST localhost:9876/api/v1/q \
-H 'content-type: application/json' \
-d "{\"query\": \"remember 'the parrot is turquoise' topic:color\"}"

curl -X POST localhost:9876/api/v1/q \
-H 'content-type: application/json' \
-d '{"query":"recall parrot"}'
``````json
{
"results": {
"count": 1,
"hits": [
{ "value": "the parrot is turquoise", "timestamp": "...", "score": 0.2867 }
]
}
}


## Use it from an agent

### MCP

`fraise-mcp` is a stdio MCP server for a running daemon, so any MCP client can remember and recall. It exposes two tools, `recall` and `remember`, each taking one FQL statement, and embeds every statement's text locally, so retrieval is hybrid (text, graph and vector) out of the box while the model writes plain FQL. It runs with uv's `uvx`, with nothing else to install, and needs no flags when the daemon is on its default address.

Start the daemon first (`brew services start fraise`, or `systemctl --user start fraise` on Linux), then register the server with whichever coding agent you use.

#### Claude Code```sh
claude mcp add fraise -- uvx fraise-mcp

That registers it for the current project; add --scope user to make it available in every project instead.

Codex```sh

codex mcp add fraise -- uvx fraise-mcp


Or write it into `~/.codex/config.toml` directly:```toml
[mcp_servers.fraise]
command = "uvx"
args = ["fraise-mcp"]

OpenCode

Add it to opencode.json in your project root:```json
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fraise": {
"type": "local",
"command": ["uvx", "fraise-mcp"]
}
}
}


#### Any other client```json
{
  "mcpServers": {
    "fraise": { "command": "uvx", "args": ["fraise-mcp"] }
  }
}

The fraise binary also carries the two tools without the embedding: fraise mcp sends each statement as written, searching by text and graph, with no Python. See MCP for the embedding model, the settings, and the built-in bridge.

The server describes itself over MCP: each tool arrives with a description and a schema for its one argument — the FQL shapes, a worked example, what a score means — so a client knows what recall and remember do and how to call them without being told. What a tool description cannot carry is the policy: the habit of reaching for memory unprompted, and the judgement about what is worth keeping. That belongs in the file your agent already reads — CLAUDE.md for Claude Code, AGENTS.md for Codex and OpenCode — and two habits are enough: recall before answering anything that leans on earlier decisions or preferences, and remember only facts that will still matter in a later session, one self-contained fact per call with the topics and entities that will make it findable.

SDKs

Python (sdk/python) — the only SDK today:```sh
pip install --pre fraise-sdk
``````python
from fraise_sdk import FraiseClient

with FraiseClient("http://localhost:9876") as fraise:
fraise.remember("the parrot is turquoise", topics=["color"])
for hit in fraise.recall("parrot", top=5):
print(hit.value, hit.score)


The Python SDK is dependency-light and supports vector search when you supply an embedder. See its README for embeddings and the full API.

**TypeScript** — not available yet (#179). Until it lands, TypeScript callers use `fraise mcp` or talk to the HTTP endpoint directly; it is two verbs over one route, so a client is a short wrapper around `fetch`. See the HTTP API.

### Claude Agent SDK

The Python SDK ships memory tools for the Claude Agent SDK, exposed as an in-process MCP server so the agent decides *what* to store and recall:```python
from claude_agent_sdk import ClaudeAgentOptions
from fraise_sdk import FraiseClient
from fraise_sdk.integrations.claude_agents import memory_server, allowed_tools

fraise = FraiseClient("http://localhost:9876")
options = ClaudeAgentOptions(
    system_prompt="Remember durable facts the user shares, and recall them when relevant.",
    mcp_servers={"fraise_memory": memory_server(fraise)},
    allowed_tools=allowed_tools(),
)

A complete, Docker-runnable agent lives in examples/claude-agent-sdk.

OpenAI Agents SDK

memory_tools(client) returns bound recall and remember tools:```python
from agents import Agent, Runner
from fraise_sdk import FraiseClient
from fraise_sdk.integrations.openai_agents import memory_tools

fraise = FraiseClient("http://localhost:9876")
agent = Agent(
name="Assistant",
instructions="Remember durable facts the user shares, and recall them when relevant.",
tools=memory_tools(fraise),
)

result = Runner.run_sync(agent, "My favourite colour is orange.")
print(result.final_output)
```

A complete, Docker-runnable agent lives in examples/openai-agents.

References

  • Roadmap
  • Documentation
  • Architecture
  • Query language grammar
  • Release process
  • Issues

Contributing

Contributions are welcome — see CONTRIBUTING.md for how to build, test, and submit changes.

Code of Conduct

This project follows the Contributor Covenant.

Community

Questions, ideas, or building something with Fraise? Join the Discord. Bugs and feature requests belong in issues so they don't get lost.

License

MIT — see LICENSE.

常见问题

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

在客户端按下面的安装命令接入:docker run -p 127.0.0.1:9876:9876 ghcr.io/fraisehq/fraise:latest。装完在客户端配置里引用同一个包或端点。

Fraise 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Fraise 收费吗?

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

Fraise 需要 API Key 吗?

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

Fraise 支持哪些客户端?

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

Fraise 能提供哪些能力?

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

Fraise 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

Fraise 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

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

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