PaperType

dev.papertypePublished by papertype.devv0.1.0Updated Oct 26, 2026

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

The publisher's own server: type.com

Overview

AI-generated overview

PaperType renders Markdown, HTML or invoice, certificate and report templates to PDF files through the PaperType API, saving them locally.

What you can do
  • Render Markdown, HTML or document templates (invoices, certificates, reports) into PDF files.
  • Save the rendered PDFs to a local output directory, defaulting to a folder under the OS temp directory.
  • Send rendering requests to the PaperType API, with the API origin configurable for test deployments.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when an assistant needs to turn Markdown, HTML or a document template into a finished PDF file on the user's machine, for example generating invoices, certificates or reports without a separate rendering step.
Requirements
Runs locally over stdio via npx (Node.js required). Needs a PaperType API key in PAPERTYPE_API_KEY, obtained by signing up at papertype.dev. Optional PAPERTYPE_BASE_URL (default and PAPERTYPE_OUTPUT_DIR (default OS temp dir plus /papertype). Network access to the PaperType API.
Before you install
Requires a PaperType API key stored in PAPERTYPE_API_KEY; keep it out of shared configs. Document content is sent to the PaperType API for rendering, so avoid sending confidential material unless that is acceptable. Rendered PDFs are written to PAPERTYPE_OUTPUT_DIR, which may be a shared temp location.

Installation

In SourceWeft

  1. Open PaperType 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.

Tools

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

Version history

1
  1. v0.1.0LatestOct 19, 2026

Score

15% 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

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Type integrations