MCP & Command Line

Your AI can ship the PDF.

Vaelora bundles an MCP server and a command-line tool that run the same conversion engine as the app — headless. Register once, and "turn these notes into a PDF" becomes something your assistant just does.

The Settings window on the Integrations tab: Claude Desktop and Claude Code registered, with the bundled command-line tool path below
Setup

Registered in one click.

Open Settings ▸ Integrations and add Vaelora to Claude Desktop or Claude Code. Prefer the terminal? vaelora mcp install claude-desktop does the same thing.

  • Quiet about permissions — registering edits one config file and nothing else. Your styles and presets live where the helper can simply read them, so starting a server never puts a dialog in front of you.
  • Status at a glance — each client shows whether it's registered and whether the registration has gone stale.
  • Nothing extra to install — the helper ships inside the app at Vaelora.app/Contents/Helpers/vaelora.
The tools

Eight tools, no token tax.

Every tool returns a file path and a summary — never PDF bytes. A conversion costs your assistant a handful of tokens, however long the document is.

export_pdf

Markdown in, finished PDF out — with any style, page setup, headers and footers, numbering, and cleanup options. Returns the output path and a page summary.

inspect_document

A dry run: how the document would paginate — pages, headings, warnings — without writing anything. Lets an assistant check before it commits.

list_styles

Every built-in style plus your own, by name — so "make it look like a technical report" resolves to the real thing.

list_presets

Your saved conversion presets, ready to apply — the same ones the inspector shows, shared with the app.

get_style

The CSS of any style, read out in full — so an assistant can see what a look actually does before it rewrites a line of it.

install_style

Add a stylesheet to your library, validated on the way in. It appears in the inspector like any other, and the CLI can use it too.

remove_style

Take one back out again. Built-ins are read-only, so there is always a known-good baseline to fall back to.

markdown_guide

The dialect, in the assistant's own terms — front matter, alerts, image attributes, header tokens. It writes Markdown Vaelora renders properly, first time.

The command line

Scriptable, the boring way.

The same helper is a plain CLI. Put it in a Makefile, a git hook, a cron job — anywhere a document should become a PDF without anyone watching.

  • Every inspector setting is a flag — page size, per-side margins, header and footer slots, numbering, Markdown options.
  • Your defaults carry over — unset options inherit your Vaelora settings, so a conversion starts where a new document in the app would.
  • Your styles come too — styles and presets are shared with the app, so the CLI knows every look you've made.
# Markdown in, PDF out
vaelora export report.md -o report.pdf \
        --style technical-report --page-size a4

# Show the settings, render nothing
vaelora export report.md --dry-run

# What's in the library
vaelora styles
vaelora presets

# Wire up an assistant
vaelora mcp install claude-desktop
vaelora mcp status
Parity, guaranteed

If the inspector can do it, so can they.

The app, the CLI, and the MCP server are all projected from one shared option table — and a test fails the build if a setting exists that the headless surfaces can't reach. Feature parity isn't a promise; it's enforced.

Get started

Two minutes to agent-ready.

Download Vaelora, open Settings ▸ Integrations, click Add. Then ask your assistant for a PDF.

Download .dmg See all features

The helper reads and writes files anywhere you can, so an assistant converts a document where it already lives.