"A tool for managing and working with file systems" matching MCP servers:

Provides local persistent working memory for AI agents, allowing them to load rules, preferences, and project state before tasks and save validated experiences after successful completion. Works with stdio MCP clients via a local JSON file.

Prevents context bloat and the 'Lost in the Middle' phenomenon by distilling action histories into concise summaries while maintaining a clear core objective.

Enables AI harnesses to maintain a persistent memory layer backed by a local SQLite file, providing MCP tools to add, search, deprecate, and synchronize facts without deleting history.

A read-only MCP server that provides document awareness for agents by parsing local files into structured profiles, blocks, chunks, and search results, enabling agents to understand and cite document content without dealing with raw file formats.

Enables a connected frontier-model assistant to develop research grant proposals with traceable evidence, claim review, and versioned drafts. It preserves source passages, judgments, proposal versions, and editable exports in a local research workspace.

A-MEM is a self-evolving memory system for coding agents that automatically organizes knowledge into a Zettelkasten-style graph with dynamic relationships, enabling semantic and structural search.

Provides a 'reflect' tool that creates cognitive checkpoints for AI assistants, forcing structured step-by-step reasoning through complex problems to improve accuracy and maintain context during task execution.

Enables AI consciousness continuity and self-knowledge preservation across sessions using the Cognitive Hoffman Compression Framework (CHOFF) notation. Provides tools to save checkpoints, retrieve relevant memories with intelligent search, and access semantic anchors for decisions, breakthroughs, and questions.

A modular, extensible MCP multi-server hub that gives LLMs sandboxed file access, Git operations, web fetching, and persistent memory, deployable via Ansible.

Central registry for AI tools with vector search and knowledge graph, enabling intelligent tool discovery, chaining, and execution via MCP.

Implements Anthropic's 'think' tool for Claude, providing a dedicated space for structured reasoning during complex problem-solving tasks that improves performance in reasoning chains and policy adherence.

Provides an MCP interface to the ROBOT command-line tool for OWL ontology editing, enabling operations like merging, reasoning, and conversion via natural language.

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.

An MCP server that allows Claude and other LLMs to manage persistent memories across conversations through text file storage, enabling commands to add, search, delete and list memory entries.

MCP server that enables persistent, hybrid, local memory for LLM agents, with vector + BM25 search, knowledge graph, and policy-driven retention, providing token-budgeted context injection for AI assistants.

Persists Claude Code sessions to Notion as team memory, enabling queryable recall of decisions, work state, and project architecture.

Provides an intelligent, graph-based memory system for LLM agents using the Zettelkasten principle, enabling automatic note construction, semantic linking, memory evolution, and autonomous graph maintenance with background optimization processes.

MCP server for Obsidian vaults, optimised for Cursor agents — safe note editing, lean tool surface, direct filesystem access.

Memory bank with Server as SSH support for central knowledge base

Enables Codex projects to read Git-backed kickoff, acceptance, handoff, progress, and next-step context, and to append validated, audited progress events through scoped MCP tools. This supports visible agent progress, resumable sessions, and safer handoffs.

Production-ready MCP server providing RAG, hierarchical memory, and 8+ tools for AI agents via the Model Context Protocol.

Enables AI agents to retrieve Git-backed project context, handoff packages, progress, and next steps, and to append validated progress events with matching project-record commits. This supports visible agent progress, resumable work, and safe handoffs while keeping high-risk actions outside the MCP surface.

Enables agents to read Git-backed project context and append audited, idempotent progress events through scoped, short-lived credentials, supporting resumable handoffs and visible project state.

Enables AI agents to read Git-backed project context and append validated, audited, idempotent progress events through short-lived, scoped credentials, supporting resumable work and safer handoffs.

A robust MCP server that transforms OneNote notebooks into an AI-accessible knowledge base for Gemini Spark, enabling natural language queries to list, read, and search notes via Microsoft Graph API.

Enables Codex agents to read a project's kickoff card, acceptance criteria, progress, Git trail, and handoff package, then append one validated, idempotent progress event with an agent verification note and matching Git commit. Access is limited to short-lived, scoped, revocable credentials bound to a single workspace and project, with high-risk actions kept outside the tool surface.

Enables MCP clients to read a project’s kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, and to append validated, audited, idempotent progress events as Git-backed project records.

Enables Codex and MCP clients to read a project's kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, and to append validated, audited, idempotent progress events tied to project-record Git commits.

Enables agents to retrieve project context and append validated, audited progress events through scoped MCP tools, keeping project records Git-backed and handoffs resumable.

Enables AI agents to retrieve Git-backed project context—kickoff cards, acceptance criteria, handoffs, progress, and next actions—and to append validated, audited progress events under scoped credentials.