Engram

io.github.tomcat65由 GitHub 账号 tomcat65 发布v0.1.2更新于 Oct 27, 2026

Coordination bus + shared truth for AI agent fleets — self-hosted MCP server + stdio bridge.

发布方自己的服务：Engram

已验证STDIO仅桌面知识与记忆沟通与协作 AI 与机器学习

服务详情

标识符: io.github.tomcat65/engram
传输: STDIO
运行时: Desktop only
信任: Verified
发布于: Sep 16, 2026

安全提示

MCP 服务会接收对话中的工具调用请求，并可能执行外部操作。启用前请先了解该服务能做什么，并只授予它所需的权限。

注册中心已验证此条目所属的 GitHub 账号 tomcat65。这并不表明该账号就是产品方。

SourceWeft 的检查只涵盖条目是否完整、端点是否响应；不审查服务器的代码，也不审查其工具的行为。

在 README 中添加徽章

向读者展示该 MCP 服务已收录于 SourceWeft，徽章链接到本页。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.tomcat65%2Fengram.svg)](https://sourceweft.com/mcp/io.github.tomcat65%2Fengram?utm_source=readme&utm_medium=badge)

概览

AI 生成的概览

自托管的协调总线与共享知识图谱，让多个 AI 编码代理共享状态、互相发消息，并在会话之间恢复上下文。

可以做什么: 共享由实体、观察和关系构成的知识图谱，支持取代机制与服务端当前状态解析
在代理之间发送定向或按能力匹配的消息，支持消息取代、已读状态以及原子确认加归档
用一次带预算的 resume 调用恢复会话，用 checkpoint 捕获结构化状态，并发写入时分支而非覆盖
把冲突以分支头形式暴露出来，而不是静默解决
遵循已发布的 Adaptive Coordination Protocol 规范与实操教程来组织多代理协作
适用场景: 适合多个 AI 编码代理或框架在同一项目上协作、需要共享同一份当前事实、交接工作或让上下文跨会话保留的场景。单个代理只需要简单记忆存储时意义不大。
运行要求: 以本地 stdio 桥接（npm 包）形式在桌面运行，另需自行托管 Engram 服务器，通常用 docker compose 启动。需要 API_KEY 密钥（由该包的 init 命令生成），可选 MCP_HOST 与 MCP_PORT 指向服务器。需要能访问该服务器和 npm 仓库。

安装前请注意

API_KEY 用于桥接与你自己服务器之间的认证，应作为密钥保管，并让服务器只监听本机回环地址。代理可以写入、取代和归档共享状态与消息，并发写入会影响其他代理读到的内容。默认配置被描述为封闭安全，但设置 CORS_ORIGINS 后会开放跨域访问。

安装

在 SourceWeft 中

打开控制台中的 Engram，将其添加到工作区。
为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照仓库中的启动说明。

README

Engram

A coordination bus + shared truth for your agent fleet. Self-hosted, two-component setup: a dockerized server plus a thin stdio bridge for your MCP clients.

Engram is an MCP server that lets multiple AI coding agents — Claude Code, Codex, Cursor, custom harnesses — share state, preserve context across sessions, and coordinate with each other. It is not another memory store. Its differentiators:

Supersession + current-state resolution: observations supersede each other (replace-current), and get_current_observation resolves the chain server-side — so readers get the newest non-superseded state. Conflict handling is implemented: checkpoint is branch-preserving CAS — concurrent writers branch rather than overwrite, and conflicts surface as heads, never silently resolved (contract-tested; see the evidence ledger).
Agent messaging with a tracked delivery lifecycle: direct and capability-based sends, message supersession, read-state as a shared signal, atomic ack+archive. (Described as tracked lifecycle, not guaranteed delivery — the states are honest about what the server knows.)
The Adaptive Coordination Protocol (ACP): the ETA-driven coordination discipline that co-evolved with the server — published as docs/SPEC.md with a real two-harness worked tutorial.

Documentation

Doc	What it covers
Quickstart	Clean machine → two coordinating agents in ~15 minutes
Concepts	One current truth, messaging lifecycle, resume/checkpoint, honest security model
ACP SPEC	The coordination protocol, versioned (1.0.0)
Tutorial	Annotated transcript of a real Claude Code ↔ Codex review loop over Engram
Tool compatibility map	The 19-tool v1 surface; every retired tool and its exact replacement
Backup & restore	Tested SQLite backup/restore/compaction runbook

Status

Published. @tomcat65/[email protected] is live on the npm registry and the source is public at github.com/tomcat65/engram. The install path is contract-tested and was smoke-verified post-publish on a clean machine: npx -y @tomcat65/engram-mcp resolves the bin, and the first-run wizard runs straight from the registry install.

House rule: every claim in these docs must trace to a test or a measurement (see the evidence ledger below). Claims that don't are bugs.

Evidence ledger

Claim	Evidence	Source	Date
Tree green, full gates	lock-verify (manifest-bound pin matched), clean `npm ci`, script-integrity, typecheck, build, tests (33 files, 408 passed \| 2 skipped \| 6 todo), schema-docs, final-tree smoke, docker build — all PASS, exit 0	this repository, `internal/run-staged-proof.sh`	2026-07-16
Documented env boots the runtime	Final-tree smoke gate: server starts from `.env.example` variables with a generated key, authenticated MCP request succeeds, DB lands at the documented path, bridge round-trips on the same contract, compose ports are loopback-bound, and the untouched placeholder key fails startup	this repository, `internal/final-tree-smoke.mjs`	2026-07-16
resume/checkpoint + conflict handling implemented	ENG-4 P0 contract suite (120 executable tests: CAS branching, conflict heads, idempotent replay, budget coverage closedness, scope-bound handles)	`tests/contract-eng4-p0.test.ts`	2026-07-16
Install path works	CLI contract suite (9 tests: bin mapping, wizard key-gen + parseable configs, .env write-once, live demo round-trip verified server-side, bridge delegation)	`tests/contract-cli.test.ts`	2026-07-16
Closed-safe defaults	Placeholder key fails startup; compose ports loopback-bound; CORS grants no cross-origin access unless `CORS_ORIGINS` is set (tested)	`internal/final-tree-smoke.mjs`, `tests/contract-cli.test.ts`	2026-07-16
Discovery is truthful	tools/list advertises the exact frozen schemas the handlers implement; retired legacy shapes are schema-rejected (regressions added after an adversarial review caught drift)	`tests/contract-eng4-p0.test.ts`	2026-07-16
Published + installable from the registry	`npm publish` succeeded under 2FA (auth-and-writes, security key); `npm view @tomcat65/engram-mcp version` → `0.1.0`; clean-machine smoke: fresh npx cache, `npx -y @tomcat65/engram-mcp --help` and `… init` ran from the registry install	npm registry, post-publish smoke	2026-07-16

v1 surface (short)

Install (two-component setup): server via docker compose up, then the @tomcat65/engram-mcp stdio bridge per MCP client; first-run wizard generates the API key and prints ready-to-paste config for Claude Code / Codex / Cursor / Claude Desktop; optional namespaced (demo-*) demo seed on an otherwise empty DB.
Knowledge graph: entities, observations, relations, supersession, current-state resolution, conflict surfacing.
Agent messaging: direct, capability-based, superseding; tracked delivery lifecycle.
resume / checkpoint: budgeted one-call session rehydration with closed coverage accounting, and CAS-protected, branch-preserving structured state capture.
ACP: the coordination protocol as a versioned spec + real worked example.