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

Provides AI coding assistants persistent engineering memory stored as Markdown files in an Obsidian vault, enabling project context retrieval, session capture, decision recording, and memory search without requiring Obsidian to be running.

A live MCP server that connects AI assistants to a running Obsidian instance, enabling full app automation including reading notes, clicking UI elements, managing plugins, and executing JavaScript.

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.

A local MCP server that enables AI applications like Claude Desktop to securely access and work with Obsidian vaults, providing capabilities for reading notes, executing templates, and performing semantic searches.

An MCP server that enables AI assistants to interact with Obsidian vaults by providing tools for note management, full-text search, and link analysis. It supports comprehensive file operations, frontmatter manipulation, and daily note creation while ensuring security through path validation.

Enables Claude Code CLI to interact with Obsidian by reading selections, opening files, showing diffs, and running an embedded terminal.

Manages Supabase projects, databases, edge functions, secrets, and branches across organizations using the Supabase Management API with 24 tools.

Enables AI agents to manage Obsidian vaults through full CRUD operations, wikilink management, and section-level manipulation. It supports frontmatter editing, tag-based searching, and automated link updates to maintain vault integrity.

Enables AI assistants to interact with Obsidian vaults, providing tools for reading, creating, editing and managing notes and tags.

An MCP server that exposes ChromaDB vector database operations, enabling AI assistants to perform collection management and semantic document searches. It supports HTTP, persistent, and in-memory connection modes along with various embedding providers including OpenAI and HuggingFace.

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

Connects AI assistants to your n8n instance to manage workflows, executions, credentials, and user settings through 31 specialized tools. It enables users to perform n8n operations like workflow creation, activation, and execution history retrieval via natural language.

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.

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

Lets coding agents search the official Obsidian directory of 8,900+ community plugins and 870+ themes, with download counts, latest versions and last-update dates, so they can check what already exists or spot gaps before writing code. It also works for picking a plugin or theme to install, needs no API key, and only reads public data.

Enables the management of a technical terminology glossary within an Obsidian vault by providing tools to add, search, and retrieve term definitions. It supports structured Markdown entries featuring both developer-focused and simplified explanations for efficient knowledge management.