Permite que un cliente de IA extraiga texto, divida, redacte, añada marcas de agua, anote y rellene formularios en documentos PDF a través de un Document Engine autoalojado.
También conocido como PSPDFKit/nutrient-document-engine-mcp-server, nutrient-document-engine-mcp-server, @nutrient-sdk/document-engine-mcp-server
- Stars
- 62
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- 0.0.3
- Último commit
- 4 nov 2026
- Licencia
- MIT
¿Qué es Nutrient Document Engine MCP?
Nutrient Document Engine es un MCP server. Permite que un cliente de IA extraiga texto, divida, redacte, añada marcas de agua, anote y rellene formularios en documentos PDF a través de un Document Engine autoalojado.
Resumen generado a partir del README del proyecto
Acerca del MCP server de Nutrient Document Engine
Procesar documentos PDF mediante lenguaje natural es lo que este servidor permite a los desarrolladores que construyen flujos de trabajo de documentos privados. Conecta agentes de IA a un Document Engine autoalojado, lo que permite un despliegue local o on-premise para mantener una residencia de datos estricta. Los usuarios pueden interactuar con sus archivos usando Claude Desktop, LangGraph u otras plataformas compatibles con MCP ejecutando el motor a través de Docker Compose.
El servidor proporciona un conjunto de herramientas para el acceso, edición y seguridad del contenido. Permite que una IA extraiga texto, busque en archivos y renderice páginas como imágenes. Para la modificación de documentos, admite la división de archivos, la adición de marcas de agua y el llenado de formularios PDF. Las funciones de seguridad incluyen la redacción de información sensible, como números de seguridad social o detalles de tarjetas de crédito, utilizando patrones preestablecidos o regex personalizados.
La configuración requiere Node.js y una conexión a una instancia local mediante una URL base y tokens de autenticación. Aunque se ejecuta con una licencia de evaluación por defecto, los usuarios pueden eliminar las limitaciones proporcionando una clave de activación. Esta configuración está diseñada específicamente para quienes requieren control de despliegue sobre su infraestructura de procesamiento de documentos.
Qué puedes hacer con él
- 1Extracción de información de contactoPide a un agente de IA que encuentre detalles específicos como nombres y números de teléfono en una colección de facturas.
- 2Redacción de datos sensiblesAutomatiza la eliminación de información privada, como números de seguridad social, de documentos fiscales.
- 3División de archivos grandesInstruye a un agente para que divida un contrato extenso en secciones más pequeñas y manejables.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar Nutrient Document Engine MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar Nutrient Document Engine MCP en Claude Code
$ claude mcp add --env 'DOCUMENT_ENGINE_API_AUTH_TOKEN=<YOUR_DOCUMENT_ENGINE_API_AUTH_TOKEN>' --env 'DOCUMENT_ENGINE_BASE_URL=<DOCUMENT_ENGINE_BASE_URL>' --env 'DASHBOARD_PASSWORD=<YOUR_DASHBOARD_PASSWORD>' nutrient-document-engine-mcp-server -- npx -y @nutrient-sdk/document-engine-mcp-serverInstalar Nutrient Document Engine MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"nutrient-document-engine-mcp-server": {
"command": "npx",
"args": [
"-y",
"@nutrient-sdk/document-engine-mcp-server"
],
"env": {
"DOCUMENT_ENGINE_API_AUTH_TOKEN": "<YOUR_DOCUMENT_ENGINE_API_AUTH_TOKEN>",
"DOCUMENT_ENGINE_BASE_URL": "<DOCUMENT_ENGINE_BASE_URL>",
"DASHBOARD_PASSWORD": "<YOUR_DASHBOARD_PASSWORD>"
}
}
}
}Instalar Nutrient Document Engine MCP en VS Code
.vscode/mcp.json
{
"servers": {
"nutrient-document-engine-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@nutrient-sdk/document-engine-mcp-server"
],
"env": {
"DOCUMENT_ENGINE_API_AUTH_TOKEN": "<YOUR_DOCUMENT_ENGINE_API_AUTH_TOKEN>",
"DOCUMENT_ENGINE_BASE_URL": "<DOCUMENT_ENGINE_BASE_URL>",
"DASHBOARD_PASSWORD": "<YOUR_DASHBOARD_PASSWORD>"
}
}
}
}Instalar Nutrient Document Engine MCP en VS Code CLI
$ code --add-mcp '{"name":"nutrient-document-engine-mcp-server","type":"stdio","command":"npx","args":["-y","@nutrient-sdk/document-engine-mcp-server"],"env":{"DOCUMENT_ENGINE_API_AUTH_TOKEN":"<YOUR_DOCUMENT_ENGINE_API_AUTH_TOKEN>","DOCUMENT_ENGINE_BASE_URL":"<DOCUMENT_ENGINE_BASE_URL>","DASHBOARD_PASSWORD":"<YOUR_DASHBOARD_PASSWORD>"}}'Instalar Nutrient Document Engine MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"nutrient-document-engine-mcp-server": {
"command": "npx",
"args": [
"-y",
"@nutrient-sdk/document-engine-mcp-server"
],
"env": {
"DOCUMENT_ENGINE_API_AUTH_TOKEN": "<YOUR_DOCUMENT_ENGINE_API_AUTH_TOKEN>",
"DOCUMENT_ENGINE_BASE_URL": "<DOCUMENT_ENGINE_BASE_URL>",
"DASHBOARD_PASSWORD": "<YOUR_DASHBOARD_PASSWORD>"
}
}
}
}Instalar Nutrient Document Engine MCP en Codex
$ codex mcp add nutrient-document-engine-mcp-server --env 'DOCUMENT_ENGINE_API_AUTH_TOKEN=<YOUR_DOCUMENT_ENGINE_API_AUTH_TOKEN>' --env 'DOCUMENT_ENGINE_BASE_URL=<DOCUMENT_ENGINE_BASE_URL>' --env 'DASHBOARD_PASSWORD=<YOUR_DASHBOARD_PASSWORD>' -- npx -y @nutrient-sdk/document-engine-mcp-serverInstalar Nutrient Document Engine MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.nutrient-document-engine-mcp-server] command = "npx" args = ["-y", "@nutrient-sdk/document-engine-mcp-server"] [mcp_servers.nutrient-document-engine-mcp-server.env] DOCUMENT_ENGINE_API_AUTH_TOKEN = "<YOUR_DOCUMENT_ENGINE_API_AUTH_TOKEN>" DOCUMENT_ENGINE_BASE_URL = "<DOCUMENT_ENGINE_BASE_URL>" DASHBOARD_PASSWORD = "<YOUR_DASHBOARD_PASSWORD>"
Instalar Nutrient Document Engine MCP en Gemini CLI
$ gemini mcp add -s user -e 'DOCUMENT_ENGINE_API_AUTH_TOKEN=<YOUR_DOCUMENT_ENGINE_API_AUTH_TOKEN>' -e 'DOCUMENT_ENGINE_BASE_URL=<DOCUMENT_ENGINE_BASE_URL>' -e 'DASHBOARD_PASSWORD=<YOUR_DASHBOARD_PASSWORD>' nutrient-document-engine-mcp-server npx -- -y @nutrient-sdk/document-engine-mcp-serverInstalar Nutrient Document Engine MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"nutrient-document-engine-mcp-server": {
"command": "npx",
"args": [
"-y",
"@nutrient-sdk/document-engine-mcp-server"
],
"env": {
"DOCUMENT_ENGINE_API_AUTH_TOKEN": "<YOUR_DOCUMENT_ENGINE_API_AUTH_TOKEN>",
"DOCUMENT_ENGINE_BASE_URL": "<DOCUMENT_ENGINE_BASE_URL>",
"DASHBOARD_PASSWORD": "<YOUR_DASHBOARD_PASSWORD>"
}
}
}
}Configuración
DOCUMENT_ENGINE_API_AUTH_TOKENObligatorioSecretoAPI auth token for your Document Engine instance.
DOCUMENT_ENGINE_BASE_URLObligatorioBase URL of your Nutrient Document Engine instance (e.g. http://localhost:5000).
DASHBOARD_PASSWORDSecretoOptional: local status dashboard password.
DASHBOARD_PASSWORDDASHBOARD_USERNAMEDASHBOARD_USERNAMEOptional: enables the local status dashboard (Basic auth username).
DOCUMENT_ENGINE_API_AUTH_TOKENDOCUMENT_ENGINE_BASE_URLLOG_LEVELOptional log level (default info).
MCP_TRANSPORT
| Nombre | Descripción | Tipo |
|---|---|---|
| DOCUMENT_ENGINE_API_AUTH_TOKEN | API auth token for your Document Engine instance. | ObligatorioSecreto |
| DOCUMENT_ENGINE_BASE_URL | Base URL of your Nutrient Document Engine instance (e.g. http://localhost:5000). | Obligatorio |
| DASHBOARD_PASSWORD | Optional: local status dashboard password. | Secreto |
| DASHBOARD_PASSWORD | — | |
| DASHBOARD_USERNAME | — | |
| DASHBOARD_USERNAME | Optional: enables the local status dashboard (Basic auth username). | |
| DOCUMENT_ENGINE_API_AUTH_TOKEN | — | |
| DOCUMENT_ENGINE_BASE_URL | — | |
| LOG_LEVEL | Optional log level (default info). | |
| MCP_TRANSPORT | — |
Verificaciones automáticas
Ejecutado 13 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesiblepspdfkit/nutrient-document-engine-mcp-server is public and reachablegithub.com/pspdfkit/nutrient-document-engine-mcp-server ↗Aprobado
- El paquete indica este repositorio como su origen@nutrient-sdk/document-engine-mcp-server names pspdfkit/nutrient-document-engine-mcp-server as sourcenpmjs.com/package/@nutrient-sdk/document-engine-mcp-server ↗Aprobado
- Procedencia de la compilación (atestación de Sigstore)No build attestation published for this releaseNo verificado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-11-04github.com/pspdfkit/nutrient-document-engine-mcp-server ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo popular package one edit away from @nutrient-sdk/document-engine-mcp-serverAprobado
- No hay avisos críticos en el paquete ni en sus dependencias128 resolved dependencies checked; no critical advisoryosv.dev ↗Aprobado
- Sin instrucciones ocultas para el modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPNo verificado
README
Ver en GitHubNutrient 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.
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 22.x (22.23.4+), 24.x (24.22.1+), or 26.x (26.12.1+) - 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:
git clone https://github.com/PSPDFKit/nutrient-document-engine-mcp-server.git
cd nutrient-document-engine-mcp-server
docker-compose up -d
2. Connect Claude Desktop
Add this to your Claude Desktop config (Settings → Developer → Edit Config):
{
"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
- Open your web browser and go to http://localhost:5100/dashboard.
- Upload the documents you want to work with by using the drag-and-drop interface.
- 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.
# 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
- LangGraph Document Processing - Workflow examples for contract processing, form filling, and report generation.
- OpenAI Agents SDK Document Processing - Workflow examples for contract processing, form filling, and report generation.
- Document Chat Interface - Web application with React and LangGraph.
- Procurement AI Agent - An AI Agent written with Langgraph.js, that classifies and collates POs, invoices, and payment documents into groups and flags for human review
Documentation
- Configuration Guide - Environment variables, transport modes, dashboard.
- Features Reference - Detailed description of all document processing tools.
- Evaluation Framework - Testing and benchmarking tools.
Removing Evaluation Watermarks and Limitations
Document Engine runs in evaluation mode with limitations by default. To remove them:
- Contact Sales to purchase a license from Nutrient
- Configure your license by setting the
ACTIVATION_KEYenvironment variable in your Docker Compose configuration or Document Engine setup - 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.
Preguntas sobre Nutrient Document Engine MCP
¿Cómo agrego Nutrient Document Engine MCP a Claude Code?
Ejecuta claude mcp add --env 'DOCUMENT_ENGINE_API_AUTH_TOKEN=<YOUR_DOCUMENT_ENGINE_API_AUTH_TOKEN>' --env 'DOCUMENT_ENGINE_BASE_URL=<DOCUMENT_ENGINE_BASE_URL>' --env 'DASHBOARD_PASSWORD=<YOUR_DASHBOARD_PASSWORD>' nutrient-document-engine-mcp-server -- npx -y @nutrient-sdk/document-engine-mcp-server en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego Nutrient Document Engine MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Cómo instalo el Nutrient Document Engine MCP server?
Clona el repositorio, inicia el Document Engine con Docker Compose y luego apunta la configuración de tu Claude Desktop al comando npx con la URL y las credenciales de tu Document Engine. Reinicia el cliente para conectarte.
¿Puedo redactar datos sensibles como números de seguridad social con este servidor?
Sí, el servidor puede crear y aplicar redacciones utilizando patrones preestablecidos como SSN y tarjetas de crédito, o mediante regex personalizados.
¿El Nutrient Document Engine MCP server funciona con plataformas de IA distintas a Claude Desktop?
Sí, funciona con cualquier plataforma compatible con MCP, incluyendo LangGraph, APIs de OpenAI y agentes personalizados.
¿Es necesario un token de autenticación MCP HTTP?
Solo para hosts HTTP que no sean de loopback; en ese caso, el servidor se niega a iniciar sin un token. El transporte stdio por defecto nunca requiere uno.