# PSPDFKit/nutrient-document-engine-mcp-server [Health: Active]

**Category:** 🛠️ Other Tools and Integrations  
**Repository:** https://github.com/PSPDFKit/nutrient-document-engine-mcp-server  
**GitHub Stars:** 62  
**npm Downloads (last month):** 55  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/pspdfkit-nutrient-document-engine-mcp-server

## Description
Self-hosted MCP server for Nutrient Document Engine. On-premises document processing with natural language control — designed for HIPAA, SOC 2, and GDPR compliance.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "nutrient-document-engine-mcp-server": {
    "command": "npx",
    "args": ["-y","@nutrient-sdk/document-engine-mcp-server"],
    "env": {
      "DASHBOARD_USERNAME": "",
      "DASHBOARD_PASSWORD": "",
      "DOCUMENT_ENGINE_BASE_URL": "",
      "DOCUMENT_ENGINE_API_AUTH_TOKEN": "",
      "MCP_TRANSPORT": "",
      "MCP_HOST": "",
      "MCP_HTTP_AUTH_TOKEN": "",
      "ACTIVATION_KEY": ""
    }
  }
}
```

**Requires environment variables:** `DASHBOARD_USERNAME`, `DASHBOARD_PASSWORD`, `DOCUMENT_ENGINE_BASE_URL`, `DOCUMENT_ENGINE_API_AUTH_TOKEN`, `MCP_TRANSPORT`, `MCP_HOST`, `MCP_HTTP_AUTH_TOKEN`, `ACTIVATION_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What PSPDFKit/nutrient-document-engine-mcp-server does

PSPDFKit/nutrient-document-engine-mcp-server provides an MCP interface to Nutrient Document Engine, allowing an AI client to invoke document-processing operations through natural-language requests or direct tool calls. Documents are managed by the connected Document Engine instance, while the MCP server exposes the available operations to an MCP-compatible client.

The project is intended for self-hosted or private-cloud deployments where the operator controls the Document Engine location and document data residency. It is separate from Nutrient's cloud-oriented DWS MCP Server, which is designed for hosted API workflows.

## How it works

The default connection method is stdio. An MCP client starts the server with `npx`, and the server uses configuration values to reach the Document Engine API. Documents are uploaded through the Document Engine dashboard at the configured local address, then made available for processing through the connected AI client.

An optional HTTP transport can expose the MCP endpoint. It binds to `127.0.0.1` by default. If configured with a non-loopback host, it requires a nonempty `MCP_HTTP_AUTH_TOKEN`, and clients must send that value as a bearer token on every `/mcp` request. A token can also be required for loopback HTTP deployments. The `/health` and `/dashboard` paths are not protected by this MCP bearer token; dashboard access uses its own username and password settings.

## Setup and configuration

Running the PSPDFKit/nutrient-document-engine-mcp-server setup requires Node.js 18 or newer for the `npx`-based MCP process and Docker Compose to run Nutrient Document Engine locally. The documented Claude Desktop setup starts Document Engine with Docker Compose, then adds an MCP entry whose command is `npx` and whose package is `@nutrient-sdk/document-engine-mcp-server`.

The example configuration supplies `DASHBOARD_USERNAME`, `DASHBOARD_PASSWORD`, `DOCUMENT_ENGINE_BASE_URL`, and `DOCUMENT_ENGINE_API_AUTH_TOKEN`. After restarting the client, documents can be uploaded through the Document Engine dashboard and queried from the MCP conversation.

Document Engine uses an evaluation license by default. Removing evaluation limitations requires purchasing a Nutrient license and setting `ACTIVATION_KEY` in the Document Engine or Docker Compose configuration, then restarting Document Engine. The activation key is a Document Engine setting rather than an MCP client credential.

## Tools and capabilities

The PSPDFKit/nutrient-document-engine-mcp-server README groups its document operations into these areas:

- Content access: extract text, search documents, render pages as images, and extract form data or table structures.
- Document editing: split and duplicate documents, add watermarks, and fill PDF forms.
- Security: create and apply redactions using preset sensitive-data patterns, such as social security numbers and credit cards, or custom regular expressions.
- Annotations: add, read, and delete highlights, notes, stamps, and other document annotations.
- System operations: discover documents, retrieve metadata, and monitor health.

The repository also includes examples for LangGraph, OpenAI Agents SDK workflows, a document-chat interface, and a procurement agent. These examples demonstrate possible integrations; they are not required for the MCP server's basic operation.

## Limitations and notes

It does not provide client-specific setup instructions for every platform.

HTTP authentication protects MCP requests only. Dashboard credentials remain separately configured, and `/health` is not covered by the MCP bearer token. Evaluation mode may impose watermarks or other limitations until a licensed Document Engine configuration is supplied.

_Full upstream README: https://allmcps.com/mcp/pspdfkit-nutrient-document-engine-mcp-server/readme_