Skip to main content
Glama
PDFMakerAPI MCP Server

PDFMakerAPI MCP Server

PDFMakerAPI MCP server

npm Glama score Add to Cursor Install in VS Code

An MCP server for PDFMakerAPI. It exposes a single create_document tool that turns a plain-English document description into a shareable link which opens in the PDFMakerAPI editor — preview it, edit any field, and download the PDF.

Works with Claude Desktop, Claude.ai, Cursor, Windsurf, Cline, Zed, VS Code, ChatGPT, and any other MCP client. It's a thin client of the public API at https://api.pdfmakerapi.com, so it needs no account or credentials of its own.

What is PDFMakerAPI?

PDFMakerAPI is a PDF template builder and PDF generation API. Instead of hard-coding documents or wrestling with HTML-to-PDF converters that break when your content changes, you design a reusable template once in a visual, no-code editor — placing text, tables, images, and dynamic fields exactly where you want them — then feed it data to produce a finished, editable PDF.

Generate a single document or thousands. Fill a template in yourself, share a link so anyone completes it in the browser as a fillable PDF form, send JSON to the REST API, trigger generation from no-code tools like Zapier, Make, and n8n, or create documents straight from AI agents like Claude and ChatGPT. Prefer to start from a prompt? Describe what you need and let Quill build it.

Teams use PDFMakerAPI for invoices, receipts, certificates, reports, and contracts — anything you'd otherwise rebuild by hand every time the data changes. Start building free with 100 PDFs a month.

Related MCP server: Nutrient Document Engine MCP Server

Quick install

One-click:

Add to Cursor Install in VS Code

Or add the same config manually (works in every desktop client):

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

Setup by client

Settings → Developer → Edit Config (claude_desktop_config.json), add the mcpServers block above, and restart Claude.

Use the Add to Cursor button, or add the block to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project).

Add the block to ~/.codeium/windsurf/mcp_config.json (or via Settings → Cascade → MCP).

Cline → MCP Servers → Configure, and add the mcpServers block.

Use the Install in VS Code button, or add to .vscode/mcp.json (note: VS Code uses a servers key):

{
  "servers": {
    "pdfmakerapi": { "command": "npx", "args": ["-y", "@pdfmakerapi/mcp"] }
  }
}

In settings.json:

{
  "context_servers": {
    "pdfmakerapi": { "command": { "path": "npx", "args": ["-y", "@pdfmakerapi/mcp"] } }
  }
}

Hosted (remote) option — no install

If your client supports remote MCP servers, just point it at the hosted endpoint — no npx, no Node:

https://api.pdfmakerapi.com/mcp
  • Claude.ai (web): Settings → Connectors → Add custom connector → paste the URL.

  • ChatGPT (Plus/Pro/Enterprise): Settings → Connectors → add the URL.

  • Cursor / others: add { "url": "https://api.pdfmakerapi.com/mcp" } instead of command/args.

Usage

Ask your assistant for a document:

"Make a professional invoice for Acme with 3 line items." "Create a course completion certificate." "Build a clean one-page resume."

It calls create_document and returns a link like https://app.pdfmakerapi.com/d/<id> — open it to preview, edit any field, and download the PDF.

Configuration

Env var

Default

Purpose

PDFMAKERAPI_BASE_URL

https://api.pdfmakerapi.com

Point at a different API (e.g. http://localhost:3001 for local dev).

Develop

git clone https://github.com/GerardoBarrera/pdfmakerapi-mcp.git
cd pdfmakerapi-mcp
npm install
npm run build   # compile to dist/
npm run dev     # run from source (tsx)

Troubleshooting

  • Server doesn't appear in your client — restart the client after editing its MCP config, and check the JSON is valid (no trailing commas). For remote clients, confirm the URL is exactly https://api.pdfmakerapi.com/mcp.

  • npx fails to start — ensure Node.js 18+ is installed (node -v), then retry npx -y @pdfmakerapi/mcp@latest.

  • Connection / timeout on the remote endpoint — verify your network/proxy allows HTTPS to api.pdfmakerapi.com, and that you're using the Streamable HTTP transport.

  • "Document is too large" — documents are capped at ~1 MB of JSON; trim large tables or split into multiple documents.

  • The returned link won't open — copy the full link (it ends in a document ID); if it 404s, generate the document again.

  • Still stuck? — open a GitHub issue or email support@pdfmakerapi.com.

License

MIT

Available Tools

1 tool
create_documentCreate PDF DocumentAInspect

Create a professional, shareable PDF document — invoices, receipts, certificates, reports, resumes, letters, and more. Returns a link that opens the document in the PDFMakerAPI editor, where the user can preview it, edit any field, and download the PDF.

Design a THOROUGH, realistic document (don't leave it sparse) that exactly follows this model, then pass it as document.

DOCUMENT MODEL (PDFMakerAPI) Document:

  • id: string (short slug)

  • name: string

  • description: string (one short sentence)

  • pageSize: "letter" | "a4" | "legal" | "letter-landscape" | "a4-landscape" | "square" (default "a4")

  • pageBackgroundColor: hex string (default "#ffffff")

  • margin: "none" | "sm" | "md" | "lg" — page margin; default "lg"

  • gap: "none" | "sm" | "md" | "lg" — vertical spacing between top-level sections; default "lg"

  • variables: Variable[] — every {{placeholder}} you use MUST be declared here

  • children: Node[] — the document body, top to bottom

Variable: { id, name (snake_case, used as {{name}}), label (human), type: "text"|"date"|"number"|"currency", defaultValue?: string }

Node (every node has: id, name, width: "full"|"1/2"|"1/3"|"1/4"|"2/3"|"3/4"|"auto", order: number, align?: "left"|"center"|"right", style?: NodeStyle):

  • container: { type:"container", layout:{ direction:"row"|"column", gap:"none"|"sm"|"md"|"lg", justify?:"start"|"center"|"end"|"between", alignItems?:"start"|"center"|"end"|"stretch" }, children: Node[] }

  • text: { type:"text", content: string (supports \n and {{vars}}), fontSize?:"xs"|"sm"|"base"|"lg"|"xl", fontWeight?:"normal"|"medium"|"semibold"|"bold" }

  • table: { type:"table", columns: { id, name (data key), label (header), width?: "40%", align?: "left"|"center"|"right" }[], rowVariable: string }

  • spacer: { type:"spacer", height: "sm"|"md"|"lg"|"xl" }

  • divider: { type:"divider", lineStyle?: "solid"|"dashed"|"dotted" }

NodeStyle: { backgroundColor?: hex, backgroundMode?: "none"|"solid"|"gradient", gradientTo?: hex, textColor?: hex, padding?: "none"|"sm"|"md"|"lg"|"xl", borderRadius?: "none"|"sm"|"md"|"lg", fullBleed?: boolean }

VARIABLES — how data is inserted

  • In text content, insert a value with double braces and the exact snake_case name, e.g. {{invoice_number}} — no spaces inside the braces. Every {{name}} used MUST be declared in variables[].

  • Give every variable a realistic defaultValue so the result looks complete.

  • TABLES do NOT use {{}}. A table renders one row per item in its rowVariable array, pulling item[column.name] for each cell — so each column "name" must match the row object's key. The rowVariable variable's defaultValue must be a JSON-encoded string of the row array, e.g. JSON.stringify([{ description: "Brand design", qty: "1", amount: "$2,400.00" }]).

RULES

  • Use containers (direction:"row") to place items side by side.

  • For label/value pairs (dates, totals, "Bill To", reference numbers), nest a direction:"row" container with two text children — a BOLD label (fontWeight:"bold") and the value as a {{variable}} — each with a width (e.g. label "1/3", value "2/3") so they align in columns. Stack such rows in a column container.

  • Use a table node for any repeating rows (line items, attendees) and set rowVariable.

  • Spacing between sections comes from the document "gap" (default "lg") — do NOT insert spacer nodes between top-level sections.

  • Table column alignment: left-align text columns, right-align money/number columns, center short codes/status; a header's alignment matches its column.

  • Every id must be unique. Keep it clean and professional.

After the tool returns a url, share it with the user and tell them they can open it to preview, edit any field, and download the PDF.

Inputs: document (required). Returns: url, id

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.6/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined and distinct.

    Naming Consistency5/5

    A single tool has no naming inconsistencies. The name 'create_document' is descriptive and follows a common verb_noun pattern.

    Tool Count4/5

    The single tool is appropriate for a focused server that creates PDF documents. However, it might be considered slightly thin as it combines creation and editing via a returned URL.

    Completeness3/5

    The tool covers document creation comprehensively, but lacks supporting tools for managing documents (e.g., listing, updating, deleting). This leaves agents with no way to perform other lifecycle operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables creative PDF generation with full design control including colors, shapes, emoji, and Unicode support. Supports everything from simple documents to artistic masterpieces using PDFKit's powerful API.
      5
      1,045 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and users to process documents through natural language, supporting PDF operations like text extraction, redaction, splitting, form filling, annotations, and content search.
      60 npm
      62
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server for reading, rendering, and searching PDF files, specifically optimized for LLMs to extract text, tables, and technical diagrams. It enables metadata retrieval, multi-format text extraction, and page-to-image rendering using PyMuPDF.
      5
      82
      MIT