The PDF Editor for Claude Cowork pilot is 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. To keep working on documents in Claude, add Nutrient MCP as a connector. It’s a supported product, not a pilot.

Explore the Nutrient MCP server See the setup steps

WHAT THIS MEANS

What changes, and what doesn’t

The extension is no longer supported

Nutrient PDF Editor for Claude Cowork receives no further updates. Remove it in Claude Desktop under Settings → Extensions.

Documents are unaffected

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 engine is unchanged

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

Nutrient MCP

Nutrient MCP brings Nutrient’s document tools to Claude, Claude Code, and Codex. Describe the document work in plain language, and the server does it.

Get started

Extraction and processing in one server

Extract data, parse to Markdown, classify, convert, OCR, merge, watermark, sign, and redact, all driven by prompt.

Nothing to install

In Claude, add one URL as a custom connector and sign in with your Nutrient account. No extension, no package, and no API key.

Same credits as the API

The server uses the credits on your Nutrient account at the same credit rates as the API.

Frequently asked questions

Why is the pilot complete?

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.

I already installed the extension. What should I do?

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.

Can I still work on PDFs from Claude?

Yes. Add Nutrient MCP to Claude as a connector, and Claude can extract data, convert, OCR, redact, watermark, and sign documents for you. Results show up as cards in the chat, and you can open a document next to its extracted values to check them.

What is the difference between the two?

The Cowork extension was a PDF editor that ran on your computer, so you and Claude could take turns on the same open document. Nutrient MCP works in Nutrient’s cloud instead: Claude sends it a document, Nutrient does the work, and the result comes back to the chat. It needs a Nutrient account, uses credits, and doesn’t let you edit pages by hand.

How do I connect Nutrient MCP?

There’s nothing to install. In Claude, go to Settings → Connectors, add a custom connector with https://mcp.nutrient.io/mcp, and sign in with your Nutrient account. For Claude Code and Codex, the setup steps show the command.

Will the viewer come back?

The editor won’t come back. In Claude, Nutrient MCP can open a document in a viewer so you can check extracted values, but you can’t edit pages by hand in it. For a full viewer and editor inside your own product, use Nutrient Web SDK, the same engine the pilot ran on. Contact us for use cases that need the agent and the viewer together.

Where did the extension source go?

The repository stays on GitHub as a record of the pilot. It isn’t maintained.