Claude Nutrient DWS connectorWhat Claude does to your documents through the Nutrient DWS API.
The Claude Nutrient DWS connector exposes 5 tools. 2 read, 3 write processed files, 0 stay undocumented. Below: what Claude converts, signs and redacts from your computer, what travels to Nutrient's API, and the folder that fences it all in.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when a stack of documents needs processing
Nutrient DWS is a desktop extension: it runs on your machine inside Claude Desktop and reads files from a folder you pick. When you ask for a conversion, a signature or a redaction, it sends the document to Nutrient's processing API and writes the result back to your disk, at the path you gave.
Transform a file without dedicated software. document_processor handles conversions, OCR, watermarks, rotation and annotation flattening. One tool, several kinds of jobs, each sent to Nutrient's API, with the result written back to a local output path.
Sign a PDF. document_signer applies a CMS / PKCS#7 or CAdES digital signature, visible or invisible, and saves the signed copy at the output path you give it.
Remove what shouldn't travel. ai_redactor finds and permanently strips names, addresses, SSNs, emails or custom criteria you define for the job.
Two tools only read: check_credits looks up your DWS credit balance and sandbox_file_tree lists the files in the allowed folder. What Claude won't do: reach outside that folder when one is configured, or start a job on its own without you asking. A pipeline that processes every new file dropped in a folder belongs to an automation platform, covered in the Integrations hub.
The vocabulary, in one minute
Five words to know before installing Nutrient DWS in Claude.
- Connector
- The link you install once between Claude and a service, here as a local extension, so Claude can use it while answering.
- Tool
- One named capability the connector opens to Claude. Claude picks which to call; the directory sheet lists them all.
- Authorization
- The service's sign-in screen where you grant access. For Nutrient, it opens in your browser on the first API call.
- Approval
- The confirmation Claude waits for in the chat before an action that produces or changes something on your behalf.
- MCP
- The shared standard connectors are built on: it lets an assistant drive an outside service, here Nutrient's API.
Install the Claude Nutrient DWS connector in three steps
- 01
Find Nutrient DWS
In Claude Desktop's settings, open Customize, then Connectors, and look for Nutrient DWS. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization first.
- 02
Start the connection
Click Connect on its row. Nutrient's sign-in window opens in your browser the first time a job goes through its API. If the link breaks, Disconnect and a fresh connection bring it back.
- 03
Review the access
Read Nutrient's authorization screen before you accept: Nutrient, not Claude, sets what the access covers. You can withdraw it later from Claude or from your Nutrient account.
The 5 tools in the Claude Nutrient DWS connector
Nutrient DWS gives Claude 5 tools: 2 that read your account, 3 that change something in it.
Two tools consult, three produce a processed file. Names stay exactly as Claude shows them.
- 2 read
- 3 write
What Claude reads (2)
2 toolsA balance and a file list, with nothing sent off for processing.
check_credits
Checks your Nutrient DWS account for the current credit balance and usage. Nutrient notes that no document content gets uploaded for this lookup.
sandbox_file_tree
Shows Claude which files sit in the extension's allowed folder, read-only and without uploading anything to Nutrient.
What Claude produces (3)
3 toolsThree jobs that send the document to Nutrient and write a result to your disk.
document_processor
Approval: see the ruleConverts a file, runs OCR, adds a watermark, rotates pages or flattens annotations, then saves the output. The document goes to Nutrient's API for the operation.
document_signer
Approval: see the ruleSigns a PDF with a CMS / PKCS#7 or CAdES signature, using a visible or invisible appearance, and writes the signed file where you asked.
ai_redactor
Approval: see the ruleDetects and permanently removes sensitive content from a document: names, addresses, SSNs, emails, or custom criteria you set.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before every action it takes on your behalf, right when it matters.
For Nutrient DWS, no source describes a confirmation specific to converting, signing or redacting, so the general rule covers all three jobs. Claude acts with your rights and nothing more. On Team and Enterprise, workspace owners decide whether a member may let some actions through without a fresh prompt, and they can limit a connector for the whole organization, for instance by keeping reads and closing writes.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan: for Nutrient DWS, that answer isn't published anywhere.
The general rule is public: desktop extensions like this one install on Claude Desktop, which is open to all users. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before members connect. DWS credits are managed on Nutrient's side. For the current state, the Nutrient DWS sheet in the directory is the reference.
Where the Nutrient DWS connector stops
A connector isn't an automation: Claude only processes a document while it is answering you, never when a file lands.
The directory badge isn't a security audit, and Anthropic doesn't vouch for how a publisher's tools behave. Only Nutrient documents this connector, through its project page and the extension manifest. Those sources list further tools, field extraction among them, that aren't on the directory sheet and are left out here. The limits below come from those pages. More connectors the team has reviewed sit in the Claude connectors hub.
Need help connecting Nutrient DWS to Claude?
A person reads every message.