"Integrating Obsidian with ChromaDB for Memory Management" matching MCP servers:

A local, read-only MCP server (plus CLI) over your own stock/ETF transaction log. A deterministic core computes drawdown-first risk with bootstrap confidence intervals and validates targets with walk-forward verdicts. The assistant narrates, but the number fence makes it structurally impossible for the model to produce a figure.

Model-agnostic, agent-ready Obsidian MCP server with RBAC, SLSA provenance, and native search. 163 tools across 31 domains, multi-vault, pluggable embeddings.

A local MCP server that gives AI assistants persistent long-term memory using a biological neural architecture with cortex, synapses, and hippocampus.

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.

Hosted memory for AI agents that learns from outcomes, with shared rooms. One key across Claude, Cursor & ChatGPT.

Embedded, local-first agent memory: facts extracted into a per-namespace SQLite file (vec0 + FTS5) with hybrid retrieval and point-in-time (time-travel) queries. ADD-only history over stdio — no server process, no cloud dependency.

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.

Provides persistent local memory for any MCP-compatible AI agent, enabling agents to store, search, recall, forget, export, and manage preferences, rules, and facts with zero dependencies, no cloud, and no API keys.

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

Enables capturing Claude conversations as Obsidian notes and searching the vault from chat, using the Obsidian CLI.

MARM MCP provides persistent memory and structured session context beneath any AI tool, so your agents learn, remember, and collaborate across all your workflows.

A stateless MCP server that gives coding agents a curated entry point to shared memory, orchestrating Hindsight (facts) and LightRAG (corpora) for automatic routing, URL ingestion, and consistency tooling.

Local-first persistent memory MCP: shared SQLite key/value store, searchable, TTL-aware and secret-safe.

A portable, self-hosted semantic memory layer for LLM agents, enabling them to search and add memories by meaning over the Model Context Protocol.

Two-layer memory for AI agents. Episodes compress into identity. The only MCP memory server with an immune system. Patterns earn permanence through evidence, false knowledge gets caught and demoted, and stale information fades — so your agent's memory gets smarter over time, not just bigger. Zero dependencies. 5 tools. Works with any MCP client.

Provides AI agents with persistent, long-term memory via OKF-formatted markdown and SQLite indexing, enabling stateful storage, retrieval, and search across sessions.

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 semantic memory and persistent storage for Claude, leveraging ChromaDB and sentence transformers for enhanced search and retrieval capabilities.

HR Management AI - MCP server providing AI-powered tools and automation by MEOK AI Labs

A persistent, project-scoped memory layer for AI coding agents, providing 39 tools for capturing, searching, deduplicating, relating, and maintaining memory records across long-running coding sessions.