Integration

Nutrient DWS Processor API integration

Nutrient DWS Processor API (formerly PSPDFKit) processes documents in the cloud: convert Office files, images, e-mails, HTML and Markdown to PDF, run OCR, watermark, redact by search or with AI, digitally sign PDFs, fill DOCX, XLSX and PPTX templates with JSON, and build documents from several inputs with outputs such as PDF/A, images, Office, HTML, Markdown or extracted JSON. Every processing call spends credits (the Free plan has 50 a month and stamps its output with a For Evaluation Purposes Only watermark unless pay-as-you-go is enabled; analyze_build gives a build's cost free) and returns the result as a file. Left out on purpose: async jobs (they hand out a per-job access token), Viewer session token minting and the deprecated account info route. On plans with data retention enabled, Nutrient may retain submitted files to improve its services and train models, and special-category personal data must not be submitted. Authentication: the live API key from the Nutrient dashboard (pdf_live_...), sent as a Bearer token.

Connect Nutrient DWS Processor API How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Nutrient DWS Processor API.Built from the 12 Nutrient DWS Processor API tools below, on the connection you add once.

What you can do with Nutrient DWS Processor API

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Document, 9 operations

ai_redact_pdfAi redact pdfPOSTUses AI to find content matching plain-language criteria (for example all personal names and addresses) in a PDF and redacts it, returning the PDF as a file. Listed at 0.05 credits.
convert_html_to_pdfConvert html to pdfPOSTRenders an HTML file to PDF and returns the PDF as a file. Spends 0.5 credits (HTML to PDF).
convert_markdown_to_pdfConvert markdown to pdfPOSTConverts a Markdown file (CommonMark with GFM tables, task lists, footnotes) to a styled PDF and returns it as a file. Spends credits (the pricing page lists no rate for it).
convert_to_pdfConvert to pdfPOSTConverts an Office document, image, e-mail (EML, MSG) or other supported file to PDF and returns the PDF as a file. Spends credits: Office to PDF 1, image to PDF 0.5.
fill_office_templateFill office templatePOSTFills a DOCX, XLSX or PPTX template with JSON data (placeholders, loops, images) and returns the filled document in the same format, as a file. DOCX templating is listed at 2 credits.
ocr_pdfOcr pdfPOSTRuns OCR on a PDF so its text becomes searchable and selectable, and returns the PDF as a file. Spends 2 credits.
redact_pdfRedact pdfPOSTFinds text by search term, regex or preset (e-mails, phone numbers, card numbers...) in a PDF and redacts it, returning the redacted PDF as a file. Spends 1 credit.
sign_pdfSign pdfPOSTDigitally signs a PDF (invisible signature by default, or a visible one at a position or form field) and returns the signed PDF as a file. Spends 10 credits.
watermark_pdfWatermark pdfPOSTAdds a text or image watermark to every page of a PDF and returns the watermarked PDF as a file. Spends 1 credit.

Build, 2 operations

analyze_buildAnalyze buildPOSTReturns how many credits a build_document request with these parts, actions and output would cost, without running it. Free of charge.
build_documentBuild documentPOSTBuilds a document from parts given by URL, applies actions and returns the result as a file (PDF by default). Spends credits per feature used; analyze_build gives the exact cost free.

Account usage, 1 operation

get_account_usageGet account usageGETReturns the subscription type and status and the usage counters (credits and other units used and allowed this period) for one Nutrient DWS product.

Use Nutrient DWS Processor API from Claude Code, Cursor or Codex

Connect Nutrient DWS Processor API in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Nutrient DWS Processor API operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Nutrient DWS Processor API

Create your workspace
Sign up free. Nothing to install.
Connect Nutrient DWS Processor API once
Add your Nutrient DWS Processor API connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.