Engram

ro.rootcausePublished by rootcause.roOfficial publisherv1.0.1Updated Oct 26, 2026

A second brain for Claude: remembers your work, plans your day, encrypted under a key only you hold.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Engram is a remote "second brain" server that lets an assistant remember your work and plan your day, with data encrypted under a key only you hold.

What you can do
  • Remember and recall your work: the server is described as a second brain for Claude that keeps track of what you are working on.
  • Plan your day: it is presented as helping organize and plan daily work.
  • Keep stored data encrypted under a key only you hold.
  • No tool list is published, so the exact operations available to an assistant are not documented here.
When to use it
Worth considering if you want an assistant to carry context about your work across sessions and help plan your day, and you prefer a hosted service that keeps your data encrypted under your own key.
Requirements
A remote streamable HTTP endpoint at engram.rootcause.ro; no local package or runtime is needed. OAuth authentication is required. No environment variables or headers are declared.
Before you install
The service stores personal work context and daily plans on a third-party host, so review its privacy and retention terms. Encryption depends on a key only you hold, so losing that key may make data unrecoverable. OAuth grants the server access to your account; no tool list is published, so what it can read or change is not documented.

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/ro.rootcause%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://engram.rootcause.ro/mcp/directory"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestOct 18, 2026
  2. v1.0.0Oct 17, 2026

Score

67% 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

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.