"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.

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 basic implementation of persistent memory using a local knowledge graph. This lets Claude remember information about the user across chats.

Persistent AI knowledge base for Claude via Model Context Protocol — fully offline, no cloud API key required. Stores architectural decisions, technical debt, project progress, and domain knowledge in versioned Markdown files.

Provides a file-based, git-friendly memory store for coding agents to persist and recall project-specific lessons, bugs, and conventions via JSON files in the repository.

A persistent memory system using a local knowledge graph that enables Claude to remember information about users across chats, with advanced search, graph traversal, and filtering capabilities for entities, relations, and observations.

Local repository memory for Codex that indexes TypeScript/JavaScript structure into local SQLite, exposes compact MCP tools, and renders deterministic SVG/map frames.

An intelligent personal CRM that processes WhatsApp conversations to build a searchable knowledge base about contacts using diarization, transcription, and PII sanitization. It exposes MCP tools for semantic search, contact summaries, and reminder management within Claude Desktop.

An MCP server that implements Project Memory Protocol (PMP) to manage shared project memory in the .ai/ directory, providing 13 tools for project context, tasks, decisions, and conversation summaries.

Provides AI assistants with progressive code intelligence to explore repository structure, find symbols, and assess the impact of changes using ast-grep.

MCP server for system monitoring, enabling users to ask about CPU, memory, disk, network, and processes on their system.

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

MCP server with local vector search for your codebase. Smart indexing, semantic search, Git history — all offline.

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

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.

An MCP server that gives AI models a persistent notebook backed by a folder of Markdown files, with tools to discover, read, write, edit, and delete notes.

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.