Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Read-only visualization for Cortex memory, knowledge, sessions, traces, and codebase graphs.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
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": {
"hypermnesia-viz": {
"command": "uvx",
"args": [
"hypermnesia-mcp-viz"
]
}
}
}Run this in your terminal
claude mcp add hypermnesia-viz -- uvx hypermnesia-mcp-vizPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"hypermnesia-viz": {
"command": "uvx",
"args": [
"hypermnesia-mcp-viz"
]
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"hypermnesia-viz": {
"type": "stdio",
"command": "uvx",
"args": [
"hypermnesia-mcp-viz"
]
}
}
}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.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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 8, 2026
The registry name was verified with the GitHub account cdeust, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed –, and the latest version (3.2.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
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.
Hypermnesia MCP Viz is published as `hypermnesia-mcp-viz` everywhere: Python, MCP Registry, Claude Code, Codex, Gemini, and the console command.
The cross-platform visualization layer for [Cortex](https://github.com/cdeust/Cortex). Codex, Gemini CLI, Claude Code, and any stdio MCP host can launch the same read-only server and browser UI. It turns Cortex's memory store, a host-neutral live activity stream, Claude Code's historical session archive, and your codebase graph into six live reading angles: a project galaxy, a 3D anatomical brain, an execution trace, a consolidation kanban, a curated knowledge browser, and a wiki. It never writes a memory: it renders, it never remembers. (It does keep its own derived graph/layout caches in the Cortex database, listed under Boundary.)
Launch with the open_visualization tool (or /cortex-visualize). One launcher opens six reading angles; the default landing view is Trace.
The whole UI ships on the AI Architect design system: a paper-first reading surface with a persistent ink (night) toggle, greyscale chrome, and a data palette resolved from design tokens at runtime, flipping the surface re-inks every view in place without disturbing a settled layout, and every count on screen is exact and streamed, never rounded.
Python 3.11 or newer is required. Upgrade Python 3.10 installations before updating: the fixed Pillow 13 release requires Python 3.11.
Claude Code users can install Hypermnesia MCP Viz from the same cortex-plugins marketplace as Cortex:
claude plugin marketplace add cdeust/Cortex
claude plugin install hypermnesia-mcp-viz@cortex-plugins
This install name becomes available in the Cortex marketplace only when this repository and the matching marketplace change in cdeust/Cortex#351 are released together. Maintainers must not publish either half of the rename on its own.
cortex-vizExisting Claude Code installs are not aliases for the new plugin identity. Remove the old install, refresh the marketplace after the coordinated release, and install the canonical plugin:
claude plugin uninstall cortex-viz@cortex-plugins
claude plugin marketplace update cortex-plugins claude plugin install hypermnesia-mcp-viz@cortex-plugins
Claude composes plugin tool names from the plugin manifest name, the mcpServers key, and the tool name. Update both old full names wherever they appear in permission allowlists, hooks, skills, or agents:
mcp__plugin_cortex-viz_cortex-viz__open_visualization becomes mcp__plugin_hypermnesia-mcp-viz_hypermnesia-mcp-viz__open_visualization.mcp__plugin_cortex-viz_cortex-viz__get_methodology_graph becomes mcp__plugin_hypermnesia-mcp-viz_hypermnesia-mcp-viz__get_methodology_graph.The removed cortex-viz console command is not retained as an alias, so Cursor, Windsurf, VS Code, and other direct-process configurations must invoke hypermnesia-mcp-viz instead.
Hypermnesia MCP Viz is a companion to [Cortex](https://github.com/cdeust/Cortex) that never writes a memory. Install Cortex first (
claude plugin install hypermnesia-mcp@cortex-plugins): the visualizer reads its shared PostgreSQL store, and writes only its own derived caches there (Boundary). Point both at the same database: thedatabase_urlplugin setting defaults topostgresql://127.0.0.1:5432/cortex; set it to the same value you gave Cortex.
Restart your Claude Code session, then launch the visualizer:
/cortex-visualize
Codex, Gemini CLI, and other MCP hosts launch the same server as a plain stdio process; see Other MCP hosts for the exact configuration.
One launcher opens all six reading angles (Graph · Brain · Trace · Knowledge · Wiki · Board) in the browser, served live from the Cortex store, your session JSONL, the code graph, and git.
No Cortex, no PostgreSQL, no setup: Hypermnesia MCP Viz is still useful on its own. The Trace view (the default landing view) reads only ~/.claude/projects/*.jsonl and your local git: every Claude Code session becomes a navigable domain → session → prompt → action → file chain, with per-file diffs and commit history. If you use Claude Code, the data is already on your disk.
/cortex-visualize. When Cortex's database isn't reachable, the server logs one line and starts in no-DB mode automatically: Trace is fully live; the five DB-backed views (Graph, Brain, Knowledge, Wiki, Board) appear greyed out with an install pointer instead of erroring.CORTEX_VIZ_NO_DB=1 (or pass --no-db when running the standalone server directly).Installing Cortex later lights up the other five views against the same UI (no reconfiguration).
More options (Clone, manual run)
Clone + run from source:
git clone https://github.com/cdeust/cortex-viz.git && cd cortex-viz
pip install -e . DATABASE_URL=postgresql://127.0.0.1:5432/cortex python3 -m cortex_viz
CORTEX_VIZ_NO_DB=1 python3 -m cortex_viz
Each project becomes a cloud of nodes around one gold domain hub. Inside every cloud, nodes sit in six concentric levels by the Claude surface (or the code itself) that produced them:
| Level | What's there | Click through to |
|---|---|---|
| L1 · Setup | Skills · Commands · Hooks · Agents · MCPs | File paths; which domains share an MCP (thin indigo bridges) |
| L2 · Tools | One hub per Claude tool per domain (Edit · Write · Read · Grep · Glob · Bash · Task) | Files touched + total uses |
| L3 · Files | Every file Claude opened, read, edited, searched, or referenced, colored by primary tool | first_seen / last_accessed / last_modified + See diff against HEAD |
| L4 · Discussions | One node per Claude Code session | started_at, duration, message count + View full conversation replay |
| L5 · Memories | Persistent memories, colored by consolidation stage | Full content, tags, every scientific measurement |
| L6 · AST symbols | The code itself: functions, methods, classes, modules, constants parsed from 10 languages (Rust, Python, TypeScript, Java, Kotlin, Swift, Objective-C, C, C++, Go) | Qualified name, symbol type, parent file, and named defined_in / calls / imports / member_of edges |
Why L6 matters. L5 and below tell you *what Claude did*; L6 tells you *what the code is*. Three things become visible for free: shared code (any symbol referenced by two projects drifts into the inter-project gap), impact (clicking a symbol surfaces every caller, importer, and member: "what breaks if I change this?" is a graph neighbourhood, not a grep), and the shape of the codebase itself (a dense petal around a file means a fat internal API; a thin one means a leaf module). A grouped filter (L1–L6 / by kind / by AST edge kind / Cross-domain) isolates any slice.
The same graph, on a second surface: every node placed inside an anatomical cortical mesh by the neuroscience of memory systems rather than by force-direction. Episodic memories sit in the medial temporal lobe and migrate outward to neocortex along a hot→consolidated depth gradient (the complementary-learning-systems consolidation model); semantic entities in temporal neocortex; code symbols in association cortex; procedural skills in the striatum and cerebellum; domains at the connectome's rich-club hubs. Region centres are registered from real MNI152 atlas coordinates (affine fit, not vertex-exact; the mesh is a single unlabeled surface). Every synapse routes along a major white-matter tract (fornix, uncinate, SLF, corpus callosum). Node colour is the same semantic palette as the galaxy (memories by consolidation stage, entities/symbols by type), and a live Memory science panel mirrors the store's system vitals (consolidation pipeline, skills, source-monitoring, extinction, sleep phases, and every mechanism Cortex exposes).
Because the full graph (278k+ nodes, 5.5M edges) is far larger than a browser can take in one payload, the brain streams it in progressively through a bounded-queue, frame-budgeted NDJSON loader: the cloud fills in as you watch. Clicking any node opens the same rich detail card as the galaxy (content, tags, live heat, relations, git diff, impact). Open it from the Brain button in the view bar, directly at /brain, or programmatically via open_visualization(view="brain").
Five columns by consolidation stage (labile · early_ltp · late_ltp · consolidated · reconsolidating). Each header states the stage's live count (server-side truth, not the loaded page) above its reference stage physics (decay ×, vulnerability %, plasticity %) and the stage's advancement rule (e.g. replays ≥ 1 or imp > 0.3 at `lab
Only the beginning is shown; read the rest in the repo