Nutrient Document Engine MCP Server 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.
claude mcp add nutrient-document-engine-mcp-server -- npx -y nutrient-document-engine-mcp-server
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
62 ★ · PSPDFKit/nutrient-document-engine-mcp-server · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 62 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository PSPDFKit/nutrient-document-engine-mcp-server;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
**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? | Server | Best for | Deployment | Core capabilities | |---|---|---|---| | Nutrient DWS MCP Server | Cloud document workflows | Nutrient-hosted API (API key) | Convert, OCR, redact, sign, extract, watermark, automation | | Nutrient Document Engine MCP Server | Self-hosted document workflows | On-prem/private cloud | Document 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. - Ecosystem overview: Nutrient AI Infrastructure - Product landing page: Nutrient MCP Server 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 Prerequisites - **Claude Desktop** - Download from Anthropic. - **Docker Compose** - Download from Docker. For running Nutrient Document Engine locally. - **Node.js 18+** - This MCP server runs via npx. 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: 2. Connect Claude Desktop Add this to your Claude Desktop config (Settings → Developer → Edit Config): 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 . 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. The default stdio transport is unchanged and never requires MCP_HTTP_AUTH_TOKEN. Features This MCP server provides document processing tools in these areas: