"Information about memory banks" matching MCP servers:

Memory Bank Server provides a set of tools and resources for AI assistants to interact with Memory Banks. Memory Banks are structured repositories of information that help maintain context and track progress across multiple sessions.

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

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.

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

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.

Gives every AI agent working in a repository a shared, persistent knowledge graph stored in a plain JSONL file, with each entity, relation, and observation tagged with the date and agent that added it. Provides tools and prompts for searching, editing, renaming, merging, cleaning up, and exporting that memory, and keeps it locked to the repository that owns it.

Local, searchable project memory for AI coding agents. Markdown source of truth, MCP interface, safe structured updates

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.

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

Local-first persistent memory for coding agents and MCP clients. It keeps important project context across sessions and reduces wasted tokens by retrieving only relevant memories instead of replaying unnecessary history.

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.

Provides Claude Code with cross-session long-term memory via Letta, allowing it to read and store project context, learnings, and decisions.

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

A minimal MCP server that exposes a single tool to query local hardware information (OS, CPU, memory, architecture).

Enables AI assistants to save resolved debugging sessions as concise experience cards into a local JSON knowledge network, and to retrieve relevant past cards when new bugs arise. It also powers a spaced-repetition review interface to reinforce memory of those experiences.

Provides persistent memory for OpenCode coding agents, allowing them to store and recall architecture decisions, conventions, and gotchas across sessions via semantic search.

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.