Pdf It

io.github.mrslbtPublished by GitHub account mrslbtv2.1.0Updated Oct 27, 2026

Native PDF renderer for AI markdown. Cover, TOC, page-numbered footer. Fonts embedded, zero config.

VerifiedSTDIODesktop onlyFiles & StorageMedia & Design

Overview

AI-generated overview

Local MCP server that converts markdown into styled PDFs with a cover page, table of contents and page-numbered footer.

What you can do
  • Convert markdown into a PDF, with optional title, author and output path
  • List the available templates (research-report or plain)
  • Produce a cover page, auto-generated table of contents from H1/H2 headings and a footer with title and page number
  • Render code blocks, tables, lists and charts with embedded fonts, writing the file to a chosen location
When to use it
Useful when a session produces a long markdown report, summary or design doc that should become a presentable PDF to send to a client or colleague, without manual HTML or Pandoc work.
Requirements
Runs locally over stdio as the npm package pdf-it-mcp, installed globally or via npx. Needs Node.js 20 or newer; the renderer and fonts ship inside the package, so no other install or configuration is required. No accounts, API keys or environment variables are declared.
Before you install
It writes PDF files to disk: by default under ~/Documents/pdf-it/, or to any absolute path passed as output_path, so the assistant can create or overwrite files wherever it is pointed. Content comes from the model's markdown, so review generated documents before sending them out. The README describes it as an unofficial community tool with no liability for rendering failures.

Installation

In SourceWeft

  1. Open Pdf It in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

pdf-it

[pdf-it MCP server] [MCP Badge] [npm version] [npm downloads] [License: MIT]

A Model Context Protocol (MCP) server and Claude Code skill that turns markdown into PDFs that look like they were made on purpose. Cover page, table of contents, code blocks that hold across page breaks, page-numbered footer. One command from your Claude session to a file you can send to a client.

Fonts ship inside the package, so every PDF looks the same on every machine. Nothing to install, nothing to configure.

[pdf-it cover example]

Why this exists

Every Claude Code research session ends the same way: a wall of useful markdown and no clean way to turn it into a PDF a person would actually want to read.

Chrome print: takes 30 seconds, output looks like a Word doc. Manual HTML conversion: 10 minutes per document. Pandoc: works but defaults look like a 2008 academic paper. None of it produces an artifact you would send to a client.

pdf-it is one command. The output is designed by default.

[pdf-it body example]

Install

bash
npm install -g pdf-it-mcp

Or run on demand with npx pdf-it-mcp.

Requirements

  • Node.js 20 or newer
  • Nothing else to install. The renderer and fonts ship inside the package.

Configure

Claude Desktop

Edit claude_desktop_config.json:

json
{  "mcpServers": {    "pdf-it": {      "command": "npx",      "args": ["-y", "pdf-it-mcp"]    }  }}

Claude Code

bash
claude mcp add pdf-it -- npx -y pdf-it-mcp

Cursor

Add to ~/.cursor/mcp.json with the same shape as Claude Desktop.

Cline / Continue / Zed / Goose

Standard MCP config. Same npx -y pdf-it-mcp command.

Use

In any Claude session connected to the server, ask:

Save this as a PDF

Or any of these phrasings: export as PDF, make a PDF report from this, turn this into a PDF, /pdf. The skill picks up the request and routes it through pdf-it. The output lands in ~/Documents/pdf-it/ by default.

Tools

ToolDescription
generate_pdfConvert markdown into a PDF. Accepts a template (research-report or plain), optional title and author for the cover, and an optional output path.
list_templatesReturn the list of available templates with descriptions.

generate_pdf parameters

ParameterRequiredDescription
contentyesMarkdown string to convert
titlenoShown on the cover and in the page footer
authornoShown on the cover above the date
output_pathnoAbsolute path for the output. Defaults to ~/Documents/pdf-it/{slug}-{timestamp}.pdf
templatenoresearch-report (default) or plain

Templates

NameDescription
research-reportCover page with title, author, and date. Auto-generated table of contents from H1 and H2 headings. Body with proper hierarchy. Footer with title and page number. Best for research, summaries, design docs, reports.
plainNo cover, no TOC. Dense body content only. Best for short notes and quick exports.

Skill

This package ships with a Claude Code skill at SKILL.md. Trigger phrases the skill responds to:

  • save this as PDF
  • export as PDF
  • make a PDF report from this
  • turn this into a PDF
  • generate a PDF
  • /pdf

See SKILL.md for the full skill spec.

Output

By default PDFs are written to ~/Documents/pdf-it/{slug}-{timestamp}.pdf. Pass output_path to override.

Design

Three families ship inside the package:

  • Newsreader for the cover title (display 60, light) and body H1 (display 32). High-contrast serif that holds editorial weight at large sizes.
  • DM Sans for H2, H3, table type, and the TOC heading. Quieter sub-hierarchy.
  • JetBrains Mono for page numbers, metadata, code, and figure captions.

Pure white paper, near-black ink (#111113), secondary ink for date and table cells (#2B2B2E), muted gray for page numbers and date (#7A7A7E), hairline borders (#E6E6E6). No accent colors. Code blocks render without syntax highlighting on purpose: color choices in PDFs age badly.

Every value lives in src/templates/design-tokens.ts as the single source of truth. If you want a different design language, fork the components. They live in src/templates/components/ and are plain React-PDF components with a small surface area.

How it works

  1. Parse: remark converts your markdown into an AST.
  2. Compose: the AST becomes typed React components (Cover, TOC, and body primitives like H1/H2/H3, Paragraph, CodeBlock, Blockquote, Table, lists, and charts).
  3. Render: @react-pdf/renderer rasterizes the React tree into a deterministic PDF with embedded fonts and TOC anchors.
  4. Output: the PDF lands in ~/Documents/pdf-it/{slug}-{timestamp}.pdf with title/author metadata embedded.

Total time: typically sub-second for a 5-page document, 1-2 seconds for a 30-page document.

Recognition

Listed on npm, Glama, and LobeHub.

Disclaimer

This is an unofficial, community-built tool. It is not affiliated with, endorsed by, or sponsored by Anthropic PBC. Claude and Claude Code are trademarks of Anthropic PBC.

pdf-it runs locally and ships its own renderer (@react-pdf/renderer) and fonts. Use at your own risk. The author accepts no liability for issues arising from misuse, prompt injection, bugs, or rendering failures.

License

MIT. See LICENSE.

Source: README.md at commit 1d9eb43

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts