Memex

Name: Memex
Author: dioniipereyraa

作者：dioniipereyraa版本 0.2.3i★ –i在你的电脑上运行

注册名称io.github.dioniipereyraa/memex

安装

概览

作者提供的说明（英文原文）

One searchable memory of your Claude.ai chats and Claude Code sessions, served over MCP.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 搜索与 AI 记忆

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "memex": {
      "command": "uvx",
      "args": [
        "memex-chats"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add memex -- uvx memex-chats

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "memex": {
      "command": "uvx",
      "args": [
        "memex-chats"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "memex": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "memex-chats"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 dioniipereyraa 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“搜索与 AI 记忆”中的其他服务器比较i

星标数多于此分类中其他 7286 个服务器的 0%
发布到注册中心的时间比此分类中其他 7286 个服务器的 17% 更新
基础检查结果等于或优于此分类中其他 7286 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Memex 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.2.3）于5个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Context7, Codebase Memory, Exa

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

作者：upstash

Up-to-date docs for AI agents

电脑或云端★ 64,224MIT昨天更新

安装

Codebase Memory

作者：DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

在你的电脑上运行★ 48,148MIT21天前更新

安装

Exa

作者：exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

在云端运行★ 5,213MIT上个月更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Memex

Your Claude.ai chats and your Claude Code sessions live in two worlds that never talk. Memex makes them one memory you can search from both.

Local-first MCP server that indexes your Claude.ai chat history and your local Claude Code / terminal sessions, and exposes them to Claude Code (stdio) and Claude.ai (remote MCP connector).

Status: alpha, 0.3.1 on PyPI. Phases 0 to 7 closed, security-audited (plus four adversarial red-team rounds). Shipped: hybrid search, live capture, auto-summaries, chat ↔ repo association, the Claude.ai remote connector (GitHub OAuth), Claude Code / terminal ingestion with secret redaction, one-command setup, cross-platform autostart, and one-click claude.ai history backfill.

*End-to-end demo: from Claude Code, you ask about something you discussed on claude.ai. Memex searches your chat history (search_chats) and Claude answers from the real conversation. No copy-paste, no manual context handoff.*

Install

One command installs uv + Memex and runs memex setup (registers the MCP server, installs the always-on capture service, indexes your local sessions, prints the pairing token):

# macOS / Linux

curl -LsSf https://raw.githubusercontent.com/dioniipereyraa/memex/main/scripts/install-pypi.sh | sh

# Windows (PowerShell)

powershell -ExecutionPolicy ByPass -c "irm https://raw.githubusercontent.com/dioniipereyraa/memex/main/scripts/install-pypi.ps1 | iex"

Then the one browser step a terminal cannot do: install the Chrome extension, paste the token it printed, and click "Backfill claude.ai history". Other paths (pipx, uv tool install, from source) are under Installation.

The problem

Brainstorming and planning happen in Claude.ai. Execution happens in Claude Code. The two worlds do not talk to each other: Claude Code cannot read a chat of yours from Claude.ai, not even the one that originated the task it is currently working on. The memory Anthropic shipped on Claude.ai (March 2026) is curated, not full history, and lives isolated inside Claude.ai.

Memex fills that gap: runs locally, indexes the entire corpus of your chats, and exposes them as MCP tools so Claude can search and pull past context whenever it needs to.

How it works

[Claude.ai]

↓ (official JSON export / Chrome ext) [Ingestor] → [SQLite + sqlite-vec] → [local embeddings (fastembed / Ollama)] ↓ [core: storage + retrieval] ↓ [MCP stdio] ───→ Claude Code, Claude Desktop [MCP Streamable HTTP] ─→ Claude.ai connector

Design: pure core (storage, ingest, embeddings, retrieval) decoupled from transport. The same engine serves both stdio and remote MCP without a rewrite.

Installation

Quick install (one command)

Installs uv if needed (it brings the right Python), installs Memex from PyPI, and runs memex setup to wire it into Claude Code (MCP server + always-on capture service + local session indexing + the pairing token). No git clone required.

# macOS / Linux

curl -LsSf https://raw.githubusercontent.com/dioniipereyraa/memex/main/scripts/install-pypi.sh | sh

# Windows (PowerShell)

powershell -ExecutionPolicy ByPass -c "irm https://raw.githubusercontent.com/dioniipereyraa/memex/main/scripts/install-pypi.ps1 | iex"

The only step a terminal cannot do is the browser one: install the Chrome extension, paste the token the installer prints, and click "Backfill claude.ai history" to import your history. Embeddings work out of the box (a quantized 130 MB fastembed model downloads on first ingest; no Ollama, no API key).

A plain pipx install memex-chats (or uv tool install memex-chats) followed

by memex setup does the same thing in two steps. The autostart service is

generated for the wheel install too (launchd / systemd / a logon Scheduled

Task), so no clone is needed for it.

From source (for development)

Clone the repo to get an editable install plus the extension source and service templates. You need git; the script installs uv and the pinned Python for you.

macOS / Linux

git clone https://github.com/dioniipereyraa/memex

cd memex ./scripts/install.sh

install.sh installs uv if you do not have it, runs uv sync, and verifies the install with memex doctor. That is the whole setup.

Windows (PowerShell)

git clone https://github.com/dioniipereyraa/memex

cd memex powershell -ExecutionPolicy Bypass -File .\scripts\install.ps1

Same three steps as the macOS script (install uv, sync, verify). If git is not installed, get it from git-scm.com first.

Manual (any OS, if you prefer explicit steps)

# 1. Install uv (skip if you already have it):

macOS/Linux: curl -LsSf https://astral.sh/uv/install.sh | sh

Windows: powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

git clone https://github.com/dioniipereyraa/memex cd memex uv sync # installs Python 3.13 + dependencies into .venv uv run memex doctor # verify

Upgrading (already have memex)

Upgrade with the same tool that installed it, or the new version will not land on your PATH. A previous install owns the memex executable, so installing again with a different manager fails with "Executables already exist" and memex keeps running the old version. (This is the usual reason memex sync seems to "not exist" after an upgrade: an old pipx-owned memex shadowed a newer uv tool install.)

# 1. Find which tool owns it:

which memex # macOS / Linux Get-Command memex # Windows (PowerShell)

2. Upgrade with that tool:

pipx upgrade memex-chats # if pipx owns it uv tool upgrade memex-chats # if uv owns it

If you want to switch managers, uninstall the old one first (pipx uninstall memex-chats or uv tool uninstall memex-chats), then reinstall. After upgrading, memex --version shows the new version and memex doctor should pass.

Multi-device (optional)

To make Claude one memory across several machines, install Tailscale first (so each device has a stable private address), then opt in once per device:

memex setup --sync     # opt-in, persisted: the always-on service is sync-reachable

It prints the single memex sync connect ... line to run on your other devices. The choice is saved, so the service stays sync-reachable across reboots without re-running anything. Full flow, security model, and the manual one-shot alternative are in Syncing across your devices.

For a dual-boot machine (Linux and Windows that are never on at the same time), use file-based sync instead: memex setup --sync-dir on each OS, pointed at the same folder. No Tailscale, no two devices online at once. See Dual-boot or never-online-together.

First run

The fast path is one command:

uv run memex setup

memex setup wires everything end to end and is safe to re-run: it registers the MCP server with Claude Code (claude mcp add), installs the always-on live-capture service (launchd on macOS, systemd on Linux, a Scheduled Task on Windows), indexes your local Claude Code sessions, and prints the access token to paste into the Chrome extension. Each step degrades to a warning instead of aborting the rest. Flags: --no-mcp, --no-autostart, --no-ingest, --remote (also install the claude.ai connector agent), -y (no prompt).

After that, the only manual step left is installing the Chrome extension and pasting the token, so new chats are captured as you go.

Manual steps (if you prefer to run them yourself)

# 1. Request your official Claude.ai export (Settings → Privacy → Export data),

then ingest it (first run downloads the embedding model, ~30s):

uv run memex ingest /path/to/your-export.zip

2. Optionally index your local Claude Code / terminal sessions:

uv run memex ingest-claude-code

3. Search, or wire it into Claude Code (see "Wiring it into Claude Code"):

uv run memex search "your query" -n 5 uv run memex stats

(If you installed with a script, the commands above work as written. If you installed the published PyPI package instead, drop the uv run prefix.)

Where your data lives. From a cloned repo, the database and exports stay

in /data. From a uvx/pip install, they go to your OS data

directory (~/Library/Application Support/memex on macOS,

%LOCALAPPDATA%\memex on Windows, ~/.local/share/memex elsewhere). Override

with MEMEX_DB_PATH / MEMEX_EXPORTS_DIR. memex doctor prints the resolved

path.

Using Memex (after setup)

Once memex setup finishes, nothing else needs launching: the capture server and the indexers run in the background. You use Memex three ways.

1. From Claude Code (the main way). Setup registers the MCP server, so Claude Code can search your whole history and keep it fresh through these tools:

Tool	What it does
`search_chats`	Semantic + keyword search across your claude.ai chats AND Claude Code sessions
`get_chat`	Fetch a full conversation by id
`list_recent_chats`	Your most recent conversations
`find_related`	Conversations related to a topic or snippet
`index_terminal_sessions`	Index your local Claude Code sessions now (so the current one becomes searchable)
`sync_now`	Sync with your other devices now (paired peers + the dual-boot shared folder)

Just ask Claude Code naturally ("what did we decide about X in my claude.ai chats?", "index this session", "sync this to my other devices") and it calls these. index_terminal_sessions and sync_now are local-only (never exposed to the remote claude.ai connector). Note sync_now sends what is already indexed, so to include the session you are in, ask Claude to index_terminal_sessions first. To have context injected automatically at the start of a session, add the optional SessionStart hook.

2. From the terminal. memex search "...", memex stats, memex doctor, memex token (re-print the extension pairing token), memex --version.

3. Capture (automatic, you run nothing). The Chrome extension indexes a claude.ai chat as you open or reload it (and its "Backfill" button imports your old history once); your Claude Code sessions are indexed when a session ends, plus a 15-minute backstop.

How fresh is the data (real-time)?

Path	Latency
A claude.ai chat into your local index	Near-instant: captured as you open/reload the chat (embedded in seconds)
A Claude Code session into your local index	At session end, plus a 15-minute backstop
Available to Claude Code on the same machine	Immediate (it reads the same local DB the capture writes)
Across devices	Not live. Periodic + overlap: see below

Same-machine is essentially real-time. Cross-device is not a live relay (it is peer-to-peer with no cloud): paired devices auto-reconcile every 15 minutes while

只显示了开头部分；其余内容请在仓库中阅读

Memex

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“搜索与 AI 记忆”中的其他服务器比较i

常见问题

替代选择

Context7

Codebase Memory

Exa

作者的 README

Memex

Install

The problem

How it works

Installation

Quick install (one command)

From source (for development)

macOS / Linux

Windows (PowerShell)

Manual (any OS, if you prefer explicit steps)

macOS/Linux: curl -LsSf https://astral.sh/uv/install.sh | sh

Windows: powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

Upgrading (already have memex)

2. Upgrade with that tool:

Multi-device (optional)

First run

Manual steps (if you prefer to run them yourself)

then ingest it (first run downloads the embedding model, ~30s):

2. Optionally index your local Claude Code / terminal sessions:

3. Search, or wire it into Claude Code (see "Wiring it into Claude Code"):

Using Memex (after setup)

How fresh is the data (real-time)?