Engram
Git-backed markdown memory for AI agents; search hides superseded and archived notes.
Connector by rwnalds · GitHub account verified by the MCP Registry
Chalk Labs
Need help deploying Engram?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.
npx agentmarket install connector/rwnalds-engram
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.
- Tools
- 6 read · 5 write · 1 delete · 4 not yet classified
- Secrets
- None asked for
- Install scripts
- None found
- Runs as
- Docker image
Tools by what they do 16
Read from the source code; the running server may list different tools.
Read 6 · Look things up without changing anything.
brain_capturebrain_listbrain_readbrain_schemabrain_searchbrain_tree
Write 5 · Create, change, send or run things.
brain_appendbrain_create_folderbrain_editbrain_movebrain_write
Delete 1 · Delete, drop, revoke or wipe things.
brain_delete
Not yet classified 4 · We could not tell from the name and description.
brain_backlinksbrain_graphbrain_recentbrain_supersede
Network hosts it talks to 7
accounts.google.com· found in codeapi.github.com· found in codegithub.com· found in codeglama.ai· found in codeoauth2.googleapis.com· found in codeopenidconnect.googleapis.com· found in codeui.shadcn.com· found in code
Files it touches
/dev/null
Tools (16)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
brain_appendAppend text to a note (creates it if missing).
brain_backlinksNotes that link to the given note.
brain_captureHand over a ROUGH note / brain-dump and let the vault file it. An agent loop reads SCHEMA.md, searches for what already exists, then deliberately creates a new note, appends to a matching one, or archives what this supersedes — and returns a manifest of every path it touched. It reads a note before overwriting it, and never deletes. Use when you have unstructured input and don't want to choose the path yourself; use brain_write when you do.
brain_create_folderCreate a new folder in the vault (with a .gitkeep).
brain_deleteDelete a note (recoverable via git history). Prefer brain_move into an archive folder — deleting destroys the reasoning trail, archiving only removes it from search. Delete when the note is wrong or duplicated, archive when it is merely no longer true.
brain_editOverwrite a note. Pass `content` (full raw markdown incl. frontmatter) — read first with brain_read, then write the whole file back. Also accepts `body` (+ optional `frontmatter`) like brain_write.
brain_graphThe knowledge graph (nodes + edges from wikilinks and related:). Optional folder filter.
brain_listList every note with metadata (path, title, folder, type, tags, status, authority). Use to discover what exists. `authority` tells you which notes are source-of-truth and which are history.
brain_moveMove or rename a note. This is how you retire something: when a note stops being true, move it to an archive folder (see brain_schema → conventions.ranking.archiveFolders) rather than deleting it. Archived notes are demoted in search and excluded by default, so they stop misleading agents while the reasoning trail survives. Leave a pointer in the replacement note saying what superseded what.
brain_readRead a note: full markdown (frontmatter + body), its `authority`, and its backlinks. Path is vault-relative, e.g. 'clients/mks/mks.md'. Pass `section` to read just one heading's content instead of the whole file — cheaper on long documents. If the heading isn't found you get the list of available headings back. Always check the returned `authority` before acting on the content: `archived` and `superseded` notes are history, not instructions.
brain_recentNotes changed most recently, newest first. Use to catch up on what humans or other agents have done since you last looked.
brain_schemaREAD THIS FIRST, before searching or writing. Returns the vault's SCHEMA.md (folder taxonomy, frontmatter conventions, wikilink model, write protocol) AND a live description of this specific vault: its folders, the `status:` values actually in use, how search ranks notes by authority, and any integrity warnings. Vaults differ — never assume conventions, read them here.
brain_searchKeyword search across the vault. Returns `{ hits, excluded }`. Each hit has `path`, `title`, `folder`, `status`, `snippet`, and `authority`. IMPORTANT — ranking is by keyword relevance, NOT by truth. A superseded document repeats the query words just as often as the live one, so it can outrank it. Every hit carries an `authority`: `authoritative` (source of truth — prefer it), `current`, `provisional` (draft/proposed — never quote as settled), `superseded`, `archived`. Rank order is a suggestion; `authority` is the signal. `excluded` is the explainable-rejection list: notes that matched the …
brain_supersedeRetire a fact and replace it, atomically. When a fact changes (a price, a term, a decision), DON'T just add a new note — the old value keeps matching searches and gets quoted. `brain_supersede(from, to)` marks the old note superseded in place (body preserved) and links it to the new one, in a single commit, so add-and-retire can't drift apart. After this, search withholds the old note with the reason "superseded by <to>". `from` = the note being retired; `to` = the note that replaces it. If `to` doesn't exist yet, pass `body` (its markdown) and it's created; otherwise write `to` first, then s…
brain_treeReturn the folder/file tree of the vault.
Show 1 more tools
brain_writeCreate or overwrite a note. PREFER `body` (markdown, no frontmatter) + `frontmatter` (an object): the YAML is serialised for you and always parses. Hand-writing frontmatter into `content` risks invalid YAML — a note whose frontmatter fails to parse loses its status, tags and title on every read, so a note claiming `status: locked` would rank as an ordinary one. Such a write is REJECTED. Follow SCHEMA.md: kebab-case path, dated names for daily/decisions, frontmatter with title/type/tags/status. Path vault-relative (e.g. decisions/foo-2026-07-09.md). WHEN A FACT CHANGED, DON'T CREATE A DATED SI…
Signals
- Stars
- 17
- Forks
- 4
- Open issues
- 1
- Last commit
- Aug 14, 2026 (2 months ago)
- Last release
- Aug 11, 2026 (2 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- Registry name
io.github.rwnalds/engram- Version
- 0.1.2
- Auth
- No auth
- Packages
- oci
ghcr.io/rwnalds/engram:0.1.2 - License
- MIT
- Repository
- github.com/rwnalds/engram
- Website
- github.com/rwnalds/engram
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get Engram running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
Engram MCP server. Agent Mart. https://agentmart.dev/connectors/rwnalds-engram (last updated 2026-10-24)