Mcp Pdf

io.github.kmalakoffPublished by GitHub account kmalakoffv1.0.3Updated Oct 24, 2026

MCP server for PDF generation using PDFKit

VerifiedSTDIODesktop onlyFiles & StorageMedia & Design

Overview

AI-generated overview

Lets an assistant generate PDF documents, layouts, and resumes locally, render PDF pages to PNG, and measure text.

What you can do
A local MCP server built on PDFKit that creates PDF files through tools. The pdf-document tool produces flowing documents with automatic pagination, pdf-layout builds precisely positioned layouts such as slides and flyers, and pdf-resume generates JSON Resume documents. pdf-image renders PDF pages to PNG, and text-measure measures text before layout. Tool calls return a file URI and metadata for the generated PDF.
When to use it
Useful when an assistant needs to produce PDF output on the user's machine, such as reports, flyers, slides, or resumes, or to convert PDF pages into PNG images. It suits local document generation where no cloud service or API key is wanted.
Requirements
Runs as a local process over stdio or HTTP and requires Node.js >=22.13; the examples use npx, included with npm. No API key or authentication is declared. Desktop only.
Before you install
It writes generated PDF and PNG files to the local machine, so review where output is saved. No credentials, payments, or third-party data sharing are indicated.

Installation

In SourceWeft

  1. Open Mcp Pdf 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

@mcp-z/mcp-pdf

Create PDF documents and layouts, render pages to PNG, and measure text through MCP. The server runs locally and requires no API key.

Requires Node.js >=22.13. The examples use npx, included with npm, to run this server and @mcp-z/cli.

Transports

MCP supports stdio and HTTP.

Both transports support the 2025 and 2026-07-28 protocol revisions. The 2026 revision is stateless, so clients using it send no initialize handshake or session ID.

Save one of these configurations as .mcp.json in the directory where you will run the commands.

Stdio

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

HTTP

json
{  "mcpServers": {    "pdf": {      "type": "http",      "url": "http://localhost:9010/mcp",      "start": {        "command": "npx",        "args": ["-y", "@mcp-z/mcp-pdf", "--port=9010"]      }    }  }}

start is an extension used by npx @mcp-z/cli up to launch HTTP servers for you. The MCP endpoint is /mcp.

First use

bash
# List toolsnpx -y @mcp-z/cli inspect --servers pdf --tools
# Create a simple PDFnpx -y @mcp-z/cli call-tool pdf pdf-document '{"content":[{"type":"text","text":"Hello from MCP"}]}'

The tool returns a file URI and metadata for the generated PDF. See the complete tool reference for parameters and examples.

Tool summary

ToolUse
pdf-documentFlowing documents with automatic pagination
pdf-layoutPrecisely positioned layouts such as slides and flyers
pdf-resumeJSON Resume documents
pdf-imageRender PDF pages to PNG
text-measureMeasure text before layout

External resources

None.

Prompts

  1. resource-fetching

Resources

  • PDFKit Documentation
  • JSON Resume Schema
  • JSON Resume Editor

Documentation

API Docs

Source: README.md at commit f2b6035

Tools

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

Version history

1
  1. v1.0.3LatestSep 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