mcpField
P

PaperType

Local
papertype.devProductivity
Visit website

About PaperType

Render Markdown, HTML or invoice/certificate/report templates to PDF files via the PaperType API

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "dev-papertype-papertype": {
      "command": "npx",
      "args": [
        "-y",
        "papertype-mcp"
      ],
      "env": {
        "PAPERTYPE_API_KEY": "<PAPERTYPE_API_KEY>",
        "PAPERTYPE_OUTPUT_DIR": "<PAPERTYPE_OUTPUT_DIR>",
        "PAPERTYPE_BASE_URL": "<PAPERTYPE_BASE_URL>"
      }
    }
  }
}
Run commandnpx -y papertype-mcp
Environment variables to set
PAPERTYPE_API_KEYSecretPaperType API key (dp_...). Get one at https://papertype.dev/signup.
PAPERTYPE_OUTPUT_DIRDirectory where rendered PDFs are saved. Default: the OS temp dir + /papertype.
PAPERTYPE_BASE_URLAPI origin. Default https://papertype.dev; change only for test deployments.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmpapertype-mcp0.1.0

Tools

3

Saved tool list · updated 1w ago

ParameterTypeRequiredDescription
cssstringNoExtra CSS appended after the theme (markdown/html). May include @page rules, e.g. '@page { margin: 2cm }'.
tocbooleanNoAdd a table of contents built from headings. Markdown input only. Default false.
dataobjectNoJSON object of fields for the chosen template (required when template is set). Shape per template is shown by list_templates.
datestringNoDate text shown on the cover page, e.g. '2026-10-18' or 'October 2026'.
htmlstringNoHTML document or fragment to render. A theme wraps it in page styles unless theme is 'none'. Provide exactly one of markdown, html, or template+data.
coverbooleanNoAdd a cover page with title, author and date (markdown/html). Default false.
themeenumNoPage style for markdown/html input. 'clean' (default, general documents), 'report' (formal, good with cover+toc), 'minimal' (plain), 'letter' (correspondence), 'none' (HTML only: no theme, just your own CSS). Ignored for templates.clean | report | minimal | letter | none
titlestringNoDocument title: used for the PDF metadata, the cover page, and the default output filename.
authorstringNoAuthor shown on the cover page and in PDF metadata.
footerstringNoFooter text printed bottom-left on every page (e.g. a confidentiality note).
headerstringNoRunning header text printed top-right on every page.
filenamestringNoSuggested file name (e.g. 'invoice-014.pdf'). Used for the saved file's name when output_path is not given.
markdownstringNoMarkdown source for the document (GitHub-flavoured: headings, lists, tables, fenced code, footnotes, admonitions). Provide exactly one of markdown, html, or template+data.
templateenumNoName of a hosted template to fill with `data` instead of writing markdown/html: 'invoice', 'certificate' or 'report'. Call list_templates to see each template's fields and sample data.invoice | certificate | report
page_sizeenumNoPaper size. Default A4. Use 'Letter' for US documents.A4 | Letter | Legal | A5
output_pathstringNoWhere to save the PDF. Omit to get a unique file named after the title under the server's output directory (PAPERTYPE_OUTPUT_DIR, default <tmp>/papertype). An existing directory (or a path ending in '/') saves a uniquely named file inside it. Any other path is used as the exact file name ('.pdf' appended if missing; an existing file is overwritten). Relative paths resolve against the output directory.
page_numbersbooleanNoPrint page numbers in the footer. Default true.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.