PDFLoom

dev.pdfloomPublished by pdfloom.devOfficial publisherv1.1.0Updated Nov 1, 2026

HTML or URL to PDF with headless Chrome, and invoice/receipt/quote PDFs from JSON.

VerifiedStreamable HTTPWeb executableFiles & Storage

Overview

AI-generated overview

Remote MCP server that turns HTML or a URL into a PDF with headless Chrome, and builds invoice, receipt or quote PDFs from JSON.

What you can do
  • Convert HTML or a web URL into a PDF using headless Chrome.
  • Generate invoice, receipt and quote PDFs from JSON input.
  • Connect over a hosted remote endpoint rather than a local package.
When to use it
Useful when an assistant needs to produce PDF documents — rendering a page or HTML snippet, or issuing business documents such as invoices, receipts and quotes — without running a browser locally.
Requirements
A remote MCP endpoint at pdfloom.dev over streamable HTTP. Authentication is required: either an API key sent in the Authorization header, or OAuth sign-in for clients that support it. No local runtime or packages are needed.
Before you install
The server requires credentials: an API key in the Authorization header, or an OAuth sign-in. Content you submit (HTML, URLs, JSON document data) is sent to a third-party hosted service, so avoid sending confidential pages or customer data unless that is acceptable. No pricing or data-retention details are provided.

Installation

In SourceWeft

  1. Open PDFLoom in the dashboard and add it to a workspace.
  2. Connect the required 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/dev.pdfloom%2Fpdfloom/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "pdfloom": {
      "type": "http",
      "url": "https://pdfloom.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.1.0LatestNov 1, 2026
  2. v1.0.0Oct 29, 2026

Score

83% 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
  • 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
  • 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.