PILOT COMPLETE
We built Nutrient PDF Editor for Claude Cowork to test one question: What does an agent do with a real, interactive PDF surface? We have the answer we needed, and the pilot is now complete. PDF automation from Claude continues in the Nutrient DWS MCP Server, which is a supported product.
WHAT THIS MEANS
Nutrient PDF Editor for Claude Cowork receives no further updates. Remove it in Claude Desktop under Settings → Extensions.
The editor ran entirely on the local machine and never uploaded a file. Every PDF edited through it is an ordinary PDF on disk, with real annotations, form data, and applied redactions. There’s nothing to export and nothing to recover.
The PDF engine behind the pilot is Nutrient Web SDK, which enterprise teams run in production. It stays fully available, as does every other Nutrient product.
WHERE TO GO NEXT
The DWS MCP Server connects Claude — or any MCP client — to the Nutrient DWS APIs. The document work is described in plain language, and the server runs it. It’s a supported product, not a pilot.
Convert, merge, split, OCR, extract data, fill forms, redact, watermark, and digitally sign — driven by prompt, on any document the server points to.
Install it as a Claude Desktop extension, or run it over stdio in another MCP client, in CI, or in a container. One server serves all of them.
The server is published on GitHub with setup instructions, and the getting started guide walks through the first run end to end.
It was scoped as a pilot from the start. We wanted to see how an agent behaves when handed a real, interactive PDF editing surface instead of a file to process. We have that answer, so we completed the pilot rather than carrying an unsupported product.
Remove it in Claude Desktop under Settings → Extensions. It gets no further updates and it isn’t supported. PDFs edited through it are unaffected — they’re ordinary files on disk, and every edit was written into them at the time it was made.
Yes, through the Nutrient DWS MCP Server. It exposes PDF operations — conversion, OCR, data extraction, form filling, redaction, watermarking, and digital signing — as MCP tools that Claude can call. It’s a different shape of tool: The work runs against the DWS APIs instead of in a viewer on screen.
The Claude Cowork extension put a visual PDF editor in the chat panel, running locally, so the user and Claude could take turns on the same open document. The DWS MCP Server has no viewer. It gives Claude a set of document operations to run against the Nutrient DWS APIs, which fits automation and MCP clients beyond Claude Desktop.
Follow the getting started guide. It can be installed as a Claude Desktop extension, or run over stdio in another MCP client. The source and the release notes are on GitHub.
We have no plan to bring it back. For an interactive PDF viewer and editor embedded in a product, that’s what Nutrient Web SDK is for — the same engine the pilot ran on. Contact us for use cases that need the agent and the viewer together.
The repository stays on GitHub as a record of the pilot. It isn’t maintained.
