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.