aide-memory

Name: aide-memory
Author: aide-memory

by aide-memoryversion 0.6.3i★ –iRuns on your computer

Registry nameio.github.aide-memory/aide-memory

Install

Overview

Description from the maker (original English)

Persistent memory layer for AI coding agents — your agent remembers what you taught it.

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: Search & AI memory

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).
The registry lists no key to fill in.

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": {
    "aide-memory": {
      "command": "npx",
      "args": [
        "-y",
        "aide-memory",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add aide-memory -- npx -y aide-memory mcp

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "aide-memory": {
      "command": "npx",
      "args": [
        "-y",
        "aide-memory",
        "mcp"
      ]
    }
  }
}

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": {
    "aide-memory": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "aide-memory",
        "mcp"
      ]
    }
  }
}

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.

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 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account aide-memory, 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 Search & AI memoryi

More stars than 0% of the other 7223 servers in this category
Published to the registry more recently than 18% of the other 7223 servers in this category
Basic checks equal to or better than 100% of the other 7223 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 aide-memory 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?

The registry does not list a required key, though some servers ask you to sign in on first use.

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 (0.6.3) reached the registry 5 months 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 on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

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

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated 3 days ago

Install

Codebase Memory

by DeusData

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

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

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

Runs in the cloud★ 5,213MITUpdated 44 days ago

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.

aide-memory

Auto-captured, auto-recalled, path-scoped memory for AI coding agents and teams.

Website: https://aide-memory.dev

Docs: https://aide-memory.dev/docs

Install: npm install -g aide-memory && aide-memory init

The problem

Coding with agents has made developers significantly more productive. But it's created a new kind of friction.

You explain how the feature you're building ties into the rest of the system, the way you like to structure your code, the patterns to follow in this area. The agent gets it. You ship great work together. Next session, it's a blank slate. You re-explain the same things.

Critical decisions being made during conversations aren't being captured. Preferences, corrections, area knowledge, guidelines. So much valuable context doesn't persist, doesn't flow to the next session, to a different tool, or to a teammate's agent when they pick up work in the same area.

Rules files (CLAUDE.md, .cursorrules) help, but they have real limits:

No unified convention or structure. A team guideline, a personal preference, an area decision, and a stack fact all blur into one file. The whole file gets injected on every turn, even when most of it might not be relevant to the area the agent is working in.
Corrections don't make it back. What you teach the agent in conversation doesn't make it back into the rules file on its own.
Tool-specific. What you teach your agent in Claude Code doesn't carry to Cursor unless you copy the file over manually.
Unscoped recall. The whole file lands in context, or nothing does. There's no prompt for the agent to pull a relevant subset based on the file it just opened.

aide-memory fills these gaps. It sits alongside your rules files, not above or below. Rules files for static, always-on guidance. aide-memory for the dynamic, scoped knowledge that grows with the codebase.

How it works

Capture happens automatically

Six hooks fire across the session lifecycle, installed by aide-memory init:

UserPromptSubmit: detects corrections ("no, use X instead") and prompts the agent to store them scoped to the code area
Stop: periodic reflection ("anything worth remembering?") on a tunable schedule picks up decisions and findings
SessionStart: injects top preferences, guidelines, and priority-always memories so the agent starts with context
PreToolUse: before the agent reads or edits a file, checks if relevant memories exist for that path and prompts recall
PostToolUse: records what was recalled so re-reads don't re-prompt
PreCompact: clears session tracking before context compaction so post-compact reads re-prompt cleanly

Recall is scoped

Memories attach to code areas via glob scopes (src/components/dashboard/**, packages/api/**). When the agent opens a file, aide-memory matches the path against stored scopes and surfaces what's relevant to that area.

Four layers organize the knowledge:

Layer	What it captures	Example
preferences	How a contributor likes to work	"Prefer modular component structure, separate concerns into smaller files"
technical	Facts not obvious from code	"Dashboard data fetching uses React Query with stale-while-revalidate"
area_context	Decisions tied to code areas	"Settings panel uses progressive disclosure; new sections follow the expand/collapse pattern"
guidelines	Team-wide principles	"Mock external calls at the network boundary in tests, not at the function boundary"

Recall ranks area_context first (most specific), then technical, then preferences, then guidelines. Scoped memories rank above project-wide ones.

Git-synced for teams

Memories are JSON files under .aide/memories/. Commit, push, pull. A post-checkout git hook rebuilds the local cache after git pull so your teammate's agent picks up your context on their next file read. Personal preferences (preferences/personal/) are gitignored. Team conventions travel with the repo.

Cross-tool

Claude Code and Cursor read the same .aide/memories/ directory. A memory captured in one tool is available in the other. Codex, Copilot, and Windsurf get a rules template at launch; deeper integration may come based on user feedback.

Quick start

# 1. Install and initialize

npm install -g aide-memory aide-memory init

2. Restart your editor so the MCP server registers

Claude Code: start a fresh session

Cursor: Cmd+Q, reopen, enable in Settings > MCP

3. Store a memory

aide-memory remember "Dashboard uses skeleton loading, not spinners" \ --layer area_context --scope "src/components/dashboard/**"

4. Recall context for a path

aide-memory recall src/components/dashboard/

5. Share with your team

git add .aide/memories/ git commit -m "Capture dashboard conventions" git push

Full walkthrough: https://aide-memory.dev/docs/quick-start

What's in the box

7 MCP tools: aide_recall, aide_remember, aide_update, aide_forget, aide_search, aide_memories, aide_import
13 CLI commands: init, recall, remember, update, forget, search, list, stats, recall-log, config, sync, migrate, cleanup
6 hooks wired into the editor at init
4 typed memory layers with personal/shared split for preferences
FTS5 keyword search plus optional semantic search via Transformers.js or Ollama

Tunable

aide-memory ships with defaults you can adjust:

How often the agent gets prompted to reflect and store context
How specific a scope needs to be before a memory surfaces per-file vs session-start-only
How much context gets injected at session start
Which hooks are active (disable per-file blocking, turn off correction detection)
Personal vs shared preferences (gitignored or committed, configurable per-project)

aide-memory init seeds .aide/config.json with all public settings. Full reference: https://aide-memory.dev/docs/configuration

Privacy

Memory content stays on your machine. Anonymized usage counts (event type, hashed machine ID, platform, Node version) ship to PostHog by default so we can see which features are used. Disable with AIDE_TELEMETRY=off.

Editor support

Editor	Status
Claude Code	Reference adapter. Start a fresh session after `init` so the MCP server registers.
Cursor	Full hook + MCP wiring. Cmd+Q and reopen after `init`, then toggle aide-memory ON in Settings > MCP.
Windsurf, Codex, Copilot	Rules template at launch. Deeper integration may come based on user feedback.

Per-editor details: https://aide-memory.dev/docs/supported-editors

Requirements

Node.js 18 or later
npm or npx

No Docker. No external databases. No API keys. No cloud accounts.

License

Free to use. See LICENSE for terms.

Documentation

Full docs: https://aide-memory.dev

aide-memory

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

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 Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

aide-memory

The problem

How it works

Capture happens automatically

Recall is scoped

Git-synced for teams

Cross-tool

Quick start

2. Restart your editor so the MCP server registers

Claude Code: start a fresh session

Cursor: Cmd+Q, reopen, enable in Settings > MCP

3. Store a memory

4. Recall context for a path

5. Share with your team

What's in the box

Tunable

Privacy

Editor support

Requirements

License

Documentation