Log inSubmit server
Nutrient Dws MCP Server logo

Nutrient Dws MCP Server

by PSPDFKit

Process, extract, redact, sign, OCR, and convert local documents through Nutrient DWS using natural language.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Nutrient Dws MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "pspdfkit-nutrient-dws-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@nutrient-sdk/dws-mcp-server"
      ],
      "env": {
        "SANDBOX_PATH": "YOUR_VALUE_HERE",
        "NUTRIENT_DWS_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

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

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 24d ago.

Overview

PSPDFKit/nutrient-dws-mcp-server connects MCP-compatible AI clients to Nutrient Document Web Service Processor and Data Extraction APIs. It runs locally over stdio, reads files from a configured directory, and sends supported document operations to DWS. Available tools cover conversion, OCR, redaction, signing, watermarking, parsing, schema-based extraction, and credit checks. Reach for it when an agent needs natural-language document workflows with local file handling and structured extraction results.

Use cases

  • Convert Office documents to PDF/A
  • Extract invoice fields with citations
  • Redact personal information from PDFs
  • Sign and watermark contracts
  • Parse documents into Markdown for retrieval

Key features

  • PDF and Office document processing
  • OCR, conversion, watermarking, and redaction
  • Structured and schema-guided extraction
  • CMS, PKCS#7, and CAdES PDF signing
  • Sandbox-aware local file access
  • DWS credit and usage lookup

Tools8

What Nutrient Dws MCP Server lets your agent do. Expand a tool for its parameters.

Self-reported~245 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

Not checked yetLast checked 1d ago

We have not completed a health check for this listing yet.

15/21 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @nutrient-sdk/dws-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars71Stargazers on the source repository.
npm downloads396Package downloads in the last 30 days.
Last commit13d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed8Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Nutrient Dws MCP Server works

What PSPDFKit/nutrient-dws-mcp-server MCP server does

PSPDFKit/nutrient-dws-mcp-server MCP server exposes Nutrient DWS document-processing capabilities to MCP-compatible AI clients. It connects to the Nutrient Document Web Service Processor API for document transformations and the Data Extraction API for parsing and field extraction. The server is intended for workflows where an agent needs to work with PDFs or Office documents using natural-language requests.

Supported workflows include conversion, OCR, watermarking, rotation, annotation flattening, redaction, document merging, and PDF signing. Extraction can produce whole-document Markdown, typed JSON with bounding boxes and confidence values, or a JSON structure containing named fields and per-field citations.

How it works

The package runs as a local stdio MCP server. An AI client invokes one of its tools, and the server reads input files from the configured local directory before calling the relevant Nutrient DWS API. Results can be written to explicit output paths or returned as extracted content, depending on the operation.

The first request that uses the Nutrient API can start a browser-based OAuth sign-in. API-key authentication is also available for CI, headless environments, and scripted use. Data extraction offers four parse modes: text, structure, understand, and agentic; the README identifies understand as the default and lists different credit costs for each mode.

Setup and configuration

Install the package through an MCP client configuration with npx -y @nutrient-sdk/dws-mcp-server, or install it from Claude Desktop Extensions. Set SANDBOX_PATH to the directory containing documents the server may access. Sandbox mode is recommended because it limits file handling to the configured directory. When sandbox mode is disabled, the read-only directory_tree tool can inspect local files visible to the user account.

Create a Nutrient account before using the DWS APIs. For interactive desktop use, the browser sign-in flow can provide authentication without an API key. For non-interactive operation, set NUTRIENT_DWS_API_KEY with a key created in the Nutrient dashboard. Restart the MCP client after changing its configuration, then use explicit file names or paths in requests.

The README provides configurations for Claude Desktop, Cursor, Windsurf, and VS Code, and states that other MCP-compatible clients can use stdio transport.

Tools and capabilities

PSPDFKit/nutrient-dws-mcp-server MCP server provides these tools:

  • document_processor handles conversions, OCR, watermarks, rotation, annotation flattening, and redaction workflows.
  • parse_document returns Markdown or structured extraction data with spatial coordinates and confidence values.
  • extract_fields extracts named fields into a developer-defined JSON shape and can include citations for each field.
  • document_signer applies CMS, PKCS#7, or CAdES PDF signatures with visible or invisible appearances.
  • ai_redactor detects and permanently removes sensitive content, including common personal data and custom criteria.
  • check_credits reads DWS credit and usage information without uploading document content.
  • sandbox_file_tree lists files in the configured sandbox directory.
  • directory_tree lists local files when sandbox restrictions are disabled.

The package also documents prompts for chained tasks such as signing after watermarking, extracting fields, redacting personally identifiable information, parsing documents for retrieval, and converting Office files to PDF/A.

Limitations and notes

Document-processing and extraction requests depend on Nutrient DWS access and account credits. The check_credits tool is read-only and does not upload document content, but other tools may send documents to the corresponding DWS APIs. API-key authentication is optional for interactive OAuth use but needed for the documented CI and headless fallback. Sandbox mode is strongly recommended, and explicit paths are safer than vague file-browsing instructions.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Nutrient Dws MCP Server

PSPDFKit/nutrient-dws-mcp-server is an MCP server that connects AI clients to Nutrient Document Web Service Processor and Data Extraction APIs. Its main tools process, parse, extract, sign, redact, and inspect documents, while also checking account credits and reading configured local files through stdio.

Install it in an MCP client with `npx -y @nutrient-sdk/dws-mcp-server`, or use the Claude Desktop Extensions flow. Configure `SANDBOX_PATH`, optionally add `NUTRIENT_DWS_API_KEY` for headless use, and restart the client.

Yes, it works with Cursor through a project-level `.cursor/mcp.json` configuration. Define the server as a stdio process using `npx -y @nutrient-sdk/dws-mcp-server` and set the document directory with `SANDBOX_PATH`.

No, an API key is not required for interactive desktop use because the first Nutrient API request can open browser-based OAuth sign-in. Set `NUTRIENT_DWS_API_KEY` for CI, headless environments, or scripted operation.

Related MCP servers

All in Other Tools and Integrations All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNutrient Dws MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/pspdfkit-nutrient-dws-mcp-server?style=directory)](https://allmcps.com/mcp/pspdfkit-nutrient-dws-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/pspdfkit-nutrient-dws-mcp-server"><img src="https://allmcps.com/api/badge/pspdfkit-nutrient-dws-mcp-server?style=directory" alt="Nutrient Dws MCP Server on AllMCPs" /></a>