MinerU
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Create and edit PDFs: text, Markdown, tables, metadata and pages, with Japanese font embedding.
教 AI 做这类工作的 Skill,可与本项一起使用
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 28/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 40/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 202 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 PDF Writer (PDF Agent Stack)。按照 https://mcp.popnx.com/i/shuji-bonji-pdf-writer-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月20日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server PDF Writer (PDF Agent Stack),按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "pdf-writer": { "command": "npx", "args": [ "-y", "@shuji-bonji/pdf-writer-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 PDF Writer (PDF Agent Stack) 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"pdf-writer": {
"command": "npx",
"args": [
"-y",
"@shuji-bonji/pdf-writer-mcp"
]
}
}
}用 PDF Writer (PDF Agent Stack) 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 PDF Writer (PDF Agent Stack),或回答中出现 PDF Writer (PDF Agent Stack) 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 PDF Writer (PDF Agent Stack)
PDF Writer (PDF Agent Stack) 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server PDF Writer (PDF Agent Stack),按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user pdf-writer -- npx -y @shuji-bonji/pdf-writer-mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 PDF Writer (PDF Agent Stack) 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user pdf-writer -- npx -y @shuji-bonji/pdf-writer-mcp应能看到 PDF Writer (PDF Agent Stack) 在列表中并显示已连接
用 PDF Writer (PDF Agent Stack) 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 PDF Writer (PDF Agent Stack),或回答中出现 PDF Writer (PDF Agent Stack) 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server PDF Writer (PDF Agent Stack),按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "pdf-writer": { "command": "npx", "args": [ "-y", "@shuji-bonji/pdf-writer-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 PDF Writer (PDF Agent Stack) 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 PDF Writer (PDF Agent Stack) 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 PDF Writer (PDF Agent Stack),或回答中出现 PDF Writer (PDF Agent Stack) 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server PDF Writer (PDF Agent Stack),按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "pdf-writer": { "type": "stdio", "command": "npx", "args": [ "-y", "@shuji-bonji/pdf-writer-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 PDF Writer (PDF Agent Stack) 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 PDF Writer (PDF Agent Stack) 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 PDF Writer (PDF Agent Stack),或回答中出现 PDF Writer (PDF Agent Stack) 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user pdf-writer -- npx -y @shuji-bonji/pdf-writer-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"pdf-writer": {
"command": "npx",
"args": [
"-y",
"@shuji-bonji/pdf-writer-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"pdf-writer": {
"command": "npx",
"args": [
"-y",
"@shuji-bonji/pdf-writer-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"pdf-writer": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@shuji-bonji/pdf-writer-mcp"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 shuji-bonji 验证,该账户拥有此仓库
代码最后更新于10天前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 @shuji-bonji/pdf-writer-mcp@0.28.1 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/shuji-bonji-pdf-writer-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于10天前,最新版本(0.28.1)于10天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Puter MCP, XcodeBuildMCP, Vexa, Atlassian Rovo MCP Server, Anki MCP Server
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
MCP server for Anki flashcards: adaptive review, notes, media, and deck management via AnkiConnect.
| 本项 PDF Writer (PDF Agent Stack) | Puter MCP | XcodeBuildMCP | Vexa | Atlassian Rovo MCP Server | Anki MCP Server | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 需要安装在电脑上 |
| 需要密钥 | 否 | 否 | 否 | 是 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 3/3 | 4/4 | 3/3 | 2/4 | 4/4 | 3/3 |
| 许可证 | MIT | AGPL-3.0 | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
MCP server that creates PDFs from text, Markdown, or tabular data and edits existing ones (metadata and page operations). Built on normativepdf — a clause-driven PDF library in which every behaviour is tied to an ISO 32000 clause — with CJK font embedding via harfbuzz subsetting.
Part of the PDF family alongside pdf-reader-mcp (structure analysis) and pdf-verify-mcp (authenticity verification). Where pdf-reader-mcp tells you *what is in* a PDF and pdf-verify-mcp tells you *whether it is genuine*, pdf-writer-mcp is the one that *writes it*.
[!IMPORTANT]
All file paths must be absolute (since v0.7.0). Relative paths and paths containing
..are rejected — a relative path would resolve against the MCP host's working directory, which is not the directory you think it is. This applies toinputPath,inputPaths,outputPath,outputDir,fontPathandattachmentPath. Input PDFs larger than 100 MB are also rejected.
| Tool | Purpose |
|---|---|
create_text_pdf | Plain text — honours \n, blank lines separate paragraphs, long lines wrap |
create_markdown_pdf | Markdown — headings, paragraphs, bullet/ordered lists, code blocks, quotes, rules, tables |
create_table_pdf | Ruled tables — automatic column widths, cell wrapping, headers repeated across page breaks |
Shared options: outputPath, returnBase64, fontPath, fontSize, pageSize (A4/A3/A5/LETTER/LEGAL), margin, title, drawTitle, author, onMissingGlyph, tagged, lang, pdfVersion.
Pass pdfVersion: "2.0" to write an ISO 32000-2 file. The default stays "1.7", and its bytes are unchanged.
The version is not only a header. ISO 32000-2 attaches two obligations to it, and both are met:
SOURCE_DATE_EPOCH.CreationDate and ModDate (§14.3.3); the title, author and producer move to the XMP metadata stream, where PDF 2.0 says document metadata belongs.{ "text": "Body.", "title": "Report", "pdfVersion": "2.0" }
With tagged: true, a 2.0 file declares PDF/UA-2 (ISO 14289-2) instead of PDF/UA-1, which allows only PDF 1.0 to 1.7 (ISO 14289-1 §6.1). See PDF/UA-2 below. Up to v0.26.x the combination was refused.
Pass tagged: true to produce an accessible, tagged PDF conforming to PDF/UA-1 (ISO 14289). Output is verified compliant by veraPDF (--flavour ua1, 106/106 rules).
{ "markdown": "# Title\n\nBody.", "title": "Report", "tagged": true, "lang": "en" }
Markdown maps onto the structure tree: headings → H1–H6, lists → L/LI/LBody, tables → Table/TR/TH/TD (headers get /Scope), quotes → BlockQuote, code → Code. Rules, borders and code backgrounds become artifacts. Under PDF/UA-1, heading levels are normalised so they start at H1 and never skip — a Markdown # → ### jump becomes H1 → H2 in the structure, while visual sizes stay as authored (PDF/UA-2 keeps the level as written; see below).
PDF/UA mandates a document title, so tagged: true requires title. The title is always written to the metadata (dc:title) and, by default, also drawn as the first H1. When the Markdown already starts with its own # … heading, pass drawTitle: false: the title then stays in the metadata only, and the first body heading becomes H1 (## → ### becomes H1 → H2). Output stays PDF/UA-1 compliant (veraPDF 106/106). lang (BCP 47) is inferred from the text when omitted and reported via warnings — pass it explicitly when you know it, since a wrong /Lang makes screen readers mispronounce the text.
[!NOTE]
Tagging is opt-in — default output is unchanged.
Machine validation (veraPDF) only sees whether things *exist*. It cannot judge whether reading order or alt text are *appropriate* — human review still matters.
Add pdfVersion: "2.0" to tagged: true and the file is written as PDF/UA-2 (ISO 14289-2:2024) on PDF 2.0. The default (1.7, PDF/UA-1) is unchanged.
{ "markdown": "# Title\n\nBody.", "title": "Report", "tagged": true, "pdfVersion": "2.0", "lang": "en" }
What differs from the PDF/UA-1 output, with the clause behind each:
| PDF/UA-1 (1.7) | PDF/UA-2 (2.0) | |
|---|---|---|
| XMP declaration (§5) | pdfuaid:part 1 | pdfuaid:part 2 and pdfuaid:rev 2024 |
| Namespaces (§8.2.4, §8.2.5.2) | none (the default PDF 1.7 namespace) | Document and every type the PDF 2.0 namespace has get /NS → http://iso.org/pdf2/ssn; BlockQuote and Code, which it lacks, stay in the PDF 1.7 namespace |
| Drawn title (§8.2.5.13) | first H1 | Title (not a heading) |
| Markdown headings (§8.2.5.12) | normalised to start at H1 and never skip | the level as written (# → H1, ### → H3) |
| Nested lists | inside the parent item's LBody | directly in the parent L, right after the item (ISO 32000-2 §14.8.4.8.2) |
Measured with veraPDF 1.30.0 (pdfua-2, 1,728 rules): the output of all three create tools, ensure_tagged on an untagged PDF 2.0 file, and ensure_pdfa(flavour: "pdfa-4") on a PDF/UA-2 file all pass, and the last one also passes PDF/A-4 (109/109).
Edits keep the declaration: when a tool rebuilds the XMP, pdfuaid:rev is carried with pdfuaid:part, and dc:title is kept when the Info dictionary has no Title (PDF 2.0 output does not put one there). add_bookmarks writes structure destinations on a PDF/UA-2 file, as §8.8 requires: a GoTo action whose SD names the structure element that starts on the target page, with D kept as the page destination for viewers that do not read SD. A page with no structure content keeps a page destination and is named in warnings.
An edit writes the PDF version of its input. Only an explicit conversion changes it: ensure_pdfa with flavour: "pdfa-4" / "pdfa-4f" (to PDF 2.0), and merge_pdfs with pdfVersion. Versions are never lowered.
INVALID_ARGUMENT. The message names the input's version and declarations; next_actions gives a call that fits. Examples: merge_pdfs over PDF 2.0 and PDF 1.x inputs without pdfVersion, and ensure_pdfa(flavour: "pdfa-3b") on any PDF 2.0 input (PDF/A-3 needs a %PDF-1.n header).set_metadata writes to XMP and adds no Info entries (ISO 32000-2 §14.3.3); on a PDF/UA-2 input it also moves the existing Info entries to XMP and removes them (ISO 14289-2 §6.2).add_annotation and tag_form_fields add to a PDF/UA-2 file have no /NS, so they sit in the PDF 1.7 namespace (§8.2.4 allows it); warnings says so.Every tool result carries output, read back from the written file:
{ "output": { "pdfVersion": "2.0", "declares": { "pdfua": 2, "pdfa": "4" } } }
declares.pdfua is pdfuaid:part; declares.pdfa joins pdfaid:part and pdfaid:conformance ("3b", "4", "4f"). A key is absent when nothing is declared. A declaration is only a claim — measure it with pdf-verify-mcp.
When a tool rewrites the XMP (set_metadata, ensure_pdfa), the values you did not pass are carried over as written: the other languages of dc:title, every name in dc:creator, and properties in namespaces this server does not know. Changing title replaces the x-default entry and names the other languages in warnings.
| Tool | Purpose |
|---|---|
merge_pdfs | Concatenate 2–50 PDFs in order; metadata inherited from the first file. Inputs that mix PDF 2.0 and PDF 1.x need pdfVersion: "2.0" |
split_pdf | One output file per page range |
extract_pages | Extract pages in the requested order (doubles as reordering) |
delete_pages | Remove pages (deleting every page is rejected) |
reorder_pages | Reorder by an explicit permutation of all pages |
rotate_pages | Rotate clockwise (90/180/270), accumulating over existing rotation. Edits in place, so the warning below does not apply |
[!WARNING]
The five tools other than `rotate_pages` rebuild the document from its pages.
- Carried over: attachments (
/Names /EmbeddedFiles,/AF),/Lang,/ViewerPreferences,/OutputIntents
- Not carried over: the tagged structure tree, XMP, and anything tied to page numbers or page references (bookmarks, page labels, named destinations)
- Whatever is lost is reported in
warnings— nothing disappears silently
Page specs use "1,3-5,8-" (1-based; -3 means up to page 3, 8- means page 8 to the end). Order is preserved and duplicates are removed.
| Tool | Purpose | |
|---|---|---|
set_metadata | Update Info dictionary fields (title / author / subject / keywords / creator), preserving the rest. On documents carrying XMP, dc:title etc. are kept in sync (PDF/UA and PDF/A declarations preserved). tdmReservation (0 \ | 1) and tdmPolicy write the W3C TDMRep rights statement to XMP (tdm:reservation / tdm:policy, namespace http://www.w3.org/ns/tdmrep/); a document without XMP gets one, and a PDF/A document also gets the schema described in pdfaExtension:schemas, so veraPDF does not fail ISO 19005-2 6.6.2.3 on it (v0.22.0) |
add_bookmarks | Set the outline (bookmarks); nestable via children, replaces any existing outline | |
add_annotation | Add a sticky note (text), highlight, or square annotation. On tagged PDFs the annotation is nested in an Annot element and stays PDF/UA conformant — pass alt to describe it. On PDF/UA-2, alt is also written as Contents (§8.9.4.2 requires them to match), and a different contents is refused | |
attach_file | Embed a file (/Names /EmbeddedFiles + catalog /AF + /AFRelationship) — the PDF/A-3 shape | |
stamp_page_numbers | Stamp page numbers ({n} / {total}, six positions, pages, startAt). Becomes an artifact on tagged PDFs, so conformance holds | |
fill_form | Fill AcroForm fields. Japanese values via an embedded font; can flatten in the same pass | |
flatten_form | Flatten a form into static content. Refuses tagged PDFs by default (breaks PDF/UA) | |
tag_form_fields | Repair the form inside a tagged PDF for PDF/UA-1 (nest widgets in Form, set /Tabs S, add /TU alternate names; pass labels for human-readable names). On PDF/UA-2, widgets also get /Contents (§8.10.2.3). Idempotent | |
ensure_tagged | Put an existing PDF into the PDF/UA-1 container → Scaffolding an untagged PDF | |
ensure_pdfa | Put an existing PDF into the PDF/A-3b / PDF/A-4 / PDF/A-4f container (flavour) → The archival container | |
add_watermark | Overlay a diagonal watermark ("社外秘" / "DRAFT"). Behind the body content by default; artifact on tagged PDFs |
Shared options: outputPath, returnBase64, allowBreakingSignatures.
[!IMPORTANT]
Editing signed PDFs: an ordinary sa