A Model Context Protocol (MCP) server implementation that integrates with the Nutrient Document Web Service (DWS) Processor API, providing powerful
Most browser automation work still happens through a UI a human drives. Nutrient DWS MCP server moves it into the conversation instead. 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.
A Model Context Protocol (MCP) server that connects AI assistants to the Nutrient Document Web Service (DWS) Processor API — enabling document creation, editing, conversion, digital signing, OCR, redaction, and more through natural language.
The server publishes 9 tools. What each one is for:
document_processor — Document processing for conversions, OCR, watermarking, rotation, annotation flattening, and redaction workflowsparse_document — Structured data extraction (DWS Data Extraction API): typed JSON elements with bounding boxes and confidence, or whole-document Markdownextract_fields — Schema-guided field extraction (DWS Data Extraction API): pulls specific named fields into a JSON shape you define, with per-field citationsdocument_signer — PDF signing with CMS / PKCS#7 and CAdES signatures plus visible or invisible appearance optionsai_redactor — AI redaction for detecting and permanently removing sensitive content such as names, addresses, SSNs, emails, and custom criteriacheck_credits — Read-only account lookup for current DWS credits and usage. No document content is uploadedsandbox_file_tree — Read-only view of files inside the configured sandbox directorydirectory_tree — Read-only view of local files when sandbox mode is disabled. Sandbox mode is strongly recommendedAuthentication — The server authenticates to the Nutrient DWS API (https://api.nutrient.io) using one of:Configuration is passed through the environment: SANDBOX_PATH, NUTRIENT_DWS_API_KEY, NUTRIENT_DWS_EXTRACTION_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as @nutrient-sdk/dws-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Nutrient DWS's toolset — document_processor, parse_document, extract_fields and 6 more — is a fair guide to whether it matches your workflow. It is maintained by PSPDFKit; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| document_processor | Document processing for conversions, OCR, watermarking, rotation, annotation flattening, and redaction workflows |
| parse_document | Structured data extraction (DWS Data Extraction API): typed JSON elements with bounding boxes and confidence, or whole-document Markdown |
| extract_fields | Schema-guided field extraction (DWS Data Extraction API): pulls specific named fields into a JSON shape you define, with per-field citations |
| document_signer | PDF signing with CMS / PKCS#7 and CAdES signatures plus visible or invisible appearance options |
| 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 |
| sandbox_file_tree | Read-only view of files inside the configured sandbox directory |
| directory_tree | Read-only view of local files when sandbox mode is disabled. Sandbox mode is strongly recommended |
| Authentication | The server authenticates to the Nutrient DWS API (https://api.nutrient.io) using one of: |
{
"mcpServers": {
"nutrient-dws": {
"command": "npx",
"args": ["-y", "@nutrient-sdk/dws-mcp-server"],
"env": {
"SANDBOX_PATH": "/your/sandbox/directory",
// "C:\\your\\sandbox\\directory" for Windows
// Optional for CI or headless usage:
// "NUTRIENT_DWS_API_KEY": "YOUR_API_KEY_HERE"
},
},
},
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SANDBOX_PATH | Filesystem location the server is allowed to use. | Optional |
| NUTRIENT_DWS_API_KEY | Credential the server authenticates with. | Yes |
| NUTRIENT_DWS_EXTRACTION_API_KEY | Credential the server authenticates with. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.