Nutrient DWS MCP Server

Created By
PSPDFKita year ago
A Model Context Protocol (MCP) server implementation that integrates with the Nutrient Document Web Service (DWS) Processor API, providing powerful PDF processing capabilities for AI assistants.
Overview

What is Nutrient DWS MCP Server?

Nutrient DWS MCP Server is a Model Context Protocol (MCP) server that integrates with the Nutrient Document Web Service (DWS) Processor API, providing advanced PDF processing capabilities for AI assistants.

How to use Nutrient DWS MCP Server?

To use the server, you need to sign up for a Nutrient DWS API key, install Node.js, and configure the server with Claude Desktop. After setting up, you can process documents by instructing the AI assistant to perform various operations.

Key features of Nutrient DWS MCP Server?

  • Document creation: Merge PDFs, Office docs, and images.
  • Editing: Watermark, rotate, flatten, redact, and more.
  • Format conversion: Support for PDF ⇄ DOCX and images.
  • Digital signing: Add compliant digital signatures.
  • Data extraction: Extract text, tables, or structured content.
  • Security: Redaction presets and password protection.
  • Advanced OCR: Multi-language and image recognition.
  • Optimization: Compress files without quality loss.

Use cases of Nutrient DWS MCP Server?

  1. Automating document workflows for AI assistants.
  2. Enhancing document security through redaction and digital signing.
  3. Converting and editing documents in various formats.

FAQ from Nutrient DWS MCP Server?

  • What platforms does it support?

    Currently, it supports macOS and Windows, with potential for Linux in the future.

  • Is there a sandbox mode?

    Yes, it has a sandbox mode for enhanced security, restricting file operations to a specific directory.

  • How do I process documents?

    You can instruct the AI assistant with commands like "redact all PII from secret.pdf" or "merge documents".

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
PSPDFKit
Star
9
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago