Nutrient Document Engine MCP Server

io.github.PSPDFKitPublished by GitHub account PSPDFKitv0.0.3Updated Oct 24, 2026

MCP server for self-hosted Nutrient Document Engine: extract, edit, redact, and annotate documents.

The publisher's own server: Nutrient MCP

Overview

AI-generated overview

Lets an assistant work with documents on a self-hosted Nutrient Document Engine: extract text and tables, edit, redact, and annotate PDFs.

What you can do
Exposes document processing tools over stdio for a self-hosted Nutrient Document Engine instance. Capabilities include extracting text, searching documents, rendering pages as images, and pulling form and table data; splitting documents, adding watermarks, duplicating files, and filling PDF forms; creating and applying redactions with preset patterns or custom regex; and adding, reading, or deleting annotations such as highlights, notes, and stamps. It also lists documents, returns metadata, and reports health.
When to use it
Choose it when document workflows must stay on-premises or in a private cloud and you want deployment control and data residency, rather than a hosted document API. It suits teams that need an assistant to read, edit, redact, or annotate documents already loaded into their own Document Engine instance.
Requirements
Runs locally via npx, so Node.js 18+ is needed, plus a reachable Nutrient Document Engine instance (Docker Compose is suggested for local use). Required environment variables: DOCUMENT_ENGINE_BASE_URL and DOCUMENT_ENGINE_API_AUTH_TOKEN. Optional: DASHBOARD_USERNAME, DASHBOARD_PASSWORD, LOG_LEVEL. Documents are uploaded through the local dashboard before processing.
Before you install
The server needs the secret DOCUMENT_ENGINE_API_AUTH_TOKEN, and optionally DASHBOARD_PASSWORD for the local status dashboard. Tools can modify documents: splitting, watermarking, duplicating, filling forms, applying redactions, and deleting annotations. Redaction and form filling change content, so verify results before relying on them. Document Engine runs in evaluation mode with limitations and watermarks until a purchased license is activated.

Installation

In SourceWeft

  1. Open Nutrient Document Engine MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Nutrient Document Engine MCP Server

[Document workflows using natural language]

[npm]

Connect AI agents to document processing.

This MCP server exposes document processing capabilities through natural language, supporting both direct human interaction and AI agent tool calling.

Which MCP Server Should I Use?

ServerBest forDeploymentCore capabilities
Nutrient DWS MCP ServerCloud document workflowsNutrient-hosted API (API key)Convert, OCR, redact, sign, extract, watermark, automation
Nutrient Document Engine MCP ServerSelf-hosted document workflowsOn-prem/private cloudDocument processing with deployment control and data residency

You are in the Document Engine MCP Server repo. Choose this when you need self-hosted/on-prem document workflows and deployment control.

Example Conversations

Once configured, you (or your agent) can interact with documents through natural language:

You: "What documents do I have available?"
AI: "I can see you have 3 documents: annual-report.pdf, contract-draft.pdf, and tax-form-2023.pdf. Would you like me to analyze any of these?"

You: "Extract all the names and phone numbers from these invoices"
AI: "I found 12 contacts: John Smith (555-0123), Sarah Johnson (555-0456)..."

You: "Redact all social security numbers from these tax forms"
AI: "I've identified and redacted 3 SSNs across 2 documents. The redacted versions are ready."

You: "Split this 50-page contract into separate sections"
AI: "I've split the contract into 5 sections: Terms (pages 1-8), Payment (pages 9-15)..."

Setup with Claude Desktop

[Document Engine MCP Server + Claude Desktop]

Prerequisites

Licensing

Nutrient Document Engine runs with an evaluation license by default. Please see Removing Evaluation Limitations section on how to remove the evaluation limitations.

1. Start Nutrient Document Engine

Open a terminal window, then run:

bash
git clone https://github.com/PSPDFKit/nutrient-document-engine-mcp-server.gitcd nutrient-document-engine-mcp-serverdocker-compose up -d

2. Connect Claude Desktop

Add this to your Claude Desktop config (Settings → Developer → Edit Config):

json
{  "mcpServers": {    "nutrient-document-engine": {      "command": "npx",      "args": ["-y", "@nutrient-sdk/document-engine-mcp-server"],      "env": {        "DASHBOARD_USERNAME": "admin",        "DASHBOARD_PASSWORD": "password",        "DOCUMENT_ENGINE_BASE_URL": "http://localhost:5000",        "DOCUMENT_ENGINE_API_AUTH_TOKEN": "secret"      }    }  }}

3. Restart Claude Desktop

4. Upload and Process Documents

  1. Open your web browser and go to http://localhost:5100/dashboard.
  2. Upload the documents you want to work with by using the drag-and-drop interface.
  3. Switch back to Claude Desktop and ask questions like: "List my documents and extract text from the contract"

HTTP Transport Security

The optional HTTP transport binds to 127.0.0.1 by default. A non-loopback MCP_HOST requires MCP_HTTP_AUTH_TOKEN; the server refuses to start without a nonempty token. Clients must send the token on every /mcp request as Authorization: Bearer <token>. If a token is set for a loopback HTTP server, /mcp requires it there too. This token does not protect /health or /dashboard; dashboard access uses DASHBOARD_USERNAME and DASHBOARD_PASSWORD.

bash
# Local-only HTTP transport; no MCP bearer token required.MCP_TRANSPORT=http npx @nutrient-sdk/document-engine-mcp-server
# Network-accessible HTTP transport; bearer authentication is required.MCP_TRANSPORT=http MCP_HOST=0.0.0.0 MCP_HTTP_AUTH_TOKEN=replace-with-a-secret \  npx @nutrient-sdk/document-engine-mcp-server

The default stdio transport is unchanged and never requires MCP_HTTP_AUTH_TOKEN.

Features

This MCP server provides document processing tools in these areas:

Content Access: Extract text, search documents, render pages as images, extract form data and table structures.

Document Editing: Split documents, add watermarks, duplicate documents, fill PDF forms.

Security: Create and apply redactions for sensitive data using preset patterns (SSNs, credit cards, etc.) or custom regex.

Annotations: Add, read, and delete document annotations including highlights, notes, and stamps.

System: Document discovery, metadata retrieval, and health monitoring.

Use with Other AI Platforms

This MCP server works with any AI platform that supports the Model Context Protocol:

  • Claude Desktop - Quick setup with the configuration above.
  • LangGraph - Integrate with LangGraph agents for complex workflows.
  • OpenAI APIs - Connect through MCP-compatible frameworks.
  • Custom agents - Any MCP-compatible AI system.

Examples and Documentation

Examples

Documentation

Removing Evaluation Watermarks and Limitations

Document Engine runs in evaluation mode with limitations by default. To remove them:

  1. Contact Sales to purchase a license from Nutrient
  2. Configure your license by setting the ACTIVATION_KEY environment variable in your Docker Compose configuration or Document Engine setup
  3. Restart Document Engine to apply the license

For detailed licensing configuration, see the Document Engine licensing guide.

Server Based Document Engine Setups

On-Premise Installation: Follow the Nutrient Document Engine installation guide.

Managed Cloud: Use a hosted Document Engine instance - setup guide.

Contributing

We welcome contributions! See CONTRIBUTING.md for development setup, testing guidelines, and how to submit pull requests.

License

MIT License - see LICENSE file for details.

Source: README.md at commit 0b4c7d0

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.0.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Nutrient integrations