ES Archive

MCP文档知识

提供方 未标注

文档知识 Streamable HTTP 会话登录 社区 / 第三方 Claude DesktopClaudeCursorVS Code

为Claude和ChatGPT提供持久、可搜索的存档和记忆。原生macOS MCP服务器,从App Store安装,无需设置。私密、本地且开源。

一句话选型结论

按资料字段整理

ES Archive 属于文档知识类 MCP 服务器,Streamable HTTP,会话登录,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

支持客户端

适用场景

记忆

安装与配置

Streamable HTTP 会话登录
新一代远程传输,替代 SSE
  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

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

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

知识库读写

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

内容整理

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

选择建议

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

值得选的地方

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

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
ES Archive当前 未标注 Streamable HTTP 支持远程部署 无 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

服务器档案

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

详细介绍

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

ES Archive

An AI-first archive server for Claude, ChatGPT, LM Studio, and any other MCP-compatible client.

Persistent archive that the AI owns: store, retrieve, organize, curate, and forget across sessions. The Archive is the collection; an entry is what a session writes into it. Built natively in Objective-C with Core Data, on-device multilingual Core ML embeddings, and optional CloudKit sync. Designed and optimized for Claude; Claude Desktop, ChatGPT desktop, and LM Studio all connect to the same server over stdio, each as its own persona, in one shared archive.

ES Archive was known as ES Memory through version 3.3.3. The rename was a clean cut, no aliases: the MCP tools (memory_* → archive_*), bundle identifiers, and app group all changed. The CloudKit container and sync schema did not, so a synced archive re-downloads on first launch, and legacy .esmemory backups still open.

Read more about the technology and philosophy behind ES Archive on alpharecursion.com.

Two ways to run it

ES Archive is one engine that ships in two forms, built as two targets in this repository:

  • ES Archive MCP — a stdio server, and the recommended install. Any client that can launch a stdio MCP server spawns it directly: Claude Desktop, Claude Code, ChatGPT desktop, LM Studio, Codex. No localhost port, no network listener. Concurrent sessions — across all of those clients at once — share one in-process engine over a local UNIX-domain socket: the first to start hosts it, the rest relay, so N sessions cost one engine, not N (see Architecture). Each session declares its persona at launch with --author, so Claude, ChatGPT, and a local model each write as themselves into the same archive.
  • ES Archive Server — the HTTP app. Hosts the same engine behind a hardened localhost web server for clients that speak MCP-over-HTTP or SSE (curl, a cloudflared tunnel, HTTP-only clients), with port-bound personas and per-port authentication. Use this when you need /sse or HTTP clients, or remote access.

Both read and write the same kind of archive; each keeps its own local store.

Requirements

  • macOS 26 (Tahoe) or later
  • ES Archive MCP: any client that launches stdio MCP servers — tested with Claude Desktop, Claude Code, ChatGPT desktop, LM Studio, and Codex
  • ES Archive Server: any MCP-over-HTTP or SSE client

Install (ES Archive MCP, recommended)

  1. Install ES Archive MCP from the Mac App Store.
  2. Connect the client(s) you use — see below. Each is a one-time step.

That's all. The client launches the server on demand and the archive tools appear automatically — no separate app to keep running, nothing listening on a port. While it's running the host presents the app's UI — a Dock app by default (Archive Scope, persona management, backup/restore), or a menu-bar item if you switch to Minimal mode in Settings.

Every client points at the same executable:```
/Applications/ES Archive MCP.app/Contents/MacOS/ES Archive MCP


and passes `--author ` to say who is writing. The name is the persona: it is stamped on every entry the session stores and scopes what the session reads, so each assistant keeps to its own slice of the shared archive. Without the flag the session writes as **Claude**.

### Claude Desktop

In ES Archive MCP, choose **Help ▸ Connect ES Archive…** and click **Connect to Claude**. That builds a connector pointing at this copy of the app and hands it to Claude Desktop, which asks you to approve the install.

### ChatGPT desktop

ChatGPT's desktop app can launch stdio MCP servers directly. In ChatGPT, open **Settings → Plugins → MCPs → Add**. The **Connect to a custom MCP** dialog opens with the **Type** toggle already on **STDIO** (the other option, Streamable HTTP, is for the Server app). Fill in:

| Field | Value |
|---|---|
| Name | `ES Archive` (any name you like) |
| Type | **STDIO** (the default) |
| Command to launch | `/Applications/ES Archive MCP.app/Contents/MacOS/ES Archive MCP` |
| Arguments | `--author` and `ChatGPT` — one argument per row, using **Add argument** for the second |
| Environment variables, passthrough, working directory | leave empty |

Save, then start a new conversation; the `archive_*` tools appear as a plugin. Use whatever persona name you like in place of `ChatGPT` — that is the name entries will carry. To change the arguments later, open the server from the MCPs tab; switching between STDIO and Streamable HTTP requires an uninstall and re-add. Note that this is a recent ChatGPT feature and much of the older advice online (HTTP-only connectors, developer mode) no longer applies.

### LM Studio

In ES Archive MCP, choose **Help ▸ Connect ES Archive…** and click **Copy MCP Configuration**, then in LM Studio choose **Program ▸ Edit mcp.json** and paste. Add an author for the model you run, and load a model that supports tool use:```json
{
  "mcpServers": {
    "es-archive": {
      "command": "/Applications/ES Archive MCP.app/Contents/MacOS/ES Archive MCP",
      "args": ["--author", "Gemma"]
    }
  }
}

Claude Code```sh

claude mcp add es-archive -- "/Applications/ES Archive MCP.app/Contents/MacOS/ES Archive MCP" --author Claude


### Any other stdio client

The LM Studio snippet is plain MCP-over-stdio. Any client that can launch a command with arguments (Codex, editors, agent frameworks) uses the same executable path and `--author`.

ES Archive MCP is distributed through the **Mac App Store**, sandboxed like every App Store app. All data stays on your Mac; if you're signed into iCloud it syncs through your own private CloudKit database, and nothing else leaves the machine.

## Build from source

The on-device embedder is a **git submodule**, and the two dependency projects are cloned **next to** the repository so other projects can share them:```sh
git clone --recurse-submodules https://github.com/apocryphx/ES-Archive.git
git clone https://github.com/apocryphx/ObjCTokenizer.git
git clone https://github.com/apocryphx/GCDWebServer.git

If you already have a clone without the submodule:```sh
git submodule update --init


The embedder submodule pulls ~220 MB of model weights and tokenizer through **Git LFS**, so install it once beforehand (`brew install git-lfs && git lfs install`).

| Dependency | Path | What it is |
|---|---|---|
| embeddinggemma-300m-qat-q4_0-coreml | `ES_Archive/Embedders/embeddinggemma-300m-qat-q4_0-coreml` (submodule) | EmbeddingGemma Core ML package + tokenizer (Hugging Face, LFS) |
| ObjCTokenizer | `../ObjCTokenizer` | HuggingFace-compatible tokenizer in Objective-C |
| GCDWebServer | `../GCDWebServer` | Hardened localhost HTTP server for ES Archive Server |

Open **`ES Archive.xcodeproj`** (it references both dependency projects as subprojects) and build the `ES Archive MCP` or `ES Archive Server` scheme. A build phase verifies the embedder model landed in the bundle and fails red if the submodule is missing.

To keep the submodule moving with the main repo on every pull, set once per clone:```sh
git config submodule.recurse true

What it does

ES Archive exposes 22 MCP tools. Most retrieval and curation runs through archive_cli, a Unix-pipeline surface — compose operations with · the way you would in a shell (lfind --tag "X" · w2vgrep "concept" · head 5); run archive_cli("man") for the full vocabulary. The rest are direct tools:

  • Storage — archive_store, archive_read, archive_update, archive_erase
  • Retrieval — archive_search (semantic, with optional recency weighting), archive_grep (line-level pattern search — the matching passages with context, not just which entries contain a string), archive_timeline, archive_tagged
  • Pipeline — archive_cli (composable surface), archive_pipeline (its underlying executor)
  • Discovery — archive_discover (hubs, orphans, forgotten, and other archive structures)
  • Graph — archive_link, archive_unlink, archive_links, archive_tag, archive_untag, archive_tags
  • Annotation & history — archive_comment, archive_reference, archive_revisions
  • Identity & upkeep — archive_author_list, archive_maintenance

Tags are deliberately curated — every tag's existence is an authorial judgment, not an automatic extraction. On archive_store, the server returns similarity scores against existing entries as a behavioral cue against duplication.

Skills

The tools are the instrument; the skills are how an assistant learns to play it. The repository carries two complete suites in skills/, each documenting the same tool surface in its own voice, and each owned and edited only by the assistant it is written for:

Suite Written for Skills
skills/claude/ Claude Desktop, Claude Code, claude.ai es-archive-overview (orientation, loads the rest), -store, -research, -curate, -discover, -toml
skills/codex/ ChatGPT desktop and Codex codex-es-archive (orientation), -store, -research, -curate, -discover, -records, -visitor (reading another AI's archive)

The skills are versioned next to the code they describe so that a tool change and its skill change land in the same commit. Both apps bundle the Claude suite at build time and install it from the Install Claude Skills… card of the Connect window (Help ▸ Connect ES Archive…): each skill has a Read button to see its text and an Install button that hands it to Claude Desktop for confirmation and shows a checkmark once done. For a developer machine, scripts/sync-skills.sh copies the Claude suite to ~/.claude/skills and packs .skill files for claude.ai, and copies the Codex suite to ~/.codex/skills, where both Codex and ChatGPT desktop (Settings → Plugins → Skills) pick it up. See skills/README.md.

Storage and embeddings

Entries are stored locally in Core Data. Vector embeddings are computed on-device with EmbeddingGemma — Google's embeddinggemma-300m, quantized to int4 (768-dimensional) — via Core ML. It is multilingual across 100+ languages, so a query in one language reaches entries written in another; each entry is embedded with its title alongside its summary for sharper retrieval. CloudKit sync across your devices is optional — without iCloud, ES Archive works fully offline, and with it, data stays within your iCloud account. No third-party services, no telemetry.

Archive Scope

Both apps include a visual layer that renders the Archive as a force-directed graph. Nodes are entries, edges are explicit links and similarity connections, color encodes access frequency. Each entry draws one similarity edge to its single nearest neighbor, and small clusters that would otherwise float free are bridged into the main body, so the graph reads as one connected whole rather than scattered fragments. A second tab shows tags as an Archimedean spiral, sized by frequency. The views update live as the Archive changes and as tools are called — you can watch new entries find their place, and see when sustained engagement with a topic produces a hub.

Personas

An ES Archive persona is an author: a name that is stamped on everything a session writes and that scopes everything it reads. Several assistants can share one archive without seeing or overwriting each other's entries, and the tags, links, and Archive Scope graph stay one shared structure.

The stdio ES Archive MCP scopes a persona per connection: each session declares its author with --author at launch. That is how Claude Desktop, ChatGPT, and LM Studio coexist on one machine — three clients, three personas, one engine, one archive. Its Settings pane lists the Archive's personas to delete or merge them (merge renames an author across all of its records, which is how you fold a misnamed persona into the right one).

The HTTP ES Archive Server binds personas to ports instead: the port a request arrives on is its identity, so authorship is stamped from the channel rather than asserted by the client, and misattribution is structurally impossible. Personas are managed in Settings → Personas — every author already in the Archive is listed with its record count; from there you can assign a port to serve a persona, create a new one, rename or merge an author, or delete a persona along with its records. Each port can independently require a Cloudflare Access JWT, so a persona exposed over a cloudflared tunnel sits behind edge authentication while a local-only persona stays open. A read-only GET /personas directory lets a client discover which port serves which persona before connecting. Port-bound personas, persona creation, and per-port JWT stay exclusive to the Server app.

Architecture

The engine — the Core Data stack, the on-device embedder, vector search, and every MCP tool implementation — is shared by both targets. What differs is the transport:

  • ES Archive MCP speaks MCP as newline-delimited JSON-RPC over stdio, and N concurrent sessions — whichever clients spawned them — share one engine rather than N. The first session to start binds a UNIX-domain socket in the shared App Group container and hosts the engine in-process; every other session connects to that host, declares its --author, and relays its requests over the socket, never loading its own Core Data stack or embedder (≈30 MB per relay vs. ≈550 MB for the one host). The election is the bind() itself — kernel-arbitrated, no daemon, App-Store-safe (see design-decisions/socket-election.md). The host also owns the single GUI; relays stay headless and exit when their host does, so nothing lingers. There is no HTTP listener anywhere in the target. Shutdown is stdin EOF or SIGTERM, draining cleanly before the store is saved.
  • ES Archive Server hosts the same engine behind a localhost HTTP server — GCDWebServer (a sibling dependency), hardened with security fixes documented in CHANGES-2026-05-09.md and CHANGES-2026-04-25.md — binding to 127.0.0.1 only, one listener per persona. It accepts no external connections; remote access, when wanted, is delegated to a cloudflared tunnel with per-port Cloudflare Access authentication.

ES Archive ships through the Mac App Store only; packaging/ holds the App Review notes and the ChatGPT/Codex plugin.

Why Objective-C

ES Archive is written in Objective-C throughout — a deliberate choice, not a legacy constraint. Core Data, CloudKit, and GCDWebServer compose cleanly in Objective-C in ways that Swift's strict type system makes awkward; the dynamic dispatch model fits a server that routes heterogeneous MCP tool calls at runtime. The codebase has no Swift dependencies and no bridging headers.

The practical consequence: the contributor surface is small by design. This is not a project looking for pull requests. It is a working instrument, published so that developers who want to understand the architecture can read it.

Status

ES Archive has been in active development for over a year (as ES Memory until August 2026), used by its author daily and built in collaboration with Claude across many sessions. It is released publicly as part of the alpharecursion research program. The current release is 3.3.14 for both ES Archive MCP (stdio) and ES Archive Server (HTTP); ES Archive MCP is on the Mac App Store, approved September 22, 2026. The tool API listed above is stable; new tools may be added but existing ones will not be removed without notice.

Support

Questions, bug reports and feature requests go to the Issues page. Search first — the answer may already be there — then open a new issue with the app (MCP or Server), its version from the About panel, and what you expected to happen. The in-app help book (Help ▸ ES Archive Help) covers setup, connecting clients, personas and troubleshooting. Your archive stays on your Mac and in your iCloud account; see PRIVACY.md.

License

MIT. See LICENSE for full text. The GCDWebServer dependency retains its original BSD 3-Clause license; see its README.

Author

Kolja Wawrowsky — alpharecursion.com · twilighttales.art

常见问题

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

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

ES Archive 怎么在 Claude Desktop、Claude、Cursor 里配置?

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

ES Archive 收费吗?

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

ES Archive 需要 API Key 吗?

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

ES Archive 支持哪些客户端?

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

ES Archive 能提供哪些能力?

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

ES Archive 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

ES Archive 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为Streamable HTTP。

热门专题

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

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