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

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.

A persistent memory layer for Claude Code that maintains project information, technology stack, tasks, decisions, and session history between coding sessions, eliminating the need to re-explain project context.

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.

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

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.

Stores manual project memories, enables semantic retrieval, and tracks per-memory confidence using PostgreSQL with pgvector and OpenAI-compatible embeddings.

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.

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.

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.

Provides tools for managing project knowledge graphs, enabling structured representation of projects, tasks, milestones, resources, and team members.

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

A local-first MCP server that gives AI coding assistants persistent, structured, human-readable memory for a software project by storing project knowledge as Markdown files in the project's .dev-context-memory/ folder.

Enables AI coding agents to store and retrieve durable project decisions, conventions, environment notes, and bug fixes in Notion, with optional Obsidian Vault dual-write.

MCP server that exposes agent-memory-daemon to any MCP-compatible client — Kiro (CLI & IDE), Claude Desktop, Cursor, and others. The daemon does the thinking (consolidation + extraction); this server is a thin filesystem bridge so agents can read, append, and search memory through the Model Context Protocol.

Enables AI assistants to search, compare, and get detailed information about MCP servers from the mcpcatalogs.com directory.

A persistent world your agents share across sessions and models. MCP memory server with semantic memory retrieval, cross-agent handoff, a hosted remote endpoint with OAuth, a free 24-hour room, and an open-source local stdio server.