"Information about project memory" matching MCP servers:

Enables coding agents to persist notes, decisions, requirements, and learnings per project in SQLite and retrieve them across sessions via search and status tools.

Project Memory stores decisions, evidence, outcomes and reviewed lessons in local SQLite. Assistants retrieve bounded context through three MCP tools. People follow and plan work in a live workspace with an overview, sprint board, decision history, readable documents, skills and project maps. Offline exports remain available.

Provides AI-driven project memory management through structured prompts that help Claude parse tasks from specs, review code changes, sync with commit history, and maintain project documentation without directly accessing files.

Local MCP server giving AI coding agents (Claude Code, Cursor, VS Code/JetBrains Copilot) a shared, persistent memory of your projects and every bug/issue faced during development. Stateless, plain-file storage (AGENTS.md + issues.jsonl) — no database.

A persistent memory implementation using a local knowledge graph that lets Claude remember information about users across conversations.

A local MCP server that gives AI assistants persistent long-term memory using a biological neural architecture with cortex, synapses, and hippocampus.

Provides versioned, structured memory for AI agents, allowing them to store facts, detect conflicts, and track knowledge history via a hosted SaaS platform. It enables efficient hierarchical information retrieval and semantic search while keeping token usage constant as memory scales.

MCP server exposing memory search, index, and stats tools for agents, with honesty guards to prevent re-litigation of settled decisions.

Analyzes Python project structure by exploring directory trees, extracting outlines from Python and Markdown files, and inspecting OpenAPI specifications.

MCP server for managing project memory in AGENTS.md. Allows agents to record and remove durable facts using save/forget tools.

Exposes local memory vaults as 6 MCP tools over stdio, enabling clients like Windsurf, Zed, and Claude Desktop to read and write memory.

Hand a project over — to your next session, to Cursor/Codex/Gemini, to your successor — with the reasons attached. Local-first memory MCP for coding agents: decisions re-injected before the agent acts, drift detection across every project you run. One SQLite file, nothing leaves your machine.

Embedded, local-first agent memory: facts extracted into a per-namespace SQLite file (vec0 + FTS5) with hybrid retrieval and point-in-time (time-travel) queries. ADD-only history over stdio — no server process, no cloud dependency.

A read-only MCP server that lets Claude read and search source code from local project folders, with path containment security.

A lightweight, local memory server for AI coding assistants that stores durable knowledge (decisions, facts, gotchas) in a tree structure, enabling persistent context across sessions with efficient retrieval via summaries and FTS5 search.

Local memory for coding agents that can refuse, not only recall. A rule carrying a machine-checkable proof blocks the matching command before it runs, while prose-only rules can warn but never block.

Dynamic semantic memory for AI assistants that persists across sessions and clients, enabling natural language recall and project-scoped isolation.

An improved implementation of persistent memory using a local knowledge graph with a customizable --memory-path. This lets Claude remember information about the user across chats.

MCP server providing persistent memory for AI applications, enabling Claude to store and recall memories with hybrid search and knowledge graph.

Persistent long-term memory for AI agents — semantic recall across Claude, Cursor, ChatGPT & MCP.