Engram

io.github.spectra-gPublished by GitHub account spectra-gv0.2.11Updated Oct 24, 2026

MCP adapter for Engram - organizational memory for AI agents

The publisher's own server: Engram

VerifiedSTDIODesktop onlyKnowledge & Memory

Overview

AI-generated overview

An MCP adapter that connects an AI assistant to Engram, described as organizational memory for AI agents.

What you can do
The registry describes this package as an MCP adapter for Engram, characterized as organizational memory for AI agents. It runs locally over stdio, so an assistant would reach Engram's memory features through this adapter rather than through a remote endpoint. No tools, resources, or prompts are listed in the supplied manifest, so the specific operations it exposes are not documented here.
When to use it
Consider it when you already use Engram and want an assistant to work with that organizational memory through MCP. Because no tool list is provided, it is hard to judge fit for any other purpose; verify the exposed capabilities before relying on it.
Requirements
Runs as a local process on the user's machine over stdio, installed from the npm package @spectra-g/engram-adapter, so a Node.js runtime and npm are needed. The manifest declares no authentication, environment variables, or headers, and it is marked desktop only with no web executable.
Before you install
The manifest declares no credentials, but the adapter is a thin bridge to Engram, so whatever Engram stores or can change is reachable through it. No tool list is published, so read and write behavior cannot be confirmed from the supplied material. Review the package before installing and confirm what data it reads or modifies.

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

This repository has no README.

Tools

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

Version history

1
  1. v0.2.11LatestSep 16, 2026

Score

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

    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