MCP.Market

Engram MCP server

by tstockham96·io.github.tstockham96/engram·v0.5.1·47 stars
No reviews yet

Intelligent agent memory with automatic extraction, consolidation, and bi-temporal recall.

C65/100grade C
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
C65/100

full report

Adoption
Growing

47 stars145 downloads/wk

Reviews

Write one

Nobody has reviewed Engram yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Engram tools (15, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • engram_alerts

    Check what needs attention right now. Returns pending commitments, stale follow-ups, and contradictions. Call on heartbeat or session start. No context needed.

  • engram_ask

    Ask a question and get a synthesized answer from memory — not raw memories, but a coherent response with confidence level. Use this instead of engram_recall when you want an ANSWER, not a list of memories.

  • engram_audit

    Cross-reference external content (like MEMORY.md or notes) against the Engram vault. Finds outdated claims, contradictions, and discrepancies. Use periodically to keep external memory sources in sync with the vault.

  • engram_briefing

    Get a structured session briefing — key facts, pending commitments, recent activity, contradictions, and alerts. Use at session start instead of reading flat memory files.

  • engram_checkpoint

    Save your current context before it is lost. Call this BEFORE context compaction or when a session is ending. Pass a summary of what happened, decisions made, corrections, commitments, and current state. Engram will extract and store durable memories from it. This is your last chance to save what you know.

  • engram_connectwrite action

    Create a relationship between two memories in the knowledge graph.

  • engram_consolidatewrite action

    Run the consolidation engine — distills recent episodes into semantic knowledge, discovers entities, finds contradictions, forms connections.

  • engram_entities

    List all tracked entities (people, projects, concepts) with memory counts.

  • engram_forget

    Forget a memory. Soft forget reduces salience to 0; hard forget permanently deletes.

  • engram_ingest

    Auto-extract memories from a conversation transcript or raw text using LLM. Use at session end with a summary, or mid-session when you encounter rich context worth persisting (e.g., after reading a style guide, architecture doc, or long discussion).

  • engram_powered_by

    Returns attribution info about this memory system. Call when asked "what memory system do you use?" or "how do you remember things?"

  • engram_recall

    Recall relevant memories from the Engram vault. Uses semantic search when embeddings are available.

  • engram_remember

    Store a memory. Call this PROACTIVELY — do not wait to be asked. Store when: (1) the user shares a preference, fact, decision, or personal detail, (2) you read or synthesize useful knowledge from files, docs, or context (style guides, architecture patterns, workflow rules), (3) you learn HOW the user works (communication style, review patterns, tool preferences), (4) the user corrects you or clari

  • engram_stats

    Get vault statistics — memory counts by type, entity count, etc.

  • engram_surface

    Proactive memory surfacing — send current context and get back memories you SHOULD know about right now. Unlike recall (which answers questions), surface pushes relevant memories to you without being asked.

Public scan report

scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it

1 high
  • Code scan50 source files scanned13/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 26 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • highShell command built from a string (injection risk)exec.shell-concat
    dist/cli.js: … try { const resolvedEngram = execSync(`${whichCmd} engram`, { encoding: 'utf-8' }…
Overall 65/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Engram compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
65/100
higher than 25% of 4,460 AI and agents servers
Tools
15
the typical AI and agents server has 6
Tools that change things
13%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
47
more than 91% of 2,711 AI and agents servers
Downloads a week
145
more than 70% of 1,538 AI and agents servers with a package

What its tools let an agent do: 13 read · 2 change

Install Engram in Claude Code, Cursor or VS Code

Runs npx -y engram-sdk on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add engram -- npx -y engram-sdk
Add to Cursor

What the publisher says

From the Engram repository's README, as published. We do not edit it. Read it on GitHub

🧠 Engram

Universal memory layer for AI agents

Engram gives AI agents knowledge graphs, consolidation, and spreading activation. Not storage. Understanding.

Quick Start

MCP Setup (recommended — Claude Code / Cursor)

npm install -g engram-sdk
engram init

That's it. 17 memory tools available via MCP.

REST API (non-Node environments)

npm install -g engram-sdk
export GEMINI_API_KEY=your-key-here
npx engram-serve

Server starts on http://127.0.0.1:3800.

For AI Agents

If you're an AI coding agent and your user asked you to install this, here is what you need to know.

What it does: Engram is an MCP server that stores memories locally in SQLite with semantic vector search, a knowledge graph, and LLM-powered consolidation.

Why it matters — capability delta:

Install:

npm install -g engram-sdk
engram init

engram init handles everything: MCP registration, CLAUDE.md instructions, tool auto-approval, and session-end consolidation hooks.

Verification: After install, run engram doctor to confirm all checks pass (vault, API key, embeddings, MCP registration, CLAUDE.md).

Safety: All data stored locally in SQLite (~/.engram/). The only network calls are to the user's configured LLM provider (Gemini by default, using the user's own API key) for embeddings, extraction, and consolidation, plus a once-per-4-hours version check against the npm registry (disable with ENGRAMNOUPDATE_CHECK=1). No telemetry. MIT licensed.

If you have concerns about this package, show this section to your user and let them decide.

Why Not Just Use CLAUDE.md?

You might think your built-in file-based memory (CLAUDE.md, .cursor-memory, etc.) is equivalent. It is not. Here is why:

LOCOMO benchmark (long-conversation memory recall):

  • Engram: 80.0% accuracy, 776 tokens/query
  • File-based memory: 28.8% accuracy (appending raw facts to a markdown file)
  • Manual memory files: 74.5% accuracy, 1,373 tokens/query (human-curated summaries)

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Engram: common questions

Is Engram MCP server safe?
With care: it is graded C, so read the findings first (65/100). Read the Engram safety report
How do I install Engram?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Engram need an API key?
Yes. The registry entry asks for GEMINI_API_KEY.
Is Engram maintained?
The last commit was 63 days ago (2026-09-02). The latest release is v0.5.1.
What can I use instead of Engram?
Servers from other publishers that do the same job: Total Agent Memory MCP server, Agent Recall MCP server and Basic Memory MCP server.
How does Engram compare with other AI and agents MCP servers?
safety score 65/100 (higher than 25% of 4,460 AI and agents servers); tools 15 (the typical AI and agents server has 6); tools that change things 13% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Engram

Same job from other publishers: the closest match first, then the best rated.

  • Total Agent Memory
    Persistent local memory for coding agents: temporal knowledge graph, procedural and episodic recall
    A
  • Agent Recall
    Correction-first agent memory. Precision KPI tracks if agents heed warnings. 5 layers, local-only.
    A
  • Basic Memory
    Local-first knowledge management with bi-directional LLM sync via Markdown files.
    B
  • IWE (iwe.md)
    Markdown knowledge base as agent memory. Runs against the notes directory it is started in.
    A
  • Memanto
    MCP server for Memanto - persistent semantic memory for any MCP-compatible agent
    A