Nutrient Document Engine MCP Server

io.github.PSPDFKit由 GitHub 账号 PSPDFKit 发布v0.0.3更新于 Oct 24, 2026

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

发布方自己的服务:Nutrient MCP

已验证STDIO仅桌面效率与工作流文件与存储

概览

AI 生成的概览

让助手在自托管的 Nutrient Document Engine 上处理文档:提取文本与表格、编辑、涂黑和批注 PDF。

可以做什么
通过 stdio 为自托管的 Nutrient Document Engine 实例提供文档处理工具。能力包括提取文本、搜索文档、将页面渲染为图像、获取表单与表格数据;拆分文档、添加水印、复制文件、填写 PDF 表单;使用预设模式或自定义正则创建并应用涂黑;以及添加、读取或删除高亮、注释和印章等批注。还可列出文档、返回元数据并报告健康状态。
适用场景
当文档处理必须留在本地或私有云,并且需要部署控制与数据驻留时,适合选用它,而不是托管式文档 API。它适合需要助手读取、编辑、涂黑或批注已载入自有 Document Engine 实例的文档的团队。
运行要求
通过 npx 在本地运行,需要 Node.js 18+,以及可访问的 Nutrient Document Engine 实例(本地使用建议用 Docker Compose)。必需的环境变量:DOCUMENT_ENGINE_BASE_URL 和 DOCUMENT_ENGINE_API_AUTH_TOKEN。可选:DASHBOARD_USERNAME、DASHBOARD_PASSWORD、LOG_LEVEL。处理前需通过本地仪表板上传文档。
安装前请注意
该服务器需要机密 DOCUMENT_ENGINE_API_AUTH_TOKEN,本地状态仪表板可选需要 DASHBOARD_PASSWORD。工具会修改文档:拆分、加水印、复制、填写表单、应用涂黑以及删除批注。涂黑和表单填写会改变内容,依赖结果前请先核对。Document Engine 默认以评估模式运行,存在限制和水印,需激活已购买的许可证才能解除。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Nutrient Document Engine MCP Server,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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.

来源:README.md,提交 0b4c7d0

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.0.3最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Nutrient 集成