Obsidian vs Logseq in 2026: Which One Actually Works Best with Claude?

If you've spent any time down the "second brain" rabbit hole, two names keep surfacing: Obsidian and Logseq. Both are local-first. Both use Markdown. Both are free to start. And in 2026, both now plug directly into Claude through the Model Context Protocol (MCP), turning your notes into genuine AI memory.

But underneath the similarities, these tools are philosophically different — and that difference shows up the moment you try to install them, use them daily, or wire them into an LLM.

This is the comparison I wish I'd had before picking one. No marketing fluff, no "it depends" cop-outs. Real installation steps, real limitations, and a concrete verdict on which tool plays better with Claude in 2026.

TL;DR — The 30-Second Answer

• Pick Obsidian if: you write long-form prose, want the deepest plugin ecosystem, care about clean Markdown files, and want the simplest possible Claude/MCP integration.
• Pick Logseq if: you think in bullet points, journal daily, need block-level references, want native PDF annotation, and refuse to pay for anything.
• For Claude specifically: Obsidian wins on file simplicity (pure Markdown = easier for Claude to parse), Logseq wins on block-level granularity if you structure knowledge as an outline.

Now the details.

---

What Obsidian and Logseq Actually Are

Both tools solve the same high-level problem — help you capture, link, and retrieve your own knowledge — but they make opposite bets on how thinking works.

Obsidian is document-centric. You write notes as standard Markdown files in a folder (called a "vault") on your computer. You link notes with [[wiki-style]] brackets, and Obsidian builds a graph of those connections. It was first released in 2020 and currently sits at version 1.12.7 (released March 2026).

Logseq is block-centric. Every line is a bullet (a "block"), and every block is an addressable unit you can reference anywhere else in your graph. It's built around daily journaling — the app opens to today's journal by default. It's open-source, fully free, and in 2025-2026 has been transitioning to a new database-first architecture (SQLite under the hood) while keeping Markdown export intact.

The distinction isn't cosmetic. It changes how you capture thoughts, how you organize knowledge, and — crucially for this article — how an LLM like Claude reads your vault.

---

Installation: How to Actually Get Started

Installing Obsidian

Obsidian runs on Windows, macOS, Linux, iOS, and Android. Installation is roughly a two-minute job:

1. Go to obsidian.md/download
2. Pick the installer for your OS (Windows .exe, macOS Universal, or Linux AppImage / .deb / Snap / Flatpak)
3. Run the installer and launch the app
4. On first launch, click "Create new vault" or "Open folder as vault" — a vault is just a folder where your notes live
5. Start writing. Press Ctrl/Cmd + N for a new note, use [[double brackets]] to link notes

That's it. No account required. Everything is stored locally in plain .md files inside YourVault/ with Obsidian's config tucked into a hidden .obsidian/ subfolder.

Linux tip: if you're on Ubuntu or Mint, the .deb package installs cleanly via sudo dpkg -i obsidian_*.deb or your package manager's GUI.

Installing Logseq

Logseq runs on Windows, macOS, and Linux, with mobile apps on iOS and Android (though mobile is less mature than Obsidian's).

1. Go to logseq.com/downloads
2. Grab the installer for your OS
3. Install and launch
4. On first launch, Logseq asks you to choose a folder for your graph — this is where your Markdown files (and a few Logseq-specific files) will live
5. The app opens on today's journal page. Start typing — everything becomes a bullet automatically

A subtle gotcha: Logseq wraps your content in bullet-point syntax, so if you open a Logseq .md file in VS Code or any other Markdown editor, you'll see dashes and indentation everywhere. It's valid Markdown, but it's not clean Markdown. Obsidian's files look exactly like what you'd expect.

---

Core Workflow: Documents vs. Outlines

This is where the two tools stop feeling similar.

In Obsidian, you create notes. Each note is a free-form Markdown document. You can write paragraphs, bullet lists, headings, code blocks, tables — anything Markdown supports — and mix them however you want. If you've ever used any traditional note app, it'll feel immediately familiar, just supercharged with backlinks.

In Logseq, everything is a bullet. Even if you don't think in outlines, Logseq thinks in outlines for you. Press Enter and you get a new bullet. Press Tab and it nests. Every bullet is a block with its own ID, meaning you can embed that exact block elsewhere, reference it by its unique identifier, and changes sync automatically across all references. It's basically Lego for ideas.

Where each shines:

---

Plugins, Themes, and Ecosystem

Obsidian's plugin ecosystem is the single biggest reason most people end up staying with it. There are well over 2,000 community plugins covering everything you can imagine — Kanban boards, spaced repetition, calendar views, Bible study tools, AI chat, Git sync, Excalidraw whiteboards, the list is absurd. The plugin API is mature, the documentation is excellent, and community themes let you reskin the app completely.

Obsidian also shipped an official CLI in 2026, which lets developers automate vault operations and integrate notes into scripts and terminal workflows — a big deal for the CLI-first crowd.

Logseq has a respectable plugin library (roughly 150+ community plugins), but it's noticeably smaller and less polished. Where Logseq competes is in what ships out of the box: built-in flashcards (spaced repetition), native PDF annotation, native video timestamp annotation, first-class daily journals, and a task system. You don't need to hunt for a plugin for any of those — they're baked in.

If you like tinkering and customizing, Obsidian is the playground. If you want a tool that works great out of the box without any setup, Logseq might feel like home.

---

Pricing in 2026

Obsidian:

• Core app: Free for personal use, all features included
• Commercial license: $50/user/year (and as of 2025, this became optional rather than mandatory)
• Catalyst license: $25 one-time for early access to beta builds
• Obsidian Sync: Starts at $4/month (billed yearly) for 1GB / one vault
• Obsidian Publish: $8/month (billed yearly) per published site

Logseq:

• Core app: Completely free and open-source, no paid tiers
• Logseq Sync: Roughly $5/month (still in beta at the time of writing, tied to the Open Collective supporter program). Free alternatives via Git, iCloud, Syncthing, etc.

On pure cost, Logseq wins decisively — there's no feature locked behind a paywall. For freelancers who want to publish client-facing notes or teams that need reliable commercial sync, Obsidian's paid tiers justify themselves.

---

The Claude Integration — This Is Where It Gets Interesting

Both apps now hook into Claude via the Model Context Protocol (MCP). Once connected, Claude can read, search, and even write to your knowledge base — turning your vault into persistent AI memory that survives across conversations.

But the setup experience and the quality of integration differ meaningfully.

Connecting Obsidian to Claude

There are multiple valid paths. The most popular today are:

Option 1: Local REST API + MCP-Obsidian (most flexible)

1. In Obsidian, go to Settings → Community plugins, enable them if it's your first one, and install the Local REST API plugin
2. Enable the plugin and copy the API key it generates
3. Install the mcp-obsidian server (usually via npx or uv)
4. Edit your Claude Desktop config (Settings → Developer → Edit Config):

   {
     "mcpServers": {
       "obsidian": {
         "command": "npx",
         "args": ["mcp-obsidian"],
         "env": {
           "OBSIDIAN_API_KEY": "your-key-here"
         }
       }
     }
   }

5. Restart Claude Desktop and ask: "What files are in my Obsidian vault?"

Option 2: Filesystem MCP (zero plugins)

Because Obsidian vaults are literally folders of Markdown files, you can skip Obsidian plugins entirely and point the standard Filesystem MCP server at your vault folder. Claude reads the files directly. This is the simplest setup on the planet.

Option 3: Native MCP plugin (for Claude Code)

Plugins like obsidian-claude-code-mcp run an MCP server from inside Obsidian on port 22360, auto-discoverable by Claude Code via WebSocket. Good for developers who want Claude Code to simultaneously query code and notes in the same session.

Connecting Logseq to Claude

Logseq's path goes through its built-in HTTP API:

1. Open Logseq → Settings → Features and enable HTTP APIs server
2. Click the 🔌 API button in the top bar and choose "Start server"
3. In the API panel, generate a new Authorization token
4. Install an MCP server for Logseq — mcp-logseq (Python/uv) is the most stable
5. Add it to Claude Desktop's config:

   {
     "mcpServers": {
       "mcp-logseq": {
         "command": "uv",
         "args": ["run", "--with", "mcp-logseq", "mcp-logseq"],
         "env": {
           "LOGSEQ_API_TOKEN": "your-token-here",
           "LOGSEQ_API_URL": "http://localhost:12315"
         }
       }
     }
   }

6. Restart Claude Desktop

Once connected, Logseq's MCP exposes tools for block operations, page CRUD, journal access by date, and Datalog queries — which is genuinely powerful if you've structured your graph well.

Which Integration Actually Works Better?

Here's the honest answer most comparisons avoid:

For reading/context, Obsidian wins. Claude parses plain Markdown effortlessly. Standard headings, lists, and [[links]] give it clear hierarchy with no special metadata to decode. The Filesystem MCP option means Claude can read an Obsidian vault with zero Obsidian-specific setup.

For structured querying, Logseq wins. Logseq's block references, properties, and Datalog query engine let Claude pull very specific, granular slices of your graph that would require Dataview-plugin gymnastics in Obsidian. If your notes are already structured as an outline, Logseq's MCP gives Claude sharper scalpels.

Caveat: Logseq files contain extra block metadata and ID syntax. Claude has to parse through that noise to get to the actual content. Obsidian files are just… text.

---

Pros and Cons, Real Talk

Obsidian — The Good

• Pure Markdown files, fully portable, no lock-in ever
• Massive plugin and theme ecosystem (~2,000+ plugins)
• Excellent mobile apps on iOS and Android
• Handles very large vaults (10k+ notes) smoothly
• Official CLI in 2026 opens up serious automation
• Easiest integration with Claude via plain file access

Obsidian — The Bad

• Features like daily notes, tasks, PDF annotation, and flashcards require plugins
• Can become a tweaking black hole if you're prone to over-configuring
• Commercial use costs $50/user/year if your employer requires it
• Sync is a paid add-on (or you DIY with Git/iCloud/Syncthing)

Logseq — The Good

• Completely free and open-source, no feature paywalls
• Built-in daily journaling, tasks, flashcards, PDF annotation
• Block-level references are genuinely unique and powerful
• Automatic structure — you never think about "where does this note go?"
• Datalog query engine for power users
• Arguably the best Roam Research alternative

Logseq — The Bad

• Everything is a bullet whether you want it or not — prose writing feels awkward
• Files aren't clean Markdown; opening them outside Logseq is ugly
• Plugin ecosystem is smaller and less mature
• Mobile apps lag behind Obsidian's
• Has been "in beta" for a long time; bugs and sync friction still surface
• Large graphs can feel sluggish (the DB-mode rewrite should fix this, but is still stabilizing)

---

Which One Should You Actually Pick?

Skip the coin toss. Here's the clean decision tree:

• You're a developer who lives in the terminal and wants to pair notes with Claude Code → Obsidian. The CLI, the plain Markdown format, and the mature MCP options make this a no-brainer.
• You're a student, researcher, or daily journaler who annotates PDFs → Logseq. Free, batteries-included, and the journal-first workflow is genuinely superior for building a habit.
• You write long-form (blog posts, essays, documentation) → Obsidian. Logseq's outliner will fight you every paragraph.
• You think in outlines and hierarchies → Logseq. Block references are the killer feature, and Obsidian has nothing close.
• You want the path of least resistance to Claude as AI memory → Obsidian + Filesystem MCP. It's a three-minute setup and Claude reads your notes perfectly.
• You want the richest possible AI queries against structured knowledge → Logseq + mcp-logseq. Datalog + block-level access is objectively more powerful once you've invested in the structure.

And the honest answer nobody in marketing will tell you: try both. They're free, they both use Markdown, and a week with each using your real notes will tell you what no comparison article can. The tool that feels like an extension of your brain rather than a speed bump is the right one.

---

Final Verdict

If you put a gun to my head and made me pick one in 2026, I'd pick Obsidian for the broadest set of users — it's more versatile, plays better with Claude out of the box, handles every note-taking style, and has the ecosystem to grow with you.

But I'd pick Logseq in a heartbeat if I were a researcher building a structured knowledge graph, a student drowning in PDFs, or someone who lives inside a daily journal.

Both are excellent. Both are actively developed. Both respect your data (local-first, plain text, exportable). And in 2026, both can turn into real AI memory for Claude with a short MCP setup.

The only truly wrong choice is not picking one at all.

---

Want more developer-focused deep dives on the tools actually worth your time? Bookmark GitSurfer — we track the repos, workflows, and integrations that matter.