Nutrient Document Engine
A Model Context Protocol (MCP) server implementation exposes document processing capabilities through natural language, supporting both direct human interaction and AI agent tool calling.
What is Nutrient Document Engine?
Nutrient Document Engine is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to model context protocol (mcp) server implementation exposes document processing capabilities through natural language, supporting both direct human interaction and ai agent tool calling.
A Model Context Protocol (MCP) server implementation exposes document processing capabilities through natural language, supporting both direct human interaction and AI agent tool calling.
This server falls under the File Systems category on MCPgee, the world's largest MCP server directory with 33,000+ servers.
Features
- A Model Context Protocol (MCP) server implementation exposes
Use Cases
Maintainer
Works with
Installation
Manual Installation
npx nutrient-document-engineConfiguration
Configuration Details
claude_desktop_config.json
Performance
Response Metrics
Resource Usage
How to Set Up and Use Nutrient Document Engine
The Nutrient Document Engine MCP Server exposes PSPDFKit's Nutrient Document Engine capabilities through natural language, letting AI assistants and agents perform document operations including text extraction, redaction, annotation, watermarking, form filling, page splitting, and content search. It bridges the MCP protocol to a locally running Nutrient Document Engine instance via Docker, supporting both direct human interaction and programmatic tool calling by AI agents.
Prerequisites
- Docker and Docker Compose installed for running Nutrient Document Engine
- Node.js 18 or higher for the npx-based MCP server
- A Nutrient Document Engine API auth token (DOCUMENT_ENGINE_API_AUTH_TOKEN)
- Dashboard credentials (DASHBOARD_USERNAME and DASHBOARD_PASSWORD)
- An MCP-compatible client such as Claude Desktop or Claude Code
Clone the repository
Clone the Nutrient Document Engine MCP server repository.
git clone https://github.com/PSPDFKit/nutrient-document-engine-mcp-server.git
cd nutrient-document-engine-mcp-serverStart Nutrient Document Engine with Docker Compose
Launch the backend Document Engine service. It will be available at http://localhost:5000 by default.
docker-compose up -dVerify the Document Engine is running
Check that the service is healthy before connecting the MCP server.
curl http://localhost:5000/healthcheckGather configuration values
Note your DASHBOARD_USERNAME, DASHBOARD_PASSWORD, DOCUMENT_ENGINE_API_AUTH_TOKEN from your Docker Compose environment file or Nutrient dashboard. The DOCUMENT_ENGINE_BASE_URL defaults to http://localhost:5000.
Configure your MCP client
Add the server to your claude_desktop_config.json with the required environment variables. The server runs via npx and connects to the running Document Engine.
Nutrient Document Engine Examples
Client configuration
Add this to your claude_desktop_config.json to connect Claude to your Nutrient Document Engine instance.
{
"mcpServers": {
"nutrient-document-engine": {
"command": "npx",
"args": ["-y", "@nutrient-sdk/document-engine-mcp-server"],
"env": {
"DOCUMENT_ENGINE_BASE_URL": "http://localhost:5000",
"DOCUMENT_ENGINE_API_AUTH_TOKEN": "your_api_auth_token",
"DASHBOARD_USERNAME": "your_dashboard_username",
"DASHBOARD_PASSWORD": "your_dashboard_password"
}
}
}
}Prompts to try
Use these prompts in Claude to process documents through Nutrient Document Engine.
- "What documents do I have available in the document engine?"
- "Extract all text from the invoice document"
- "Redact all social security numbers from the tax_form.pdf document"
- "Add a 'CONFIDENTIAL' watermark to the contract document"
- "Split the report into individual pages and list the sections"
- "Fill in the name field on the registration form with 'John Doe'"Troubleshooting Nutrient Document Engine
Connection refused when the MCP server tries to reach the Document Engine
Ensure the Docker container is running with `docker-compose ps`. If DOCUMENT_ENGINE_BASE_URL is set to localhost inside a Docker network, it may need to point to the Docker host IP instead (e.g., http://host.docker.internal:5000 on macOS/Windows).
API auth token errors (401 Unauthorized)
Verify that DOCUMENT_ENGINE_API_AUTH_TOKEN matches the token configured in your Docker Compose environment for the Document Engine. Check the docker-compose.yml for the API_AUTH_TOKEN variable and ensure they match exactly.
Document operations return evaluation watermarks
Nutrient Document Engine runs in evaluation mode without an activation key. Provide your license ACTIVATION_KEY in the environment to remove evaluation watermarks and unlock full functionality.
Frequently Asked Questions about Nutrient Document Engine
What is Nutrient Document Engine?
Nutrient Document Engine is a Model Context Protocol (MCP) server that model context protocol (mcp) server implementation exposes document processing capabilities through natural language, supporting both direct human interaction and ai agent tool calling. It connects AI assistants to external tools and data sources through a standardized interface.
How do I install Nutrient Document Engine?
Follow the installation instructions on the Nutrient Document Engine GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.
Which AI clients work with Nutrient Document Engine?
Nutrient Document Engine works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.
Is Nutrient Document Engine free to use?
Yes, Nutrient Document Engine is open source and available under the MIT license. You can use it freely in both personal and commercial projects.
Nutrient Document Engine Alternatives — Similar File Systems Servers
Looking for alternatives to Nutrient Document Engine? Here are other popular file systems servers you can use with Claude, Cursor, and VS Code.
Electerm
★ 14.1k📻Terminal/ssh/sftp/ftp/telnet/serialport/RDP/VNC/Spice client(linux, mac, win)
Plik
★ 1.8kPlik is a temporary file upload system (Wetransfer like) in Go.
Kordoc
★ 957An MCP server that parses South Korean document formats like HWP, HWPX, and PDF into Markdown. It features specialized table reconstruction and security-hardened extraction optimized for administrative and public institution files.
macOS Automator
★ 801A Model Context Protocol server that enables execution of AppleScript and JavaScript for Automation scripts on macOS, allowing programmatic control of applications and system functions through a rich knowledge base of pre-defined scripts.
PDF Reader
★ 723Enables reading, searching, and metadata extraction from PDF files without loading the entire content into the context window. It provides efficient tools for text cleaning, page-specific extraction, and context-aware search results.
Filesystem MCP Server
★ 643Provides comprehensive filesystem operations (read, write, list, create, delete, move files and directories) through the Model Context Protocol with Streamable HTTP transport and built-in security through configurable root directory restrictions.
Browse More File Systems MCP Servers
Explore all file systems servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.
Set Up Nutrient Document Engine in Your Editor
Choose your AI client for step-by-step setup instructions.
Quick Config Preview
Add this to your claude_desktop_config.json or .cursor/mcp.json
Ready to use Nutrient Document Engine?
Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.