MarsDawn

Three ways to call marsdawn.

MarsDawn has no AI model of its own: it's built to review Markdown, not write it, so it doesn't matter which agent or model produced the file. There are three ways for an agent or a script to call marsdawn, and all three end up running the same export.

Pick whichever your tooling supports: the free marsdawn CLI, a plain-Markdown skill file, or the marsdawn-mcp MCP server. All three call the same marsdawn export and return the same JSON result.

The CLI

marsdawn export notes.md --json is callable by any agent or script that can run a shell command, model-agnostic by construction. Every field it returns is documented at marsdawn for agents, which is the source of truth for the JSON schema the other two surfaces below point back to.

The skill file

For an agent that reads plain-Markdown instructions instead of calling a shell directly — Claude Code today — the marsdawn skill is one file that teaches it to install marsdawn, run export and read the result. It's plain Markdown, so other agents that load instruction files can use the same one.

The MCP server

marsdawn-mcp is a separate, public, Apache-2.0 repository. It's an MCP server with one tool, export_markdown_to_pdf, that wraps marsdawn export --json: point an MCP client at it and the tool call returns the same JSON as the CLI.

Same export, three doors

Whichever surface calls it, the underlying behavior doesn't change: the same exporter, the same themes and paper sizes, the same diagramErrors when a Mermaid diagram fails to render. This page doesn't repeat that contract — marsdawn for agents does, in full.

Next