"A server with memory capabilities for MCP" matching MCP servers:

Turns a codebase into a persistent knowledge graph so AI coding agents can answer structural questions about functions, call chains, routes, and cross-service links through graph queries instead of reading files one by one.

Middleware that converts a serverless handler with OpenAPI spec into an MCP endpoint following stateless MCP principles.

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

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.

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

Long-term memory for AI coding agents, stored as a tree of plain local files. Agents search it before answering and save what lasts; changed facts are kept as history and flagged as outdated.

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.

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

A different approach from typical persistent-memory MCPs. Instead of a local SQLite + embeddings store, the memory lives as plain files in a .ai-memory/ directory you commit to your repo (facts.jsonl, decisions/\*.md, gotchas.md). Git is the sync layer — what one Claude/Cursor/Cline learns about a repo, the next session (or a teammate's agent) picks up automatically. 5 MCP tools: get_rep

Failure Memory provides AI coding agents with a shared local memory of failures, enabling them to record, recall, and learn from mistakes across sessions.

Persistent memory and automatic git snapshots for Claude Code, capturing decisions, patterns, and architecture across sessions.

Enables coding agents to add a bounded semantic-judgment layer for routing, ranking, extraction, verification, and escalation, returning typed signals and review recommendations.

Persistent project memory for coding agents, kept in a local SQLite store with FTS5 search: search and list memories by topic, read one with its history, add a fact, show the store's statistics, and read or regenerate the PROGRESS.md handoff. Pure standard-library Python; no network.

Provides persistent local memory for AI coding sessions, enabling agents to save and retrieve project context across different tools and sessions.

A fully local persistent memory layer for LLM coding agents (Claude Code, Codex, Gemini CLI, OpenCode). A shell wrapper intercepts tool invocations, fires hooks on every tool call, then runs a 3-layer pipeline (extract → compress to ≤500-token digest → merge into project memory doc) at session end. The next session gets prior context injected automatically.

Enables programming agents to capture errors and conversation signals, reflect on root causes, consolidate reusable skills, and retrieve relevant context for future tasks, providing a self-learning memory loop.

Provides project memory management for Claude Desktop, storing memories as Markdown files with intelligent keyword-based retrieval and automatic creation/update decisions by LLM.

Basic Memory is a knowledge management system that allows you to build a persistent semantic graph from conversations with AI assistants. All knowledge is stored in standard Markdown files on your computer, giving you full control and ownership of your data. Integrates directly with Obsidan.md

Persists AI's cognitive fragments as a knowledge graph within each project directory, enabling project-level memory isolation and sharing via Git.

MCP server that launches Mesen/MesenCE headlessly and exposes the emulator's debugger-face Lua API over MCP JSON-RPC, enabling AI agents to load ROMs, step frames, inspect memory/registers, manage breakpoints/watches, trace execution, and export Code/Data Logger maps for SNES, NES, PC Engine, and Game Boy Advance.