The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Mac Letterhead listing page.
Turn any Markdown file into a professionally-branded PDF on your company's letterhead — with no manual formatting. Mac-letterhead treats your letterhead PDF as digital stationery: it prints your Markdown into the safe area of the page (never overlapping your header, footer, or logo) and applies your brand's typography from a small CSS file.
Runs entirely on your Mac. Same engine as a drag-and-drop droplet, a command-line tool, or a Model Context Protocol server that Claude and other AI clients can call directly.
You have a company letterhead — a PDF with your logo at the top, contact info at the bottom, maybe a subtle watermark. You have documents to write, and they need to be on that letterhead: proposals, reports, invoices, memos.
The traditional options are all painful: Word templates that never quite line up, copy-paste-adjust cycles into a designer's InDesign file, or manually placing text over the letterhead in a PDF editor. Or just giving up and sending unbranded.
Mac-letterhead does the whole thing automatically. It analyzes your letterhead PDF to find the safe printable area (the space around the header, footer, and logo), renders your Markdown into that area with your brand's typography (fonts and colors from a tiny CSS file), and hands you a finished PDF. Multi-page letterhead? First-page vs subsequent pages? Handled.
The same tool ships as three interfaces — a Mac drag-and-drop app (for you), a command-line utility (for scripting), and an MCP server (so Claude and other AI clients can produce your branded documents on request).
Pick one:
Homebrew (recommended for everyday Mac use):
uvx (no permanent install; uses uv's ephemeral env):
Claude Desktop (double-click install):
Download the latest mac-letterhead-<version>.mcpb from the releases page and double-click it — Claude for macOS handles the rest.
For the best rendering quality (full CSS support via WeasyPrint), install the WeasyPrint system libraries once:
Without them, Mac-letterhead falls back to ReportLab automatically — simpler output, no external deps, everything still works.
Put your letterhead somewhere Mac-letterhead can find it. The default convention is ~/.letterhead/<name>.pdf:
(Optional, but strongly recommended) Add typography. Create ~/.letterhead/company.css with your brand's fonts and colors:
Skip this and Mac-letterhead uses a clean default.
Create the droplet on your Desktop:
A company.app appears on your Desktop.
Drop any .md or .pdf file onto the droplet. Choose where to save. You get a letterheaded PDF.
That's it. Every subsequent document is one drop.
Same engine, three interfaces.
Best for human workflows on a Mac. One-time setup, then every future document is a drag onto a Desktop icon.
Each droplet is a full macOS .app bundle you can drag around, put in the Dock, or Automator-chain. Dropping a file on it opens a save dialog for the output location.
Double-click the droplet (without dropping anything) to see the safe-area preview for that droplet's letterhead — cut marks, colour-coded tint, source label, all in one PDF that opens in your default viewer. Handy for verifying "will Markdown land where I expect it" before committing to a merge.
Best for scripting, CI, or one-shot conversions. No droplet needed.
Full reference: mac-letterhead --help.
Best when you want Claude, Claude Code, Cursor, Windsurf, or another AI assistant to produce branded documents on demand.
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):
Then in Claude: "Draft a Q3 investor update on our company letterhead." Mac-letterhead handles the formatting; the PDF lands in ~/Desktop.
Published on the official MCP Registry as io.github.easytocloud/mac-letterhead — visible on Glama and PulseMCP. For full MCP configuration (style-specific servers, multiple brands from one client), see README_MCP.md.
Mac-letterhead needs to know where on your letterhead is safe to print content — the space between the header, footer, and any logos. It figures this out in three tiers:
safe-area (or printable-area — case-insensitive, substring match). Then multiple rectangles per page work too — only the labeled one is used.Preview the resolution any time:
Colour code in the preview PDF — glance to see how confident the tool is:
| Colour | Source | What it means |
|---|---|---|
| Green | annotation | You marked it. Trusted verbatim. |
| Slate blue | auto-detected | Heuristic derived it from the letterhead layout. |
| Amber | fallback default | No content detected. Consider marking it. |
Cut marks at each corner give print-native precision; a very subtle tint fills the region for gestalt. A tiny label at the bottom-left tells you which source drove the result and the safe area's exact dimensions.
Any Markdown file can start with a YAML front-matter block declaring per-document overrides — the same convention Jekyll, Hugo, and Obsidian use. Mac-letterhead reads it, applies the options, and renders the body normally.
Supported fields (all optional, kebab-case, unknown fields are logged and skipped):
| Field | Values | Effect |
|---|---|---|
title | string | PDF title metadata + auto-generated filename |
output-dir | path (supports ~) | Where the resulting PDF is written |
page-numbers | bottom-right | bottom-center | bottom-left | alternate | See below. Omit to disable page numbers entirely (the default). |
blend-strategy | darken | multiply | overlay | transparency | reverse | Overrides the merge blend mode |
style | style name | Overrides the letterhead style (ignored on dedicated MCP servers — see README_MCP.md) |
author, subject | string | PDF metadata |
page-numbers: alternate is designed for booklet-style multi-page letterheads: page 1 is treated as a title page (no number), subsequent left-hand pages get the number bottom-left, right-hand pages bottom-right. Requires the WeasyPrint backend.
Precedence (most-specific wins):
So if an MCP tool call passes output_path=… explicitly and the document says output-dir: …, the MCP arg wins. Front matter fills in what the caller left unspecified.
The letterhead PDF supplies the visual identity (logo, header, footer). CSS supplies the typography: fonts, colors, spacing, table styling, heading treatment. Together they make one reusable brand identity that any Markdown document can be rendered through.
Full example — ~/.letterhead/company.css:
CSS is applied inside the safe area, so branded typography stays clear of your header, footer, and logo automatically. (CSS is applied by the WeasyPrint backend; the ReportLab fallback supports a reduced subset.)
Different letterheads need different overlay modes. Set with --strategy in the CLI, or when creating a droplet.
| Strategy | Best for |
|---|---|
darken (default) | Dark logo/artwork on light letterhead paper |
multiply | Watermark-like effects on subtle designs |
overlay | Better visibility across mixed contrasts |
transparency | Smooth blending with translucent layers |
reverse | Letterhead on top, content beneath |
Different letterhead template per page position:
| Letterhead PDF has… | Applied to |
|---|---|
| 1 page | Every document page |
| 2 pages | Page 1 → first document page; page 2 → all others |
| 3 pages | Page 1 → first; page 2 → even; page 3 → odd |
brew install pango cairo fontconfig freetype harfbuzz to opt into WeasyPrint.pycmarkgfm is available (it's a default dependency).mac-letterhead install --name X --letterhead /some/other.pdf --css /some/other.css for one-off droplets with non-conventional paths.docs/publishing.md.CLAUDE.md documents the architecture, release rules, and MCP registry constraints.Mac-letterhead runs entirely on your local machine. No network calls, no telemetry, no analytics, no cloud sync. See PRIVACY.md.
See CONTRIBUTING.md.
MIT.