Zaxy — event-sourced agent memory with cited checkout and reversible forgetting (stdio/SSE via PyPI)

MCP文档知识

提供方 syndicalt

文档知识 stdio · 本地进程 OAuth 授权 社区 / 第三方 ClaudeCursorVS CodeGemini CLI
查看接入方式

Zaxy turns agent work into durable, auditable memory: a hash-chained Eventloom log as the source of truth, an embedded temporal knowledge graph for reasoning (local-first, no sidecar; Neo4j/Postgres optional), cited Memory Checkout for compact context, and MCP tools for model-fa

一句话选型结论

按资料字段整理

Zaxy — event-sourced agent memory with cited checkout and reversible forgetting (stdio/SSE via PyPI) 属于文档知识类 MCP 服务器,stdio · 本地进程,OAuth 授权,可直接接入 Claude、Cursor、VS Code 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

支持客户端

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
pipx install zaxy-memory

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

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 python,再按安装命令拉取依赖。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

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

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

知识库读写

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

内容整理

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

选择建议

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

值得选的地方

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

先想清楚的地方

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

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Zaxy — event-sourced agent memory with cited checkout and reversible forgetting (stdio/SSE via PyPI)当前 未标注 stdio · 本地进程 本地部署 有 未标注
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

服务器档案

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

详细介绍

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

Zaxy

Production memory for agent teams that need receipts.

Zaxy turns agent context into an auditable project memory fabric. It captures
parent missions, worker sessions, tool observations, cited findings, conflict
review, approval packets, and accepted merge-back into one durable history that
can be queried, replayed, and inspected.

Under the hood, Zaxy uses Eventloom append-only JSONL as the source of truth and
an embedded LadybugDB graph projection for local reasoning. It is built for agents
that need to remember what happened, cite where it came from, and avoid turning
project state into a pile of markdown files and vector chunks.

The embedded LadybugDB graph projection is the default local runtime.

The plain install uses embedded LadybugDB. Install zaxy-memory[neo4j] only for the
optional Neo4j sidecar, and zaxy-memory[pathlight] only for Pathlight tracing.

Why It Matters

  • Auditable memory: every accepted fact can point back to Eventloom history.
  • Agent-team coordination: parent and worker sessions stay isolated until
    findings are reviewed and merged.
  • Local-first runtime: the default path uses embedded LadybugDB, no Neo4j sidecar.
  • MCP-native integration: Codex, Claude Code, Cursor, VS Code, Hermes Agent,
    LangGraph, CrewAI, and AutoGen can use the same memory interface.

> Benchmark claims withdrawn (2026-07-03). The prior LongMemEval numbers
> were withdrawn: they were produced in oracle mode (mean ~1.9 candidate
> sessions per question, so Recall@5/citation-coverage were ~1.0 by
> construction, not by retrieval) and the preference-question scores rested on a
> hardcoded answer table that has since been removed. Zaxy does not currently
> publish a LongMemEval score. A real, full-haystack LongMemEval run is planned;
> until it lands, treat the earlier 0.956/0.910/1.000 figures as retracted.
> The Harvey LAB claim is pending the same audit.

Quick Start

Install, init, verify```bash

pipx install zaxy-memory
zaxy init
zaxy memory log --eventloom-path .eventloom --limit 5
zaxy memory bootstrap --eventloom-path .eventloom
zaxy doctor --eventloom-path .eventloom


The PyPI distribution is `zaxy-memory`; the import package and console command
are still `zaxy`. Bare `zaxy init` sets up the local embedded graph posture,
repo-local profile, deterministic capture config, genesis event, heartbeat, and
MCP guidance. For Codex, the printed activation launcher starts the managed
capture watcher when the local capture config is present; pass `--capture start`
only when you want init itself to start the watcher before opening Codex. The
default human output is compact and action-first; add `--verbose` when you need
the full setup diagnostics, optional checks, fallback commands, resume guidance,
and notes.
For automation, `zaxy init --json` keeps the raw onboarding fields and adds
`setup.status`, `setup.issues`, `setup.pending`, `readiness.status`,
`readiness.reasons`, `readiness.actions`, and structured
`readiness.action_items` for both commands and non-command review tasks. Each
structured action carries `label`, `command`, original `source`, and `hints`
for compact-output tips such as activation `` replacement and path-stable
command guidance. Installers can render those tips without parsing prose. It also
includes `setup.summary`, `readiness.summary`,
`readiness.required_action_count`, and `readiness.reason_count`, so client UIs
can render compact status without parsing human output. It also
separates `readiness.blocking_diagnostics` from
`readiness.non_blocking_diagnostics` so scripts can distinguish setup
completion, required actions, and advisory doctor warnings before relying on
live memory.

For Codex, `zaxy init --codex-mcp-install auto` is the default. It writes or
reuses the user-level Codex MCP config when that can be done without replacing
an existing `zaxy` server entry. If no safe config target exists, it prints the
copyable `codex mcp add` command. If an existing `zaxy` entry differs, it asks
you to review that config before replacing it because Codex can silently replace
servers with the same name. Use an explicit mode when you need to force one side
of that decision after review:```bash
zaxy init --codex-mcp-install user
# or: zaxy init --codex-mcp-install command

Both Codex paths keep the server workspace-neutral. After init, start or
restart Codex through the printed zaxy activate codex ... --launch command so
the MCP server list and Zaxy activation packet are loaded together. The printed
command includes explicit --eventloom-path and --workspace-root values, so
it still targets the initialized repo when copied from another shell.

Run the single-agent memory example:```bash
python examples/single_agent_memory.py


Your local data lives under `.eventloom/` as one append-only JSONL file per
session.

For Claude Code instead of Codex:```bash
zaxy init . --domain my-project --preset local-claude --infra check

For Hermes Agent:```bash
zaxy ide-config hermes --install


For repository development, use `pip install -e ".[dev]"`, `./scripts/setup.sh`,
and `zaxy status`. Start Docker sidecars only for integration tests or explicit
backend comparisons. Production setup writes Docker secret files under
`./secrets/`; see docs/deployment.md.

## Architecture```
Agent (LangGraph / Any MCP Client)
    |
    v
MCP Server — memory_append / memory_query / memory_feedback / memory_replay / memory_invalidate
    |
    v
Eventloom (immutable JSONL log)  →  Hybrid Extraction  →  Embedded LadybugDB graph
    |                                                               |
    +—————— Optional Pathlight traces ———————————————→  Query Router
                                                              |
                                                    Hybrid Retrieval
                                                    (exact + BM25 + vector + traversal)

Zaxy also includes an observe-only OpenAI-compatible packet analyzer for model
call provenance. It forwards packets to one configured upstream endpoint and
records llm.packet.completed events to Eventloom without acting as a router.
See LLM Packet Analyzer.

Public Site and Documentation

  • Public static site: site/index.html
  • Why Zaxy: docs/why-zaxy.md
  • Getting started: docs/getting-started.md
  • MCP quickstart: docs/mcp-quickstart.md
  • Architecture: docs/architecture.md
  • Configuration: docs/configuration.md
  • MCP interface: docs/mcp.md
  • Memory export contract: docs/export-contract.md
  • Eventloom contract: docs/eventloom.md
  • Graph schema: docs/graph-schema.md
  • Retrieval: docs/retrieval.md
  • Benchmarks: docs/benchmarks.md
  • LLM packet analyzer: docs/packet-analyzer.md
  • Embeddings: docs/embeddings.md
  • Security: docs/security.md
  • Operations and deployment: docs/operations.md, docs/deployment.md, docs/runbook.md
  • Python API: docs/api.md
  • Stability commitment: docs/stability-commitment.md
  • Migration guide: docs/migration.md
  • Archived benchmark iteration notes, release drafts, and research notes live
    under docs/archive/, docs/announcements/, and docs/research/.
  • Contributing: CONTRIBUTING.md

Key Features

  • Immutable audit trail: Eventloom append-only JSONL with SHA-256 hash chains.
  • Bi-temporal graph: Facts have validity windows (valid_from, valid_to).
  • Hybrid extraction: Rule-based for typed events (60–80% cost reduction), LLM fallback.
  • Hybrid retrieval: Exact + keyword + vector + graph traversal with configurable fusion weights.
  • Session sharding: One Eventloom log per agent/session, with a shared graph.
  • MCP-native: Drop-in memory for any MCP-compatible agent framework over stdio or SSE.
  • Observable: Optional Pathlight traces, breakpoints, and diff support via zaxy-memory[pathlight].
  • Hardened local defaults: bounded MCP inputs, safe session IDs, no-sidecar embedded graph projection, and optional admin token support for replay/invalidation.

Project Structure

File Purpose
src/zaxy/event.py Eventloom JSONL I/O + hash chain integrity
src/zaxy/extract.py Hybrid extraction engine + rule registry
src/zaxy/embedded_graph_store.py Embedded LadybugDB projection store
src/zaxy/graph.py Optional Neo4j bi-temporal wrapper via zaxy-memory[neo4j]
src/zaxy/query.py Hybrid retrieval router
src/zaxy/mcp_server.py MCP stdio/SSE server
src/zaxy/trace.py Optional Pathlight observability hooks
src/zaxy/core.py MemoryFabric orchestrator
src/zaxy/session.py Per-session Eventloom log manager
src/zaxy/security.py Shared validation and input bounds
src/zaxy/__main__.py CLI (zaxy serve, zaxy replay, etc.)

Production Secrets

Zaxy supports Docker/Kubernetes-style secret files for sensitive settings:

Variable Secret-file variant
NEO4J_PASSWORD NEO4J_PASSWORD_FILE
MCP_ADMIN_TOKEN MCP_ADMIN_TOKEN_FILE
PATHLIGHT_ACCESS_TOKEN PATHLIGHT_ACCESS_TOKEN_FILE

Direct environment variables take precedence over their *_FILE variants.
Use docker-compose.prod.yml as the production compose baseline.

Development

  • Tests first (Karpathy rule). Every public function has a test.
  • Unit tests mock external services. Integration tests use Docker for optional sidecar backends.
  • Coverage gate: ≥92% enforced by CI.
  • Lint/format: ruff. Types: mypy.```bash

Run full suite with coverage gate

pytest

Run integration tests (requires Docker)

./scripts/generate-certs.sh .certs
docker compose --profile integration up -d neo4j-test neo4j-tls
pytest -m integration --no-cov

Lint and type-check

ruff check src tests
mypy src

LongMemEval benchmark numbers are WITHDRAWN (see the note at the top of this

README). The --dataset .cache/.../longmemeval_oracle.json path only exercises

the answer step over pre-selected gold sessions (oracle mode) and does NOT

measure retrieval on the full LongMemEval haystack; do not publish figures from

it as a LongMemEval score. A real full-haystack harness is TBD.

Harvey LAB external memory-ablation comparison

Consumes externally generated Harvey normalized-result artifacts for Zaxy;

does not reuse LongMemEval statistics as legal-agent benchmark evidence.

Current full external Harvey LAB evidence:

reports/benchmarks/harvey-lab-memory-ablation/publishable-statistics.md

reports/benchmarks/harvey-lab-memory-ablation/harvey-lab-benchmark.json

10/10 tasks, mean criterion pass rate 0.788, +0.184 vs regular/no-memory,

+0.081 vs article-best task rows, 9/10 wins vs article-best rows.

Production deployment preflight

scripts/validate-deployment.sh --root .

Build and validate Python release artifacts

scripts/build-dist.sh --root .

Verify local release metadata, PyPI Trusted Publishing, and LangGraph smoke

zaxy doctor --release-smoke

Validate public site and documentation links

scripts/validate-docs.sh --root .

Clean-repo beta UAT: install into a throwaway workspace and verify init,

bootstrap, deterministic capture, doctor, and memory checkout.

scripts/beta-uat.sh

Summarize beta readiness gates without external services.

zaxy doctor --beta-readiness

Go-live release gate

scripts/release-check.sh --root .
```

The full suite must stay at or above 92% coverage before a sprint is complete.

Release Publishing

The PyPI distribution name is zaxy-memory because zaxy is already occupied
on PyPI. Published releases build from GitHub Actions and upload to
using PyPI Trusted Publishing with
GitHub OIDC. The import package and console command remain zaxy.

Before publishing, run zaxy doctor --release-smoke to verify the package
version, changelog entry, release workflow, tokenless publishing posture, and
dependency-light LangGraph example.

License

MIT

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Zaxy — event-sourced agent memory with cited checkout and reversible forgetting (stdio/SSE via PyPI) 怎么安装?

在客户端按下面的安装命令接入:pipx install zaxy-memory。装完在客户端配置里引用同一个包或端点。

Zaxy — event-sourced agent memory with cited checkout and reversible forgetting (stdio/SSE via PyPI) 怎么在 Claude、Cursor、VS Code 里配置?

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

Zaxy — event-sourced agent memory with cited checkout and reversible forgetting (stdio/SSE via PyPI) 收费吗?

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

Zaxy — event-sourced agent memory with cited checkout and reversible forgetting (stdio/SSE via PyPI) 需要 API Key 吗?

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

Zaxy — event-sourced agent memory with cited checkout and reversible forgetting (stdio/SSE via PyPI) 支持哪些客户端?

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

Zaxy — event-sourced agent memory with cited checkout and reversible forgetting (stdio/SSE via PyPI) 需要什么运行环境?

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

Zaxy — event-sourced agent memory with cited checkout and reversible forgetting (stdio/SSE via PyPI) 是本地还是远程?

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

热门专题

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

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