Engram

MCP文档知识

提供方 未标注

文档知识 未标注 OAuth 授权 社区 / 第三方 Claude DesktopClaudeCursorVS Code

自托管个人记忆,具备项目范围的 MCP 搜索和上下文工具、本地 Ollama 以及文档摄取。源码可用;个人非商业用途免费,商业用途需获得许可。

一句话选型结论

按资料字段整理

Engram 属于文档知识类 MCP 服务器,传输方式未标注,OAuth 授权,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式未标注 鉴权OAuth 授权 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

未标注 OAuth 授权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Engram当前 未标注 未标注 未标注 无 2026-11-20
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

10.6 KB
来自项目仓库与上游目录的原文,未做删改

Engram

> Your knowledge. Your context. Your server.

Stop rebuilding context from scattered documents, saved pages and old conversations.
Engram brings them into a personal memory platform you host yourself, with local
Ollama processing, source-aware search and controlled access for your AI clients.

Explore Engram ·
Set up your server ·
Connect an MCP client ·
Report feedback

Free for personal, noncommercial self-hosting. Commercial, workplace and
managed-hosting use require separate written permission. Engram is
source-available; see the license and usage guide.

Why Engram?

When you need to… Engram gives you…
Remember the reasoning behind a decision Source provenance, versioned memories and an event timeline.
Bring documents and conversations together File ingestion, ChatGPT export import and a browser capture extension.
Keep extracted facts under your control A Memory Inbox and human-reviewed agent proposals.
Give an AI client useful context Project-scoped retrieval through MCP and the REST API.
Keep personal AI processing on your infrastructure Local embeddings and extraction through Ollama.
Recover your knowledge after a server failure Encrypted backups and documented, isolated restore testing.

Built for technically comfortable personal users running Linux and Docker Compose.
The deployment guide recommends 4 CPU cores and 8 GB RAM
(16 GB+ preferred), plus storage for your data, models and backups.

Engram 2.8 adds source-cited reflection, reviewed project briefs, memory lifecycle controls, pinning and audited undo. Its shared iOS and Android companion supports project-scoped memories, search, human review and a secure offline library. Native mobile builds remain on their documented preview channel; see mobile setup.

Current server release: v3.2.0
Mobile preview: v3.2.0 on the alpha1 channel
Recommended deployment: Linux + Docker Compose + host-managed Cloudflare Tunnel

v3.0 distribution: Native Windows, Linux and macOS setup packages,
Windows Store packaging and Linux build-provenance verification. Desktop packages
retain the signing and device-qualification limits documented below.

The v2.7.0 release promoted the projects and Memory Agent preview to main
and returns to the 2.x release numbering after v6.5.0. It retains the stable
security updates, dependency maintenance and Memory Intelligence features.
See the changelog.
The v2.4.0 release added the read-only Gmail connector preview and restored
the Memory Inbox review page; see Gmail setup.

v3.2 adds project notifications for failed connectors and backups, important
conflicts and updates, stale credential documentation, and candidates waiting
for review. Read and dismiss state is personal to each administrator.
Notification behavior and thresholds.

Google Calendar sync imports an owned calendar through read-only OAuth and
bounded polling. Configure Google Calendar.

Highlights

  • PostgreSQL + pgvector memory store
  • Hybrid semantic + full-text retrieval
  • Query planning, graph-aware ranking and source-labelled context previews
  • Human-reviewed contradiction resolution that preserves historical facts
  • Local Ollama embeddings and local Qwen extraction
  • Secure browser sessions and scoped API keys
  • REST API + MCP
  • Versioned memories and soft-delete approval workflow
  • Bulk files, folders and safe ZIP ingestion
  • PDF, DOCX, TXT, Markdown, CSV, JSON, YAML and log extraction
  • ChatGPT export importer
  • Unified candidate Memory Inbox
  • Duplicate, related, update and conflict classification
  • Entity graph
  • Temporal / superseding memories
  • Dynamic memory scoring
  • Event timeline
  • Memory health checks
  • GitHub App continuous connector
  • Browser page / selection / link / note capture
  • Scheduled ingestion mesh with source provenance
  • OAuth authorization for MCP with PKCE and rotating refresh tokens
  • Client ID Metadata Documents and Protected Resource Metadata
  • Automated disaster-recovery restore testing
  • Backup integrity, retention and off-site replication monitoring
  • Administrator observability dashboard for project activity, latency and service readiness
  • MinIO source-document storage
  • Redis/RQ background workers
  • Caddy local gateway
  • Encrypted PostgreSQL and MinIO backup jobs
  • No direct public database, Redis, Ollama or MinIO ports

Architecture```text

                     INTERNET
                        |
                Cloudflare HTTPS/WAF
                        |
             host cloudflared service
                        |
                127.0.0.1:8080
                        |
                  Caddy Gateway
                   /         \
                  /           \
           Next.js Web     FastAPI
                              |
          +-------------------+-------------------+
          |          |             |              |
      PostgreSQL    Redis         Ollama          MinIO
      + pgvector     RQ       embeddings/Qwen   documents

`backend` is an internal Docker network. Ollama also joins a dedicated `egress`
network so models can be pulled without exposing Ollama publicly.

## Quick start```bash
git clone https://github.com/Jxyden34/Engram.git
cd Engram

cp .env.example .env
nano .env

Generate independent secrets:```bash
openssl rand -hex 32
openssl rand -hex 32
openssl rand -hex 32
openssl rand -hex 32


Use those values for PostgreSQL, Redis, MinIO and backup encryption. Keep matching
credentials consistent inside `DATABASE_URL`, `REDIS_URL` and MinIO settings.

Start the stack:```bash
docker compose up -d --build

Pull local models:```bash
docker compose exec ollama ollama pull all-minilm
docker compose exec ollama ollama pull qwen3:4b


Create an administrator:```bash
docker compose exec -it api python scripts/create_admin.py

Health check:```bash
curl http://127.0.0.1:8080/health


v3.0.2 reduces the sidebar to four main sections with related page subtabs inside each one. **Health & about** shows the live server and web versions, service readiness and project memory quality. New installer packages include the Memory Quality fix.

## Native installers — v3.0

The setup wizard bundles prebuilt Engram application images, generates private
configuration and independent secrets, creates your administrator and opens the login
page after checking health. You do not need Python or a local application build.
Docker must already be installed and running; third-party service images and optional
AI models download during setup. Existing installations are preserved.

| Platform | Package | Status |
| --- | --- | --- |
| Windows x64 | ZIP with a compiled setup EXE | Direct download remains unsigned; requires Docker Desktop with Linux containers |
| Windows Store x64 | MSIX plus Store identity metadata | Unsigned submission candidate with a preview identity until Partner Center is configured |
| Linux x64 / ARM64 | Separate tar.gz archives | Signed Sigstore build provenance and verification bundles; requires Docker Engine and Compose 2.24.4+ |
| macOS Intel / Apple Silicon | Separate DMG installers | Unsigned previews; requires Docker Desktop; Apple signing/notarization pending |

Get release packages from GitHub Releases.
Development builds remain available from the **v3 Installer Packages** workflow run
linked from installer PR #98. The pipeline exercises
fresh Linux installations, compiles and self-tests five native packages, validates
the MSIX with Microsoft's SDK and verifies Linux provenance. Desktop Docker setup
still needs device qualification; CI checks do not establish Store acceptance.

For Windows Store distribution, register a free individual developer account and
provide Partner Center's three identity values. Microsoft signs accepted Store
submissions; the direct-download EXE remains unsigned. On Linux, download the archive
and matching `.sigstore.json` bundle and follow the recorded GitHub CLI verification
command before running the installer.

See the installer guide for requirements, Store variables,
Linux verification and the Ubuntu/Debian one-line bootstrap. A matching v3 tag attaches
the packages, checksums and Linux provenance to a draft GitHub release for review
before publication. New Linux hosts can use:```sh
curl -fsSL https://raw.githubusercontent.com/Jxyden34/Engram/main/install.sh | sudo bash

This permanent top-level launcher selects the latest stable package automatically;
the command does not change for each release. A deployed instance can also serve it
at /install.sh. Use ENGRAM_INSTALL_VERSION only when deliberately pinning a release.
This requires an interactive terminal and a published package. Existing deployments
must follow the upgrade guide, not the fresh-install wizard.

Cloudflare Tunnel

Engram intentionally does not include a cloudflared container.

Run your existing host-level cloudflared service and configure a published
hostname to:```text
http://127.0.0.1:8080


That keeps the tunnel lifecycle separate from the application stack and avoids
putting the tunnel token in this repository.

## Upgrading an existing deployment

Database migrations live in `db/migrations/`.

Example:```bash
sudo docker compose exec -T db sh -lc \
  'psql -v ON_ERROR_STOP=1 -U "$POSTGRES_USER" -d "$POSTGRES_DB"' \
  < db/migrations/004_knowledge_core.sql

See docs/UPGRADING.md before applying migrations.

Repository layout```text

backend/ FastAPI, MCP, workers and knowledge logic
web/ Next.js dashboard
db/ bootstrap schema and migrations
gateway/ Caddy configuration
ops/ encrypted backup containers
docs/ architecture, deployment and operations docs
.github/ CI, Dependabot and contribution templates
docker-compose.yml production stack
.env.example safe configuration template
```

Documentation

  • Architecture
  • Deployment
  • Native installers, Windows Store setup and Linux verification
  • Upgrading
  • Backup and restore
  • Operations
  • Roadmap
  • Projects and Memory Agent beta
  • Portfolio & engineering evidence
  • Security policy
  • Contributing
  • Changelog

Security

This application can contain extremely sensitive personal information.

Never commit:

  • .env
  • API keys
  • Cloudflare tunnel tokens
  • database dumps
  • MinIO backups
  • ChatGPT exports
  • uploaded documents
  • production logs containing credentials

See SECURITY.md.

License

Engram is source-available and free for personal, noncommercial self-hosting.
Commercial, workplace and managed-hosting use require separate written permission.
See LICENSE and the usage guide.

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Engram 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Engram 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Engram 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Engram 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Engram 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Engram 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-20。