Engram

tools.engramPublished by engram.toolsOfficial publisherv0.4.11Updated Nov 7, 2026

Memory for AI agent teams across tools, sessions, repositories, and teammates.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

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

What you can do
  • No tool list is published, so capabilities are described only at a high level.
  • Store and recall memories that persist across sessions and tools.
  • Share a memory workspace across repositories and teammates.
  • Connect through a hosted endpoint or a local npm package.
  • Claim a trial workspace later so its memories are kept.
When to use it
Useful when an assistant should remember context between sessions, across different tools, or across a team working in several repositories, and you want that memory hosted rather than kept in a single local chat.
Requirements
Either the remote endpoint at api.engram.tools with OAuth, or the local npm package engram-tools over stdio. An ENGRAM_API_KEY is optional; leaving it empty starts an email-less free agent trial. ENGRAM_API_URL optionally overrides the endpoint.
Before you install
The trial workspace is unclaimed until you run the connect step, so memories may not be retained without it. Memory content is sent to a third-party hosted service. Treat ENGRAM_API_KEY as a secret and keep it out of shared configuration.

Installation

In SourceWeft

  1. Open Engram in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/tools.engram%2Fengram/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "engram": {
      "type": "http",
      "url": "https://api.engram.tools/mcp"
    }
  }
}

README

This repository has no README.

Tools

17

engram_start

Start Engram

Begin meaningful work in a repository with a Markdown briefing: session id, ranked private/public memory, workspace guidance and optional checklists. Unlike engram_smarter, this includes workspace onboarding/activation guidance; unlike engram_rehydrate, it prepares a starting briefing instead of reconstructing a prior journal. Use once when beginning work; choose engram_smarter for a task switch and engram_rehydrate for recovery. Supply repo and task when known; context overrides the generated project/market/role/stack/task query. Reuses one eligible active journal; new_session=true deliberately creates a separate journal. Supply session_id for parallel work. Ambiguous automatic selection returns 409; list sessions and choose an exact id. Records a session event; repeating may add events or open another session. Consumes workspace daily call quota; quota exhaustion requires reset or a plan change, not immediate retries. OAuth: memory:read and session:write.

Parametersreporoletaskdepthlimitstackmarketcontextprojectagent_toolsession_idnew_session+1 more

engram_rehydrate

Rehydrate Context

Recover interrupted work after compaction, resume or lost context. Returns Markdown checkpoints, decisions, gotchas, open loops and recent events. Unlike engram_start, this restores the prior journal when available; unlike engram_recall or engram_smarter, it recovers session history rather than only searching durable knowledge. session_id selects an accessible workspace session. Closed or teammate journals are read-only history, never reopened. Automatic recovery requires one active journal for this member, repo/project and authenticated OAuth connection or supplied agent_tool within the recovery window. Multiple matches return 409: list sessions and choose an id. since filters events after selection. If none matches, loads durable task memory and opens a journal. Repeating active recovery adds events; it does not erase history. Consumes workspace daily call quota. OAuth: memory:read and session:write.

Parametersrepotaskdepthsincereasonprojectagent_toolsession_id

engram_recall

Recall Memory

Answer one concrete question from authenticated workspace/public memory before deciding or debugging. Unlike engram_smarter, this retrieves question-specific evidence without task checklists; unlike engram_get_context, it returns one ranked memory list instead of separate category samples. Use engram_rehydrate to recover an interrupted session. Returns JSON with ranked memories, ids, trust/conflict signals and retrieval hints. Example: {"repo":"engram","query":"What did we learn about Netlify SSR costs?"}. No matches returns count=0; deepen or rephrase rather than assume the answer. repo/type/tags narrow the question; limit overrides the depth budget. Records retrieval telemetry without editing knowledge. Consumes workspace daily call quota; stop on quota errors and retry only transient failures. OAuth: memory:read.

Parametersrepotagstypedepthlimitqueryrequiredsession_id

engram_store

Store Memory

Save one durable lesson privately for future workspace agents; returns a confirmation. Use engram_reflect for a milestone with several lessons/outcomes and engram_report_outcome to assess an existing memory. To correct knowledge, supply the complete replacement in content and old ids in supersedes_memory_ids; change_reason explains the replacement. Old entries retain history; this is not permanent deletion. Similar content may deduplicate and boost confidence, so retries can have effects. Consumes memory/call quota; rejects secrets and low-quality content. OAuth: memory:write.

Parametersrepotagstyperequiredcontentrequiredcontextagent_toolsession_idchange_reasonsupersedes_memory_ids

engram_report_outcome

Report Memory Outcome

Record whether a recalled memory helped; returns a confirmation. Use its exact memory_id and evidence in detail. success=false may include failure_reason; outdated marks obsolete knowledge, while success raises confidence. Only accessible workspace/public memories may be reported. Repeating adds outcomes and changes confidence; do not blindly retry. Use engram_store with supersedes_memory_ids for a verified replacement, or engram_reflect to batch milestone outcomes. Consumes workspace daily call quota. OAuth: outcome:write.

Parametersrepodetailsuccessrequiredmemory_idrequiredsession_idfailure_reason

engram_cross_pollinate

Cross-Pollinate Knowledge

Reuse a lesson solved in another repository before rebuilding a shared pattern. Unlike engram_recall or engram_smarter, this explicitly excludes target_repo from source searches and adds transfer lessons and quality gates. Returns Markdown with ranked memories and source repos from other authenticated workspace repositories, with optional public knowledge. source_repos restricts the search; include_public supplements sparse private results. Records retrieval telemetry without copying knowledge. Consumes workspace daily call quota. OAuth: memory:read.

Parametersdepthlimitcontextrequiredsession_idtarget_reporequiredsource_reposinclude_public

engram_smarter

Load Task Context

Brief a materially different task within the same session. Unlike engram_recall, this combines goal-focused memories with optional procedural checklists; unlike engram_get_context, it ranks evidence for the task instead of returning category samples. Returns Markdown with ranked workspace/public memory and retrieval hints. Use engram_start to begin work and engram_rehydrate for lost context. Example: {"repo":"engram","context":"Improve public-page delivery on Netlify while preserving localized SEO and onboarding."}. context states the whole goal; repo/file focus retrieval without reading local files. limit overrides depth; include_skills=false suppresses checklists. Records retrieval/session telemetry without editing knowledge. Consumes workspace daily call quota. OAuth: memory:read.

Parametersfilerepodepthlimitcontextrequiredsession_idinclude_skills

engram_reflect

Create Memory Checkpoint

Checkpoint a milestone or handoff for later recovery with engram_rehydrate. Supply at least one of summary, learnings, used_memories or feedback. Returns Markdown with stored/skipped counts, outcomes and next actions. Use engram_store for one lesson and engram_report_outcome for one outcome. store=false skips learning storage only: the journal and supplied outcomes/feedback can still be written. This checkpoint leaves the session open. Retrying may duplicate writes; verify prior success first. Consumes workspace daily call quota and memory quota for saved lessons. OAuth: session:write, memory:write and outcome:write.

Parametersrepotaskstoresummaryfeedbacklearningsagent_toolsession_idused_memories

engram_skill

Load Skill Guide

Find a procedural checklist before a repeatable task. Omit skill or pass an empty string to list available names; otherwise load a name such as code-review or skill:code-review. Returns JSON with available_skills/usage for listing or skill/count/steps/combined for a guide. Unknown names return count=0 and a message. Reads workspace/public knowledge without installing or executing anything. Use engram_recall for a project fact and engram_smarter for task-based guide selection. Consumes workspace daily call quota. OAuth: memory:read.

Parametersskill

engram_get_context

Get Repository Context

Audit repository knowledge by category: conventions, gotchas, patterns, solutions and architecture. Unlike engram_recall or engram_smarter, this searches each category separately and returns five sample arrays for coverage review, rather than one task-ranked list. Returns JSON with repo/file/total and up to 21 entries; this is a bounded search, not a full repository-memory export. repo is required; file/task refine search without reading files. Only when all five categories have no repo matches does the search broaden to workspace/public memory. Empty results are valid. Does not edit knowledge. Consumes workspace daily call quota. OAuth: memory:read.

Parametersfilereporequiredtask

engram_setup

Explain Engram Setup

Explain onboarding and inspect the authenticated workspace when an agent needs setup guidance. Returns one JSON response with plan/counts/limits, tool groups, activation checklist and suggested calls; no pagination or installation. Hints personalize examples: project names the work; repo scopes activation guidance, falling back to project when omitted. Does not configure the machine, open a working session or edit knowledge. Use engram_start to begin work, engram_rehydrate to recover it and engram_proof to audit adoption. Consumes workspace daily call quota; exhaustion requires reset or a plan change. OAuth: memory:read.

Parametersreporoletaskstackmarketprojectagent_tool

engram_proof

Get Engram Proof

Audit adoption before a rollout or when checking whether the workspace is using memory and reporting outcomes. Takes no arguments. Returns JSON with memory-bank breakdowns, learning-loop activity, proof points and a benchmark checklist. Does not change knowledge or run a benchmark. Use engram_setup for onboarding and engram_recall for task knowledge. Consumes workspace daily call quota. OAuth: memory:read.

Takes no parameters.

engram_list_sessions

List Sessions

Find an exact session_id before recovery, closing or a handoff. Unlike engram_rehydrate, this lists bounded metadata without replaying journal content or changing a session. Returns JSON sessions with member/client attribution, status, activity and checkpoint availability, plus next_cursor. Default scope=mine lists this member's sessions; scope=workspace explicitly includes teammates in the authenticated workspace. repo/status/agent_tool/member_id filter results; a teammate member_id requires workspace scope. limit defaults to 20, maximum 50. Pass next_cursor unchanged to continue newest-started-first pagination. Empty results are valid. Consumes daily call quota. OAuth: memory:read.

Parametersrepolimitscopecursorstatusmember_idagent_tool

engram_close_session

Close Session

Finish an exact journal at a real completion or handoff. Unlike engram_reflect, this atomically closes the session after saving a supplied final summary or confirming an existing checkpoint. Durable memories and journal history remain; closure ends journal writes without erasing knowledge. Returns JSON with session_id, closed_at, checkpoint_id, already_closed and memories_retained. Get session_id from start/rehydrate/list_sessions. Only this session's member or a human workspace owner may close it; team read access does not grant close authority. A missing checkpoint or failed save leaves it active. Repeating close returns the original receipt without duplicate summaries. Closed journals are read-only for explicit rehydrate and cannot be implicitly reopened. Consumes daily call quota. OAuth: session:write.

Parameterssummarysession_idrequired

engram_retract_memory

Retract Memory

Withdraw an exact private memory that should no longer guide agents. Unlike engram_store with supersedes_memory_ids, this needs no replacement and keeps the content for explicit restoration. Unlike engram_delete_memory, it is reversible. Returns JSON memory_id, RETRACTED status and already_retracted. Get memory_id from recall/context; provide a non-sensitive reason, 1–1000 characters. Only the creator or a human workspace OWNER may withdraw it; team read access is not write authority. Current retrieval excludes it and source-dependent patterns. Recovery suppresses free text in referencing journals rather than replay withdrawn guidance. Start a clean session for new work or restore the source. Repeating is idempotent. Public-bank and superseded records are excluded. Consumes daily call quota. OAuth: memory:write.

Parametersreasonrequiredmemory_idrequired

engram_restore_memory

Restore Memory

Make an explicitly retracted private memory available again. Unlike engram_store, this restores the original ID/content; storing matching retired content returns 409 rather than silently reviving it. Returns JSON memory_id, ACTIVE status and already_active. Retained source-dependent history becomes available when no other withdrawn sources remain. Only the creator or a human workspace OWNER may restore. Memory quota still applies. A confirmed replacement or SUPERSEDED state requires the separate replacement-review workflow; permanently erased IDs cannot be restored. An already active record is an idempotent no-op. Consumes daily call quota. OAuth: memory:write.

Parametersmemory_idrequired

engram_delete_memory

Preview or Delete Memory

Preview or permanently erase one private memory and its explicit derived patterns from the live database. Unlike engram_retract_memory, execution cannot be undone. Requires a human workspace OWNER API key; OAuth agents and member keys cannot erase. Does not delete independent memories or unrelated sessions. Default dry_run=true returns counts, derived IDs, affected session IDs (first 50), scope and confirmation. Inspect it first: execution redacts the entire free-text history/checkpoints/task/context of referencing sessions, plus associated outcomes, links, jobs and linked evidence; shared entities remain if still referenced. Execute only the reviewed ID using dry_run=false and confirmation="delete:<memory_id>". Returns erased_at/counts; repeated execution returns the original minimal ID/count receipt without erased text (a one-way content fingerprint blocks exact store replays). In-flight background writes and exact store retries cannot repopulate erased knowledge. Historical unlinked paraphrases, already delivered client context, application/provider logs, provider copies and backups are outside this live-database operation. Public-bank records are excluded. Consumes daily call quota.

Parametersdry_runmemory_idrequiredconfirmation

Version history

6
  1. v0.4.11LatestOct 22, 2026
  2. v0.4.10Oct 21, 2026
  3. v0.4.9Oct 20, 2026
  4. v0.4.8Oct 16, 2026
  5. v0.4.6Oct 11, 2026
  6. v0.4.4Sep 23, 2026

Score

75% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Engram integrations