DocPenny PDF Generator

com.docpennyPublished by docpenny.comOfficial publisherv1.0.1Updated Oct 24, 2026

Generate HTML to PDF documents in bulk or single — raw replacements or based on conditions, loops

VerifiedStreamable HTTPWeb executableFiles & Storage

Overview

AI-generated overview

Remote DocPenny server that lets an assistant turn HTML into PDF documents, one at a time or in bulk, with replacements, conditions and loops.

What you can do
  • Generate a PDF document from HTML content.
  • Produce documents in bulk from a single template.
  • Apply raw text replacements, conditional sections and loops when rendering.
When to use it
Useful when you need PDF output from HTML templates, especially repeated or personalized documents such as invoices, reports or letters generated in batches.
Requirements
A remote endpoint at mcp.docpenny.com over streamable HTTP; no local package or runtime. A DocPenny API key supplied in the x-api-key header is required.
Before you install
The API key in the x-api-key header is a secret; keep it out of shared logs and conversations. HTML content and any data used in replacements, conditions or loops is sent to DocPenny's servers, so avoid including sensitive material you do not want processed there.

Installation

In SourceWeft

  1. Open DocPenny PDF Generator in the dashboard and add it to a workspace.
  2. Connect x-api-key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.docpenny%2Fpdf-generator/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "docpenny-pdf-generator": {
      "type": "http",
      "url": "https://mcp.docpenny.com/mcp",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

39% 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 daysRequired25 pts

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

  • Auth declaredRequired10 pts
  • 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

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.