MarsDawn MCP server

marsdawn-mcp

An MCP server that lets an AI agent export Markdown to PDF and open Markdown files in the MarsDawn app, on macOS, by running the marsdawn command-line tool you already have. It's a channel for clients that have no shell of their own; where a shell is available, driving marsdawn directly is simpler.

The first release, 0.1.0, is an MCP Bundle, marsdawn.mcpb, attached to the release.

0.2.3, the latest release, is listed in the MCP Registry as dev.southern-light.mcp/marsdawn.

What it does

Two tools.

exportmarkdownto_pdf

Runs marsdawn export --json and returns the CLI's JSON result as structured content, so the PDF looks the way it does from the command line: rendered like MarsDawn's preview, Mermaid diagrams included.

openinmarsdawn

Runs marsdawn open [:line] --json and returns the CLI's JSON result. Needs the MarsDawn app installed, which isn't publicly available yet; call it once per file, since the window it opens follows that file's later edits by itself, without being called again.

No folder yet: the launch build's marsdawn open --folder answers with an error dialog in the app, so this tool doesn't offer it. It returns once folders ship in app 1.1 and the site publishes open.v3.json for them.

A failure from either tool comes back as an error with the CLI's message and what to do next. A missing MarsDawn app (openinmarsdawn only) comes back the same way, not as a thrown error.

Where it may read and write

Both tools work only inside folders you allow. There are two ways to name one, and the server uses both together:

add the folders you want, for example your Documents folder, and save. Each folder becomes one argument to the server. Until one is added, every call is refused with a message that says so. (A preset would not help: Claude Desktop does not expand ${DOCUMENTS}-style placeholders in a folder setting's default, and a required setting keeps the server from starting at all until it is saved.)

• The extension's settings. "Allowed folders" is a multi-value setting with no preset value:

roots on each tool call (and caches them only when the client promises to announce changes). Roots are the client's claim about your workspace, not something this server controls: the sandbox is as wide as the widest source, so a client where the agent can widen its own workspace widens its own confinement. Claude Desktop doesn't send roots; Claude Code does.

• MCP roots. If your client offers the roots capability, the server asks it for the current

From source, the folders are the positional arguments:

node /absolute/path/to/marsdawn-mcp/server/index.js /Users/me/Documents /Users/me/Projects

With neither a folder nor a root, every call is refused. So is a call the server can't check: if the client's roots/list answers with an error, a malformed result or nothing at all, that call sees no roots rather than everything.

Shortened. The full README is on GitHub.