Nutrient DWS MCP Server

What does “Nutrient DWS” MCP Server do?

The Nutrient DWS MCP Server is a Model Context Protocol (MCP) server implementation that connects AI assistants with the Nutrient Document Web Service (DWS) Processor API. It provides advanced PDF processing capabilities, empowering AI tools and agents to perform operations such as digital signing, document generation, editing, OCR, watermarking, redaction, and more. By integrating this server, developers can enable their AI workflows to interact programmatically with complex document workflows, automating and streamlining processes that involve PDF manipulation and management. This integration enhances development workflows by bridging AI assistants and external document-processing APIs, making it possible to build sophisticated, document-centric automation tasks.

List of Prompts

No prompt templates were mentioned in the available repository files or documentation.

List of Resources

No explicit list of MCP resources was found in the repository or documentation.

List of Tools

No direct list of tools (such as those exposed in a server.py or similar) could be found in the repository or documentation. However, features mentioned include:

• Digital signing
• Document generation
• Document editing
• OCR (Optical Character Recognition)
• Watermarking
• Redaction

Use Cases of this MCP Server

• Automated PDF Signing: Enable AI agents to digitally sign documents at scale, streamlining signature workflows for legal, HR, or sales teams.
• Document Generation: Automatically create PDF documents from templates or dynamic data, improving efficiency in reporting and contract generation.
• PDF Editing and Annotation: Allow virtual assistants to modify documents, add comments, or update content as part of review cycles.
• OCR and Text Extraction: Use AI to ingest scanned documents and extract readable text for downstream analysis or archiving.
• Watermarking and Redaction: Ensure document confidentiality and intellectual property protection by programmatically adding watermarks or redacting sensitive information.

How to set it up

Windsurf

1. Ensure you have Node.js and npm installed.
2. Locate the MCP server configuration section in your Windsurf settings.
3. Add the Nutrient DWS MCP Server with the package: @nutrient-sdk/dws-mcp-server@latest.
4. Save your configuration and restart Windsurf.
5. Verify the server is running and accessible.

Example JSON configuration:

{
  "mcpServers": {
    "nutrient-dws-mcp": {
      "command": "npx",
      "args": ["@nutrient-sdk/dws-mcp-server@latest"]
    }
  }
}

Securing API Keys: Use environment variables in your configuration.

{
  "env": {
    "NUTRIENT_DWS_API_KEY": "your-api-key-here"
  },
  "inputs": {}
}

Claude

1. Confirm Node.js and npm are installed on your system.
2. Find the MCP configuration file for Claude.
3. Add the Nutrient DWS MCP Server as a new MCP server entry.
4. Save the configuration and restart Claude.
5. Check the server status within Claude’s interface.

Example JSON configuration:

{
  "mcpServers": {
    "nutrient-dws-mcp": {
      "command": "npx",
      "args": ["@nutrient-sdk/dws-mcp-server@latest"]
    }
  }
}

Securing API Keys:

{
  "env": {
    "NUTRIENT_DWS_API_KEY": "your-api-key-here"
  }
}

Cursor

1. Install Node.js and npm if not already available.
2. Open the Cursor MCP server settings.
3. Add the Nutrient DWS MCP Server as a new server.
4. Restart Cursor to apply changes.
5. Confirm integration by running a test command.

Example JSON configuration:

{
  "mcpServers": {
    "nutrient-dws-mcp": {
      "command": "npx",
      "args": ["@nutrient-sdk/dws-mcp-server@latest"]
    }
  }
}

Securing API Keys:

{
  "env": {
    "NUTRIENT_DWS_API_KEY": "your-api-key-here"
  }
}

Cline

1. Ensure Node.js and npm are installed.
2. Locate Cline’s configuration file for MCP servers.
3. Add the Nutrient DWS MCP Server using the provided package name.
4. Save the configuration and restart Cline.
5. Verify the server by checking logs or running a sample action.

Example JSON configuration:

{
  "mcpServers": {
    "nutrient-dws-mcp": {
      "command": "npx",
      "args": ["@nutrient-sdk/dws-mcp-server@latest"]
    }
  }
}

Securing API Keys:

{
  "env": {
    "NUTRIENT_DWS_API_KEY": "your-api-key-here"
  }
}

How to use this MCP inside flows

Using MCP in FlowHunt

To integrate MCP servers into your FlowHunt workflow, start by adding the MCP component to your flow and connecting it to your AI agent:

Click on the MCP component to open the configuration panel. In the system MCP configuration section, insert your MCP server details using this JSON format:

{
  "nutrient-dws-mcp": {
    "transport": "streamable_http",
    "url": "https://yourmcpserver.example/pathtothemcp/url"
  }
}

Once configured, the AI agent is now able to use this MCP as a tool with access to all its functions and capabilities. Remember to change “nutrient-dws-mcp” to whatever the actual name of your MCP server is and replace the URL with your own MCP server URL.

Overview

Our opinion

The Nutrient DWS MCP Server provides a solid foundation for AI-powered document workflows, but the lack of explicit prompts, resources, and tool definitions in the documentation limits its immediate utility for developers seeking quick onboarding. The repository is open source with a permissive license and has modest community engagement.

MCP Score

Rating: 4/10

While the repository is functional and provides clear setup instructions, the absence of detailed prompt templates, resources, and formal tool definitions lowers its usability and developer friendliness. It’s a strong start for those already familiar with the Nutrient DWS API, but more documentation and examples would increase its score significantly.