Flavor Grenade LSP Flavored Markdown Support

Obsidian Flavored Markdown and flavor-aware Markdown language server

Flavor Grenade LSP

Keep Markdown flavors, Obsidian vault links, structured profiles, headings, embeds, tags, and safe edits clear enough for humans, editor clients, and LLM agents.

Quickstart Visual Studio Marketplace GitHub

Install

Choose the package that matches who is using the server

VS Code extension Best first install for authors working in VS Code. Install from the Visual Studio Marketplace Open the vault or configured Markdown project LSP package Use when another editor or tool owns the LSP client. npm install --save-dev flavor-grenade-lsp npx flavor-grenade-lsp LLM skill/plugin Install when Claude, Codex, or another agent needs flavor-aware Markdown evidence. npx skill install alisonaquinas/flavor-grenade-lsp --skill flavorgrenade-lsp node skills/flavorgrenade-lsp/wrappers/flavorgrenade.mjs verify-install --json

Product proof

Built for vault work that has to stay precise

How it works

How Auto Detect keeps generic Markdown generic

Flavor Grenade resolves one effective base flavor per document before applying vault behavior or structured profiles.

[core.markdown]
flavor = "commonmark"
[[core.markdown.overrides]]
path = "docs/github"
flavor = "gfm"

A root README can stay CommonMark while Obsidian notes, MDX pages, and changelogs get the behavior their evidence supports.