Nutrient DWS MCP Server(opens in a new tab) is an open source utility that connects Nutrient Document Web Services (DWS) API to natural language interfaces via the Model Context Protocol (MCP)(opens in a new tab), enabling robust document operations — such as editing, conversion, and signing — via natural language commands.

Watch the demo video

YouTube video player

Key features

FeatureDescription
Document creationMerge PDFs, Office documents, and images
EditingWatermark, rotate, flatten, redact, and more
Format conversionPDF ⇄ DOCX, images, PDF/A support
Digital signingAdd PAdES standards-compliant digital signatures using trusted certificates
Data extractionExtract text, tables, or structured content
SecurityRedaction presets, password protection, permission control
Advanced OCRMulti-language image and scan recognition
OptimizationCompress files without quality loss

Getting started with Claude Desktop and Nutrient DWS MCP Server

  1. Install Claude Desktop(opens in a new tab), sign in, and launch the app.
  2. Download the latest .mcpb package from GitHub Releases(opens in a new tab).
  3. Install the package in Claude Desktop and choose your sandbox path.
  4. Drop documents into the sandbox folder to prepare them for processing.
  5. Use Claude to run prompts like “Redact all PII from secret.pdf” or “Merge secret.pdf and contract.pdf.”
  6. Claude opens a browser for OAuth the first time a Nutrient action runs.

MCP currently relies on local file operations. Sandbox directories ensure safe batch processing.

Claude Desktop is the recommended starting point. If you use another MCP client, follow the setup below.

Using other MCP clients

  1. Install Node.js using a package manager like Homebrew (brew install node), or download it directly from nodejs.org(opens in a new tab).

  2. Configure your MCP client to run Nutrient DWS MCP Server and set your desired sandbox path:

    {
    "mcpServers": {
    "nutrient-dws": {
    "command": "npx",
    "args": [
    "-y",
    "@nutrient-sdk/dws-mcp-server",
    "--sandbox",
    "/your/sandbox/directory"
    ]
    }
    }
    }
  3. Restart your MCP client, drop documents into the sandbox folder, and start prompting.

  4. The first Nutrient action opens a browser so you can sign in or create a free Nutrient account.

If you run MCP in CI, a headless environment, or another non-interactive setup, add an env block with your API key:

{
"env": {
"NUTRIENT_DWS_API_KEY": "YOUR_API_KEY_HERE"
}
}

Use cases

The following examples show how teams use natural language prompts with Nutrient DWS MCP Server to automate common document workflows.

Contract automation

  • Digitally sign or watermark NDAs in batches
  • Merge scans, flatten layers, prepare for archiving
  • Auto-extract terms or dates with OCR

Compliance and archival

  • Convert documents to PDF/A
  • Redact emails or credit cards with built-in presets
  • Watermark board decks for internal sharing

Content extraction

  • Extract tabular data or text for import
  • OCR scanned receipts or handwritten notes
  • Preoptimize documents before archiving

FAQ

Why is this file system-based instead of supporting API uploads?

MCP currently doesn’t support binary file transfer — using a sandbox directory is the next best secure option.

Why is it open source?

Flexibility and extensibility. Contribute, fork, and adapt the tool to your use case.