"Context Memory Systems and Techniques" matching MCP servers:

An MCP server that allows users to run and visualize systems models using the lethain:systems library, including capabilities to run model specifications and load systems documentation into the context window.

Provides systems thinking models as composable analysis lenses for architecture, infrastructure, DevOps, incident analysis, and technical decision-making.

Tracks mistakes and solutions from past Claude sessions to avoid repeating failed approaches.

Enables LLM assistants to store, retrieve, and update user-specific context memory including travel preferences and general information through a chat interface. Provides analytics on tool usage patterns and token costs for continuous improvement.

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.

Provides component information, usage guidelines, and code generation for AWS Cloudscape Design System in React, with search and pattern library capabilities.

Local-first documentation for AI agents

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

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

An MCP server that preserves LLM context by intercepting large data outputs and returning only concise summaries or relevant sections. It enables efficient sandboxed code execution, file processing, and documentation indexing across multiple programming languages and authenticated CLIs.

Relays a result screenshot to Slack so you can review a coding agent's output without opening the app.

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

Deterministic dependency + CVE context for AI coding tools, over the Model Context Protocol. A ~0.85 MB pure-Rust MCP server.

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.

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

Provides AI assistants with real-time visibility into your codebase's internal libraries, team patterns, naming conventions, and usage frequencies to generate code that matches your team's actual practices.

MCP server providing deep PostgreSQL context to AI assistants, including schema DDL, index health, foreign key associations, query execution plans, and performance statistics via read-only tools.

Aggregator MCP proxy that collapses N downstream MCP servers into 4 meta-tools with progressive tool discovery, and compresses large tool outputs (HTML→Markdown, JSON summarization) with full-output retrieval via read_more and a per-session token-savings report.

Durable project-memory MCP: decisions, constraints, and pipelines across Claude sessions

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