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

A Model Context Protocol server that enables AI agents to interact with a local Logseq instance, allowing operations like creating pages, managing blocks, and searching across a knowledge graph.

A Model Context Protocol server that enables AI agents to interact with local Logseq knowledge graphs, supporting operations like creating/editing pages and blocks, searching content, and managing journal entries.

An MCP server for interacting with Logseq graphs, enabling AI assistants to read, create, and manipulate Logseq content.

A server that enables LLMs to programmatically interact with Logseq knowledge graphs, allowing creation and management of pages and blocks.

Enables AI agents to read Logseq notes, journals, tasks, pages and blocks—including embedded screenshots as viewable images—directly from the on-disk graph. It works read-only with Logseq closed and no network access, snapshotting the database so nothing can be modified.

Python stdio MCP server that interfaces with the Logseq local HTTP API, enabling tools to manage pages, blocks, queries, and graph configurations in Logseq.

Connects MCP-compatible AI assistants to Logseq graphs, enabling block-first operations, block references, and context graph building.

Enables external AI assistants to interact with Logseq graphs through 34 specialized tools for managing pages, blocks, journals, and tasks via the local HTTP API.

Enables interaction with your Logseq personal knowledge management system via MCP, allowing retrieval of tagged notes and todo lists through Logseq's HTTP API.

Interacts with LogSeq via its API.

Enables AI assistants like Claude to directly read, write, search, and navigate your local Logseq knowledge graph, including managing journals, pages, backlinks, and page relationships without manual copy-pasting.

A NestJS-based server that enables AI agents to interact with Logseq graphs through its HTTP API for managing notes, journals, and blocks. It features specialized tools for project development tracking, including progress logs, technical decisions, and workflow prompts.

Connects AI assistants to Logseq knowledge graphs to read, write, and search pages, blocks, and journals via the Model Context Protocol. It features 17 tools for full graph management, including CRUD operations, batch block insertion, and full-text search.

A hybrid MCP server that bridges Claude Desktop with both Obsidian vaults and the Bonfires platform, enabling seamless knowledge management and collaboration.

AI assistant integration with Logseq knowledge graph: 21 tools to read, write, query, and search notes, enabling seamless interaction with your notes.

Enables AI assistants to interact with your local Logseq knowledge base through advanced search, content creation, template management, and knowledge organization with privacy-first, local-only operations.

Enables local MCP clients to list, read, write, and search notes in an Obsidian vault via an HTTP server running inside Obsidian.

This is a connector to allow Claude Desktop (or any MCP client) to read and search any directory containing Markdown notes (such as an Obsidian vault).

Enables local read-first access to an Obsidian vault through the Obsidian Local REST API, letting MCP clients retrieve notes, search, list tags, and inspect document structure while keeping API key and data on-device.

Provides read-only access to an Obsidian vault, enabling file listing, content reading, and text search across notes via MCP.

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

Enables MCP clients to safely read, search, create, edit, delete, and move notes in an Obsidian vault, with automatic link repair and reversible deletes.

A local MCP connector that lets Claude read, write and search any Obsidian vault directly from disk.

A standalone Node MCP server that provides semantic search, knowledge graph, and vault editing over an Obsidian vault. It runs locally as a single stdio process without requiring an Obsidian plugin for core functionality.

Enables AI coding agents to read, write, search, and organize notes in an Obsidian vault directly via the filesystem.

Enables natural language interaction with a local Obsidian vault, allowing MCP clients to read, search, create, append, and delete markdown notes securely.

Enables interaction with multiple Obsidian vaults through natural language, supporting note operations, search, and vault management with both REST and filesystem backends.

Enables MCP-compatible AI hosts to read, search, link, and write notes in a local Obsidian vault with sandboxed file access.

Provides AI agents with per-project note organization inside a single Obsidian vault, enabling them to resolve, write, read, append, list, and search notes without overwriting existing content.

This MCP server enables Claude to interact with an Obsidian vault for persistent, structured memory, providing tools for note creation, semantic search, graph traversal, and session memory.