Nutrient Dws MCP Server

Unclaimed

by PSPDFKit

A Model Context Protocol (MCP) server implementation that integrates with the Nutrient Document Web Service (DWS) Processor API, providing powerful PDF processing capabilities for AI assistants.

Install

$npx @nutrient-sdk/dws-mcp-server

Unclaimed listing

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Tools (17)

agentic

Spatial or Markdown

ai_redactor

AI redaction for detecting and permanently removing sensitive content such as names, addresses, SSNs, emails, and custom criteria

check_credits

Read-only account lookup for current DWS credits and usage. No document content is uploaded

directory_tree

Read-only view of local files when sandbox mode is disabled. Sandbox mode is strongly recommended

document_processor

Document processing for conversions, OCR, watermarking, rotation, annotation flattening, and redaction workflows

document_signer

PDF signing with CMS / PKCS#7 and CAdES signatures plus visible or invisible appearance options

extract_fields

Schema-guided field extraction (DWS Data Extraction API): pulls specific named fields into a JSON shape you define, with per-field citations

includeCitations

(server default true), strict (default false), and multimodal (default false, increases cost/latency) are only sent when you set them explicitly.

instructions

(free text, up to 10000 characters) adds guidance for ambiguous fields. language/maxLanguages/maxScripts tune OCR the same way as parsedocument.

language

OCR language(s) for structure/understand/agentic modes; left unset, the API auto-detects. maxLanguages / maxScripts cap how many languages/scripts auto-detection considers, and only apply when language is left unset.

mode

runs the parse feeding the extraction: structure (1.5 credits/page), understand (default, 9 credits/page), or agentic (18 credits/page) — no text mode, since schema-guided extraction needs the structural parse text mode skips. Total cost per page is that parse component plus a fixed extract componen

OAuth

(no NUTRIENTDWSAPIKEY set): the same browser-flow token used by every other tool also covers Data Extraction. No extra configuration is needed.

output.data

is always returned inline, pretty-printed — it is the answer, bounded by your own schema. Alongside it, a citation match summary reports how each field was grounded (idmatch, idmatchmultiblock, idmatchpartial, fuzzymatch, notfound) and lists which field paths came back notfound (capped at 10, then "

parse_document

Structured data extraction (DWS Data Extraction API): typed JSON elements with bounding boxes and confidence, or whole-document Markdown

sandbox_file_tree

Read-only view of files inside the configured sandbox directory

structure

Spatial or Markdown

text

Markdown only