Engram

io.github.tomcat65Published by GitHub account tomcat65v0.1.2Updated Oct 27, 2026

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

The publisher's own server: Engram

VerifiedSTDIODesktop onlyKnowledge & MemoryCommunication & CollaborationAI & ML

Overview

AI-generated overview

Self-hosted coordination bus and shared knowledge graph that lets multiple AI coding agents share state, message each other and resume context across sessions.

What you can do
  • Share a knowledge graph of entities, observations and relations, with supersession and server-side resolution of current state
  • Send direct or capability-based messages between agents, with supersession, read-state and atomic ack plus archive
  • Rehydrate a session in one budgeted resume call and capture structured state with checkpoint, which branches instead of overwriting on concurrent writes
  • Surface conflicts as heads rather than silently resolving them
  • Follow the published Adaptive Coordination Protocol spec and worked tutorial for multi-agent workflows
When to use it
Useful when several AI coding agents or harnesses work on the same project and need one shared current truth, hand-offs, or context that survives session restarts. Less relevant for a single agent that only needs a simple memory store.
Requirements
Runs as a local stdio bridge (npm package) on desktop, plus a separately self-hosted Engram server, typically started with docker compose. Requires the API_KEY secret, generated by the package's init command, and optionally MCP_HOST and MCP_PORT to point at the server. Network access to the server and the npm registry is needed.
Before you install
The API key authenticates the bridge to your own server, so treat it as a secret and keep the server bound to loopback. Agents can write, supersede and archive shared state and messages, so concurrent writers affect what other agents read. Defaults are described as closed-safe, but CORS access opens if CORS_ORIGINS is set.

Installation

In SourceWeft

  1. Open Engram in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

DocWhat it covers
QuickstartClean machine → two coordinating agents in ~15 minutes
ConceptsOne current truth, messaging lifecycle, resume/checkpoint, honest security model
ACP SPECThe coordination protocol, versioned (1.0.0)
TutorialAnnotated transcript of a real Claude Code ↔ Codex review loop over Engram
Tool compatibility mapThe 19-tool v1 surface; every retired tool and its exact replacement
Backup & restoreTested 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

ClaimEvidenceSourceDate
Tree green, full gateslock-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 0this repository, internal/run-staged-proof.sh2026-07-16
Documented env boots the runtimeFinal-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 startupthis repository, internal/final-tree-smoke.mjs2026-07-16
resume/checkpoint + conflict handling implementedENG-4 P0 contract suite (120 executable tests: CAS branching, conflict heads, idempotent replay, budget coverage closedness, scope-bound handles)tests/contract-eng4-p0.test.ts2026-07-16
Install path worksCLI 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.ts2026-07-16
Closed-safe defaultsPlaceholder 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.ts2026-07-16
Discovery is truthfultools/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.ts2026-07-16
Published + installable from the registrynpm 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 installnpm registry, post-publish smoke2026-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.

License

Apache-2.0

Source: README.md at commit c019aee

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Engram integrations

Engram

tools.engramOfficial publisher

Engram gives AI assistants a shared memory layer that persists across tools, sessions, repositories and teammates.

Streamable HTTPWeb executableAuth
Knowledge & Memory17 toolsNov 8, 2026

Engram

Published by GitHub account TushaeBXN

Local, private long-term memory for AI: verbatim, searchable, correctable. No LLM or API key.

STDIODesktop only
AI & MLNot validated yetOct 25, 2026

Engram: AI memory you can edit in Obsidian

Published by GitHub account engram-app

Hosted MCP memory server that gives Claude, ChatGPT and other MCP clients shared notes they can read and write, editable in Obsidian or the web app.

Streamable HTTPWeb executableAuth
Files & StorageCredential requiredNov 7, 2026

Engram

Published by GitHub account devinmlowe

Engram is a local-first cognitive memory server for coding agents: it captures conversations, extracts structured knowledge, and serves hybrid recall, graph and

STDIODesktop only
Knowledge & MemoryNot validated yetOct 25, 2026

Engram

Published by GitHub account tstockham96

Engram gives an AI assistant a local SQLite memory vault with semantic recall, a knowledge graph, and LLM-powered consolidation.

STDIODesktop only
Knowledge & MemoryNot validated yetOct 24, 2026