ervice (DWS) Processor and Data Extraction APIs — enabling document creation, editing, conversion, digital signing, OCR, and redaction, plus structured data extraction (typed JSON with bounding boxes and confidence, or schema-guided field extraction with per-field citations) through natural language.
Nutrient DWS MCP Server
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
> [!IMPORTANT]
> **This local MCP server is no longer supported. Use Nutrient MCP instead.**
>
> Nutrient now hosts its MCP server at https://mcp.nutrient.io/mcp. Add that URL to your MCP client and sign in with your Nutrient account. There's nothing to install, no API key and no sandbox folder.
>
>
>
> In the Claude app, add https://mcp.nutrient.io/mcp as a custom connector. To switch, remove @nutrient-sdk/dws-mcp-server from your client config and add the URL. This repository stays up for reference only. It won't get new features or fixes.
**Give AI agents the power to generate, read, extract, process, and sign documents.**
Description
A Model Context Protocol (MCP) server that connects AI assistants to the Nutrient Document Web Service (DWS) Processor and Data Extraction APIs — enabling document creation, editing, conversion, digital signing, OCR, and redaction, plus structured data extraction (typed JSON with bounding boxes and confidence, or schema-guided field extraction with per-field citations) through natural language.
Features
- Local stdio MCP server for Claude Desktop and other MCP-compatible clients
- Browser-based OAuth on the first request that uses the Nutrient API, with optional API-key fallback for CI and headless environments
- Document conversion, OCR, redaction, watermarking, annotation flattening, and digital signing (Processor API)
- Data extraction (Data Extraction API): parse whole documents to Markdown or spatial JSON, then pull named fields into a JSON schema you define, with per-field citations. Four parse modes: text (1 credit/page, no OCR), structure (1.5), understand (9, the default), agentic (18, VLM)
- Sandbox-aware local file handling with explicit output paths
- Read-only account lookup for DWS credits and usage
What You Can Do
Once configured, you (or your AI agent) can process documents through natural language:
**You:** _"Merge report-q1.pdf and report-q2.pdf into a single document"_
**AI:** _"Done! I've merged both reports into combined-report.pdf (24 pages total)."_
**You:** _"Redact all social security numbers and email addresses from application.pdf"_
**AI:** _"I found and redacted 5 SSNs and 3 email addresses. The redacted version is saved as application-redacted.pdf."_
**You:** _"Digitally sign this contract with a visible signature on page 3"_
**AI:** _"I've applied a PAdES-compliant digital signature to contract.pdf. The signed document is saved as contract-signed.pdf."_
**You:** _"Convert this PDF to markdown"_
**AI:** _"Here's the markdown content extracted from your document..."_
**You:** _"OCR this scanned document in German and extract the text"_
**AI:** _"I've processed the scan with German OCR. Here's the extracted text..."_
**You:** _"Pull the vendor, invoice number, total, and due date out of invoice-0341.pdf, with citations"_
**AI:** _"Here are the four fields as JSON. Each value cites the page and bounding box it came from..."_
Installation
Install it from Claude Desktop Settings -> Extensions if you are using Claude Desktop. If you are developing locally, use the manual setup below.
The Claude Desktop MCPB extension defaults its sandbox directory to ~/Documents/Nutrient. You can change that directory in the extension settings. Clearing the field starts the server without sandbox restrictions, so file operations can use any path visible to your user account.
1. Create a Nutrient Account
Sign up for free at nutrient.io/api.
For local desktop use, the recommended path is to omit NUTRIENT_DWS_API_KEY and complete the browser sign-in flow on the first request that uses the Nutrient API. For CI, headless environments, or scripted setups, create an API key in the dashboard and set NUTRIENT_DWS_API_KEY.
2. Configure Your AI Client
Choose your platform and add the configuration:
Claude Desktop
Open Settings → Developer → Edit Config, then add:
**macOS:** ~/Library/Application Support/Claude/claude_desktop_config.json
**Windows:** %APPDATA%\Claude\claude_desktop_config.json
Cursor
Create .cursor/mcp.json in your project root:
Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
VS Code (GitHub Copilot)
Create .vscode/mcp.json in your project, or add the same server definition to your user mcp.json profile:
Other MCP Clients
Any MCP-compatible client can connect using stdio transport:
3. Restart Your AI Client
Restart the application to pick up the new MCP server configuration.
4. Start Processing Documents
Place documents in your sandbox directory and use explicit file names or paths in prompts. Explicit paths are safer and more reliable than vague file-browsing requests.