"A comparison or overview of Obsidian and Logseq" matching MCP servers:

A Model Context Protocol server that enables semantic vector search over Obsidian notes, allowing AI assistants to intelligently search and retrieve relevant note content.

Enables local MCP clients to search Obsidian Markdown vaults using semantic, keyword, and hybrid search, with local Ollama embeddings and storage in either Qdrant or PostgreSQL + pgvector.

Provides a self-hosted memory system that lets AI agents read and write durable notes as plain Markdown in an Obsidian vault, with keyword and semantic search plus wikilink graph operations.

Enables semantic search across Obsidian vaults using vector embeddings and ChromaDB. Supports multiple vaults with real-time indexing and provides both MCP server and CLI interfaces for natural language querying of notes.

Provides semantic search over Obsidian markdown notes using BAAI/bge-m3 embeddings and ChromaDB, accessible via the Model Context Protocol.

Enables semantic search and content retrieval from local Obsidian vaults through the Model Context Protocol. It allows AI assistants to query notes by meaning, filter by tags, and access full note content for enhanced knowledge integration.

A local-first Graph-RAG system combining ChromaDB with metadata-based graph relationships and Gemini 2.5 Flash for intelligent Q&A over Obsidian vaults, supporting MCP clients like Claude Desktop, Cursor, and Raycast.

Enables users to ingest PDF/DOCX/TXT/MD documents and ask natural language questions about them, using local embeddings and Groq-powered retrieval-augmented generation.

An MCP server that enables searching and retrieving ACL NLP conference papers from a Qdrant vector database using semantic search and structured filters like year, venue, and field of study.

Enables semantic search and analysis of customer support tickets. Provides tools to search tickets, analyze the dataset, and retrieve individual tickets using natural language.

askDB is an MCP server that retrieves relevant database schema (DDL) from a Pinecone index and provides it to LLMs to write SQL, without connecting to the database itself.

Provides persistent memory for AI agents using hybrid search (vector embeddings + BM25) with neural reranking, enabling storage and retrieval of insights, debugging solutions, and patterns across coding sessions.

Enables natural-language search over locally indexed files such as markdown, text, images, videos, and PDFs, and retrieves indexed text or media metadata by path. It lets Cursor query a local embedding index built with Gemini and SQLite.

Local-first, source-traceable memory for AI agents — no LLM at ingest, $0 per message, zero data egress. Gives Claude Code, Cursor, and any MCP client one shared persistent memory with semantic recall, belief revision, selective forgetting, and a provenance guard that blocks acting on stale or unconfirmed memories.

Enables agents to run hybrid dense and BM25 search over a local folder of Markdown files, read and write notes, and trigger reindexing as the folder changes. It also injects the most relevant sections into each prompt automatically and runs entirely locally with a bundled embedding model.

Agent memory for facts that change. When a user corrects something, Recall replaces the old fact, tells the agent what it replaced, and keeps the old value in a history. Ask what was believed on any date, see every change to a fact, or diff two dates. Runs locally on polign_db, Postgres with pgvector, MongoDB, or Qdrant. Apache 2.0.

Enables natural-language semantic search of a project's code through a local vector index, so questions that plain grep cannot match return ranked file:line references. It also indexes or refreshes projects on demand, reports index status, and optionally flags near-identical code across files.

A personal memory MCP server that ingests AI agent conversation logs from multiple platforms into a searchable PostgreSQL+pgvector database, enabling cross-session recall of past reasoning and decisions.

Provides AI agents with persistent, searchable memory using semantic search, auto-linking, and categorization, with zero-config local setup or production-ready external providers.

Enables agents to run semantic search across one or more local project directories by automatically maintaining a LAN-local Qdrant index with Ollama embeddings. Indexing, staleness checks, and incremental updates happen transparently, so users can query code by meaning without managing collections, chunks, or hashes.