Two Logseq variants matter
Logseq's DB version adds database graphs and an official local MCP server. The original file-based graphs have moved to Logseq OG. Choose which version you intend to use when comparing storage and integrations.
The project currently labels the DB version beta and its new real-time collaboration alpha. Check the current release status of the build and collaboration service you plan to use.
Official MCP exists in Logseq DB
The DB documentation describes a token-authenticated local HTTP server that runs through the desktop app or CLI. Tools support searching and creating or editing graph content, with documented limits. Community integrations remain another route, not the only one.
Hjarni hosts its official MCP server. Compatible remote assistants can connect without you running a local process. The difference is the connection and document model, rather than whether Logseq supports AI.
Outlines and documents
Logseq's blocks, properties, journals, and queries suit people who want a graph outliner. Hjarni uses Markdown documents in folders, with tags, shared team roles, and folder instructions. Either can provide useful source material to a connected assistant.
A folder instruction can ask an assistant to cite the source notes for a synthesis. The host still decides whether to retrieve the material, so instructions are guidance rather than automatic recall.
Exports are not interchangeable
Logseq DB offers SQLite, EDN, and Markdown exports. Its docs explicitly warn that standard Markdown does not preserve all graph data. Hjarni's Markdown ZIP importer imports Markdown documents rather than recreating a Logseq database. Check properties, block references, nesting, and attachments in a sample before moving a graph.