Markdown Oxide: Setup for Neovim, VS Code, Zed and Helix

November 11, 2026 · 10 min read

Markdown Oxide: Set Up the PKM Language Server in Your Editor

Markdown Oxide is a free language server that adds Obsidian-style wikilinks, backlinks, tags and daily notes to the text editor you already use. You install one binary, point Neovim, VS Code, Zed or Helix at it, and open your notes folder. This guide covers install, per-editor setup and the config file.

What Is Markdown Oxide?

The server is a personal knowledge management (PKM) tool written in Rust. It speaks the Language Server Protocol (LSP), so any editor with an LSP client can use it. Its docs call it unbundled: your text editor handles the editing, and the server handles the knowledge management.

It reads a folder of Markdown notes and stays compatible with Obsidian's syntax. Here's what it adds to your editor:

  • Completions for [[wikilinks]] and standard Markdown links to files, headings and blocks
  • References (backlinks) for files, headings, blocks, tags and footnotes
  • Hover previews that show a note's text plus a snapshot of its backlinks
  • Rename for files, headings and tags, with every link updated
  • Diagnostics for unresolved links, plus code actions that create the missing file or heading
  • Tag, callout, alias and footnote completions
  • Daily note links and commands such as "today" or "next monday"

The project lives at Feel-ix-343/markdown-oxide on GitHub under the Apache-2.0 license. The latest release was v0.25.12 as of November 2026. The server doesn't render or preview Markdown. For rendering inside Neovim, see our Neovim Markdown preview and plugins guide.

How Do You Install the markdown-oxide Binary?

Every editor needs the markdown-oxide executable on your PATH, except VS Code and Zed, whose extensions can download it for you. Pick the line for your platform:

# macOS or Linux with Homebrew
brew install markdown-oxide

# Arch Linux
sudo pacman -S markdown-oxide

# Windows
winget install FelixZeller.markdown-oxide

# Any OS with Rust: fetch a prebuilt binary through cargo-binstall
cargo binstall --git 'https://github.com/feel-ix-343/markdown-oxide' markdown-oxide

# Any OS with Rust: compile from source
cargo install --locked --git https://github.com/Feel-ix-343/markdown-oxide.git markdown-oxide

Each command puts a markdown-oxide binary on your PATH. Run which markdown-oxide on macOS or Linux to confirm the shell can find it.

The README also lists apk add markdown-oxide for Alpine, zypper install markdown-oxide for openSUSE, conda install conda-forge::markdown-oxide for Conda and pkgs.markdown-oxide for Nix. Neovim users can skip all of that and run :MasonInstall markdown-oxide inside mason.nvim.

How Do You Set Up Markdown Oxide in Neovim?

On Neovim 0.11 or newer, use the built-in vim.lsp.config and vim.lsp.enable functions. If nvim-lspconfig is installed, it already ships the server's defaults, so you only add one capability on top:

-- init.lua (Neovim 0.11+ with nvim-lspconfig installed)
vim.lsp.config('markdown_oxide', {
  capabilities = vim.tbl_deep_extend('force',
    vim.lsp.protocol.make_client_capabilities(),
    { workspace = { didChangeWatchedFiles = { dynamicRegistration = true } } }
  ),
})
vim.lsp.enable('markdown_oxide')

This starts the server for every Markdown buffer you open. nvim-lspconfig's defaults set the command to markdown-oxide, the filetype to markdown and the root markers to .git, .obsidian and .moxide.toml.

Two details matter. First, stick with the call form the README recommends, vim.lsp.config('markdown_oxide', ...). It merges your table into any settings you already gave the server, while assigning with vim.lsp.config.markdown_oxide = ... replaces them. The Neovim LSP docs explain the order: lsp/*.lua files on your runtimepath come first, and your own settings override them.

Second, don't skip the dynamicRegistration = true capability. The README says the server needs it to pick up files created by the "create unresolved file" code action and to resolve block completions. The features docs add that a new block link resolves after you save with :wall, as long as this capability is on.

A few extras round out the setup:

  • Without nvim-lspconfig: also pass cmd, filetypes and root_markers yourself, using the values above.
  • Before Neovim 0.11: pass the same capabilities to require('lspconfig').markdown_oxide.setup().
  • nvim-cmp users: the README gives a custom keyword_pattern for the nvim_lsp source so completions trigger after spaces, slashes and #.
  • Daily notes: nvim-lspconfig's config adds :LspToday, :LspTomorrow and :LspYesterday commands to each Markdown buffer.

To confirm it works, open a note and run :checkhealth vim.lsp. The report lists enabled configs and each active client with its root directory. The root marker decides which folder the server treats as your vault. If your notes folder has no .git or .obsidian directory, add an empty .moxide.toml at its top level so Neovim finds the right root.

Markdown Oxide in VS Code, Zed and Helix

Outside Neovim the setup is shorter, because the other editors either ship an extension or already know about the server.

VS Code. Open the Extensions view, search for "Markdown Oxide" (extension ID FelixZeller.markdown-oxide) and install it. The README recommends letting the extension download the server binary and use that. It can also use a markdown-oxide binary from your PATH. For VS Code's own preview and other Markdown extensions, see our VS Code Markdown guide. If you also want a preview with diagrams and PDF export, add Markdown Preview Enhanced.

Zed. Install the extension of the same name from Zed's extensions page. It offers the same two modes: download the binary (recommended) or use the one on your PATH. One gap: the features docs mark file, heading and tag rename as unavailable in Zed.

Helix. Put the binary on your PATH and you're done. Helix's default languages.toml already lists marksman and markdown-oxide as Markdown language servers. Run hx --health markdown to see which of them Helix finds.

Kakoune. It works through kakoune-lsp v17 or newer, with a short kakrc hook from the README that uses .obsidian and .moxide.toml as root globs.

Configuring Markdown Oxide with .moxide.toml

You don't need a config file to start. When you want one, the server reads .moxide.toml in your vault's root folder or a global file at ~/.config/moxide/settings.toml. Here's a short vault config with the settings people change most:

# .moxide.toml in the root of your notes folder
dailynote = "%Y-%m-%d"
daily_notes_folder = "Daily"
new_file_folder_path = "Inbox"
unresolved_diagnostics = true
include_md_extension_md_link = false
title_headings = false

With this file, daily notes are named like 2026-11-11.md and live in Daily/. Files created from unresolved links go to Inbox/, and Markdown-style link completions leave off the .md extension.

The dailynote format follows the Rust Chrono library's strftime syntax, so %d %b %Y gives 11 Nov 2026. Leave the daily note and folder settings unset and the server tries to import them from your Obsidian settings. Set title_headings to true if each note's first heading is its title, and Markdown-style link completions will use that heading as display text.

One caution from the configuration reference: it tracks the main branch, so it may list settings your installed version doesn't have yet. If an option seems ignored, update the binary first.

Linking, Backlinks and Daily Notes in Practice

Once the server attaches, you move between notes the way you move between functions in code. Every action below uses your editor's normal LSP keys: go-to-definition, find references, hover, rename and code actions. Take this note in an existing vault:

# Project Atlas

Kickoff happened on [[2026-11-10]] and the targets are in [[Roadmap#Q1 Goals]].
The vendor shortlist is in the [procurement note](procurement.md).

Blocked on vendor pricing. #status/blocked ^pricing-risk

Next step: book time in [[Vendor Calls]].

Here's what the server does with each line. Typing [[ lists every file and heading in the vault, fuzzy matched. Go-to-definition on [[Roadmap#Q1 Goals]] jumps to that heading, and hovering it shows the section text plus its backlinks.

The #status/blocked tag gets completions, and asking for its references lists every note that uses the tag or its subtags. The ^pricing-risk block ID lets other notes link to that exact paragraph. If Vendor Calls.md doesn't exist, you get an unresolved-link diagnostic and a code action that creates the file.

Daily notes work the same way. Typing [[today or [[next monday completes to the matching dated note. In Neovim, :LspToday opens or creates today's file. The README also offers an optional :Daily command that accepts phrases like two days ago or directives like -3. It's a snippet you add yourself, not a built-in.

That's all the syntax you need to follow the server's behaviour. For the full wikilink, embed and callout reference, use our Obsidian Markdown cheat sheet.

Markdown Oxide vs Marksman: Which Markdown LSP Should You Use?

Both servers bring links, completions and references to Markdown, but they aim at different jobs. Marksman is a general Markdown server for docs and wikis. Oxide is built around a personal notes vault.

FeatureMarkdown OxideMarksman
Wikilink and Markdown link completionYesYes
Backlinks for headingsYesYes
Block references (^id)YesNot in its docs
Tag completion and referencesYesNot in its docs
Daily notesCompletions and commandsNot in its docs
Rename with link updatesFiles, headings, tags (not Zed)Yes
Table of contents code actionNot in its docsYes
Config file.moxide.toml.marksman.toml

We prefer Oxide for a notes vault and Marksman for a documentation repo. Oxide's daily notes, tags and block links pay off when you write every day. Marksman's table of contents action suits READMEs and docs folders.

Both servers have clear limits. Neither gives you Obsidian's graph view, canvas or plugin ecosystem. Oxide's features page also lists metadata and Dataview completions as unimplemented. If you rely on Dataview queries, keep Obsidian open alongside your editor.

Using Your Oxide Notes Outside the Text Editor

Your vault stays a folder of plain .md files, which is the main appeal. The catch is that wikilinks, tags and block IDs only resolve in tools that understand them, such as Oxide or Obsidian.

To turn a note into portable standard Markdown, paste or upload it into our Obsidian to Markdown converter. It converts wikilinks, embeds, callouts, highlights, comments, tags and front matter, one note at a time. It doesn't read a whole vault.

Then paste the result into our editor to preview it side by side and download the .md file or export it. Our editor's preview doesn't render wikilinks or footnotes, so convert wikilinks first and check footnotes in Obsidian.

Quick Answers About Markdown Oxide

Markdown Oxide turns any LSP-capable editor into a linked notes workspace. Install the binary or the VS Code or Zed extension, and enable dynamicRegistration in Neovim. Add a .moxide.toml when you want custom daily note folders. When a note needs to leave your vault as standard Markdown, convert it and check the result in the editor.