Memex

Name: Memex
Author: STiFLeR7

by STiFLeR7version 1.0.3i★ –iRuns on your computer

Registry nameio.github.STiFLeR7/memex

Install

Overview

Description from the maker (original English)

Temporal engineering context for agents via MCP.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: NEO4J_URI, NEO4J_USER, NEO4J_PASSWORD, GEMINI_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: NEO4J_URI, NEO4J_USER, NEO4J_PASSWORD, GEMINI_API_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "memex": {
      "command": "npx",
      "args": [
        "-y",
        "stifler-memex-mcp",
        "serve",
        "--repo",
        "."
      ],
      "env": {
        "NEO4J_URI": "your-value",
        "NEO4J_USER": "your-value",
        "NEO4J_PASSWORD": "your-value",
        "GEMINI_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add memex --env NEO4J_URI=your-value --env NEO4J_USER=your-value --env NEO4J_PASSWORD=your-value --env GEMINI_API_KEY=your-value -- npx -y stifler-memex-mcp serve --repo .

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "memex": {
      "command": "npx",
      "args": [
        "-y",
        "stifler-memex-mcp",
        "serve",
        "--repo",
        "."
      ],
      "env": {
        "NEO4J_URI": "your-value",
        "NEO4J_USER": "your-value",
        "NEO4J_PASSWORD": "your-value",
        "GEMINI_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "memex": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "stifler-memex-mcp",
        "serve",
        "--repo",
        "."
      ],
      "env": {
        "NEO4J_URI": "your-value",
        "NEO4J_USER": "your-value",
        "NEO4J_PASSWORD": "your-value",
        "GEMINI_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

NEO4J_URI required env
Bolt URI of your Neo4j instance
NEO4J_USER required env
Neo4j username
NEO4J_PASSWORD secret required env
Neo4j password
GEMINI_API_KEY secret required env
Google Gemini API key for entity extraction

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account STiFLeR7, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32655 servers in this category
Published to the registry more recently than 75% of the other 32655 servers in this category
Basic checks equal to or better than 100% of the other 32655 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Memex safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: NEO4J_URI, NEO4J_USER, NEO4J_PASSWORD, GEMINI_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.3) reached the registry 11 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, SuperCollider

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

SuperCollider

by Tok

Make sound with SuperCollider: synths, drums, chords, melodies and soundscapes over OSC.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

memex: trusted engineering context for agentic software engineering

Open-source MCP server and hook service that keeps Claude Code and Codex

engineering context current as the code changes, and holds edits whose

evidence changed.

[memex.stifler.in](https://memex.stifler.in)

A daemon, hook service and MCP server that turn commits and file changes into structured engineering knowledge and deliver it to agents with freshness and provenance preserved, without making memex a source of personal memory or raw session state.

memex builds a bitemporal knowledge graph of your repository (modules, symbols, decisions, problems, evidence, and code evolution). In v1 it also hooks into Claude Code and Codex: each session starts with the right context, each edit is checked against the current code, and the agent is told exactly what changed.

Where memex lives


Website	memex.stifler.in
Source	github.com/STiFLeR7/memex
Python package	`memex-mcp` on PyPI
Node package	`stifler-memex-mcp` on npm
MCP Registry	registry.modelcontextprotocol.io, listed as `io.github.STiFLeR7/memex`
Claude Code plugin	STiFLeR7/claude-plugins
Directories	Glama · AI Agents Listing

Evaluation record in BENCHMARK.md, release history in CHANGELOG.md, reporting process in SECURITY.md, and how to work on it in CONTRIBUTING.md.

https://github.com/user-attachments/assets/b14e3185-ea36-4ae5-bd18-2d34e6bf7be4

*memex v1 in 60 seconds. If the player does not load, download the video.*

Live context (v1)

Coding agents work from a snapshot of the code. A teammate pushes, another agent edits a file, a branch moves, and the agent keeps acting on what it read earlier. v1 keeps that snapshot current, inside Claude Code and Codex:

When	What memex does
Session start	Delivers a bounded working set for the task, and confirms delivery from the client's own session record
Before each edit	Checks whether the context the edit rests on still holds. If not, the edit is held, the agent gets a scoped correction, and it revises
On resume	If the code changed while the session was away, names the files to re-read
Parallel agents	Gives each linked worktree its own view, so agents side by side each see their own code
Trying it out	`memex v1 mode shadow` records what would be corrected without changing anything; hooks fail open; `memex v1 rollback` stops memex at once

uv tool install memex-mcp          # installs the `memex` command

cd your-repo memex v1 doctor # what is set up, what is missing, what to do next memex v1 install claude # hooks in .claude/settings.json; global settings untouched memex v1 install codex --neo4j-uri bolt://localhost:7687 # optional, for Codex

memex needs a Neo4j 5 server you already run (Docker is not required). Hooks go only into the checkout's own project configuration, and memex never asks for or stores your client credentials. Full guide, host recipes and rollback: docs/v1/25_ONBOARDING.md.

flowchart LR

A[Your repository files + git] --> B[memex watcher tree-sitter + Gemini] B --> C[Neo4j graph bitemporal facts] C --> D[memex core ContextPacket selection] D --> H[Hook service session start · edit checks · resume notice] D --> E[Hermes MemoryProvider automatic read-only prefetch] D --> F[MCP tools explicit lookup] H --> G[Claude Code / Codex] E --> G F --> G

style B fill:#cfe8ff,stroke:#0066cc,color:#000 style C fill:#fff4cf,stroke:#cc9900,color:#000 style H fill:#d4f5d4,stroke:#2d8f2d,color:#000

Install

Via Claude Code marketplace

/plugin marketplace add STiFLeR7/claude-plugins

/plugin install memex-mcp@stifler-marketplace

Restart your Claude Code session.

The first start after installing or upgrading downloads memex's Python dependencies (about 40 seconds), which can exceed Claude Code's MCP connect timeout once. Warm it up first, then restart:

npx -y stifler-memex-mcp --help     # one-time download; later starts take a few seconds

If Claude Code still shows a connection timeout, open /mcp and reconnect memex. If a tool says memex cannot reach Neo4j, start Neo4j (for example docker start memex-neo4j); the tools recover without a restart.

Manual

docker compose -f docker/docker-compose.yml up -d

cat > .env <<EOF NEO4J_URI=bolt://localhost:7687 NEO4J_USER=neo4j NEO4J_PASSWORD=memex-local GEMINI_API_KEY=your-key-here EOF npx stifler-memex-mcp init --repo . npx stifler-memex-mcp watch --repo . npx stifler-memex-mcp serve --repo .

Hermes integration

The Hermes integration is read-only. Hermes retains personal memory, raw session state, and execution state. memex supplies repository engineering context through a bounded ContextPacket; it does not ingest Hermes state.db, transcripts, prompts, or tool results.

Add the memex provider to Hermes' profile configuration:

memory:

provider: memex plugins: memex: repo_path: /absolute/path/to/repository prefetch_timeout_seconds: 7 max_items: 8 max_chars: 12000

If Hermes is not installed, use the same context selector through the MCP get_engineering_context tool. Both paths share the protocol-neutral memex core and fail open when retrieval is unavailable.

Channel	Command
Claude Code marketplace	`/plugin install memex-mcp@stifler-marketplace`
npx (no install)	`npx stifler-memex-mcp`
uv	`uv add memex-mcp`
pip	`pip install memex-mcp`
source	`git clone github.com/STiFLeR7/memex && uv sync`

Self-hosted team deployment

For a shared team setup (one Neo4j + one memex-server, auth on by default, Neo4j's ports never exposed to the host):

bash docker/bootstrap-team-env.sh

docker compose -f docker/docker-compose.team.yml up -d

See docker/TEAM-DEPLOY.md for the full flow, capturing the initial admin key, and the down -v footgun to avoid.

At a glance

Property	Value
Output	A Neo4j graph populated continuously from your repo
Storage	Neo4j via Graphiti. Bitemporal: every edge has `created_at` and optional `expired_at`
Context	Bounded, ranked, provenance-aware `ContextPacket`
Live context (v1)	Session-start working set, edit checks with scoped corrections, resume change notice, per-worktree views (Claude Code and Codex hooks)
Integrations	Hermes MemoryProvider, MCP resources/tools, Claude Code, Cursor, Codex, Gemini CLI
Failure mode	Fail-open; agent execution continues without memex
Granularity	Scales from 50 to 5000+ modules via hierarchical Leiden clusters
Synthesis	Gemini Flash distills commits into `Decision` nodes; Pro for grounded synthesis
Confidence	Computed at query time. Two-regime decay (validated half-life ~139d, unvalidated stale at 30d)
Write governance	Per-node-type ACL, intent-confirmation on agent writes, explicit `corroborates` / `supersedes` semantics
Goal 10 evidence	8/8 valid paired runs, 0 treatment failures, 0 treatment regressions

The lifecycle

flowchart TD

Init[memex init extract baseline] --> Watch[memex watch daemon + git hooks] Watch -->|commit| Extract[tree-sitter extract symbols, imports, lockfile] Extract --> Synth[Gemini Flash diff → Decision nodes] Synth --> Write[Graphiti add_episode

post-hoc bitemporal SET] Write --> Decay[Scheduler

nightly confidence decay] Decay -->|stale edges| Archive[expired_at = now]

Cluster[memex cluster Leiden over hybrid edges] -.->|every N commits| Write

style Init fill:#e8f4ff,color:#000 style Watch fill:#fff4cf,color:#000 style Synth fill:#ffe0cc,color:#000 style Serve fill:#d4f5d4,color:#000

MCP tools

14 tools: eight read, four write, two analytic.

Read

Tool	When
`get_project_context`	Session start. Returns a cluster-level briefing under 1500 tokens regardless of repo size
`get_symbol_context`	Before editing a function or class. Returns callers, callees, linked decisions
`get_recent_decisions`	Last N days of architectural decisions, optionally module-scoped
`get_open_problems`	Active bugs and tech debt, sorted by severity
`search_context`	Hybrid search: semantic × keyword × graph traversal × RRF merge
`get_stale_context`	Edges whose composite confidence dropped below threshold
`explain_change`	Given a commit SHA, cross-references the diff with linked Decision/Problem nodes and asks Gemini Pro for a grounded explanation
`predict_impact`	Given a file path, returns a ranked list of modules likely affected based on graph coupling (no LLM call)

Write

Tool	When
`record_decision`	After making a technical choice. Supports `corroborates` (reinforce) and `supersedes` (replace)
`record_problem`	When discovering a bug or piece of tech debt
`resolve_problem`	When a tracked problem is fixed
`invalidate_edge`	When a stored fact is no longer true

Bitemporal confidence

Confidence is not a stored number that mutates. It is computed at query time from base_confidence, validation status, time since last reinforcement, and access count.

flowchart LR

Edge[Edge created base_confidence] --> Q{Validated by a human?} Q -->|yes| Slow[Slow regime half-life ~139d] Q -->|no| Fast[Fas

Only the beginning is shown; read the rest in the repo

Memex

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

SuperCollider

README from the maker

memex: trusted engineering context for agentic software engineering

Where memex lives

Live context (v1)

Install

Via Claude Code marketplace

Manual

Hermes integration

Self-hosted team deployment

At a glance

The lifecycle

MCP tools

Read

Write

Bitemporal confidence