Add one URL to Claude, Claude Code, or Codex and sign in with your Nutrient account. Your agent can then extract data from documents, convert them, sign them, and redact them. Nothing to install.
CONNECT
Add the server. Then sign in with your Nutrient account in the browser. No API key goes into a configuration file. Your agent may ask you to approve some steps. For Document Engine, Workflow, and Web SDK docs MCP, see all Nutrient MCP servers.
Go to Settings → Connectors, add a custom connector, and paste this URL.
https://mcp.nutrient.io/mcp Click Connect and sign in with your Nutrient account in the browser.
To work on a file, attach it to your message.
Run this command in your terminal.
claude mcp add --transport http --scope user nutrient https://mcp.nutrient.io/mcp Run /mcp in Claude Code, choose nutrient, and select Authenticate. Sign in with your Nutrient account in the browser.
Run this command in your terminal.
codex mcp add nutrient --url https://mcp.nutrient.io/mcp && codex mcp login nutrient The login command opens your browser. Sign in with your Nutrient account.
Add this URL as a remote (HTTP) MCP server.
https://mcp.nutrient.io/mcp Sign in with your Nutrient account when the client asks.
Read documents and act on them in one server.
Extract fields
Describe the fields you need in plain words. Values come back with citations and confidence. No schema to write.
Learn moreParse to Markdown
Turn PDFs, scans, and images into Markdown and tables your agent can read.
Learn moreConvert and edit
Convert Office files to PDF, run OCR, merge, rotate, watermark, and create PDF/A or PDF/UA files.
Learn moreEXAMPLES
After you connect, paste a prompt into Claude, Claude Code, or Codex. No scripts or custom code.
Extract the invoice number, date, supplier, net amount, tax, and total from every invoice in ./invoices and save them as one CSV. Get the policy number, claimant name, and claim amount from claim.pdf, and show where each value comes from. Sort the files in ./inbox into invoices, contracts, and other documents. Turn report.pdf into Markdown with tables. Convert contract.docx to PDF, add a CONFIDENTIAL watermark, and sign it. Redact all names, email addresses, and phone numbers in statement.pdf. Connect once
Your agent calls Nutrient MCP. You sign in once with your Nutrient account.
Send the document
Your agent sends the document to Nutrient. Nothing to set up.
Get the result
Nutrient processes the document and returns the result to your agent.
Security and data
OAuth sign-in
You sign in with your Nutrient account. No API keys in configuration files.
Access follows your organization
Requests run under your Nutrient organization and use its credits.
You control what’s kept
Nutrient MCP itself keeps nothing. Extraction runs are saved to your run history, where you can review or delete them, and uploaded files expire after 24 hours.
How Nutrient handles your dataClaude and Claude Code
In the Claude app, add the URL as a custom connector. In Claude Code, add it with one command.
Codex
Add the server and sign in with one command.
Other MCP clients
Clients that support remote MCP servers, using the same URL and sign-in.
Nutrient MCP is a hosted Model Context Protocol (MCP) server at https://mcp.nutrient.io/mcp. Add it to Claude, Claude Code, or Codex and sign in with your Nutrient account. Your agent can then extract data from documents, parse them to Markdown, classify them, convert and edit them, sign them, and redact them. There’s nothing to install.
Model Context Protocol (MCP) is an open standard for connecting AI applications to outside tools. An MCP client, such as Claude Code or Codex, connects to an MCP server, and the model working in that client can then use the server’s tools to do the work.
Nutrient MCP is tested with Claude, Claude Code, and Codex, in their apps and in the terminal. Other MCP clients that support remote servers can use the same URL and sign-in.
No. You sign in with your Nutrient account in the browser when you connect. There’s no API key to copy into a configuration file.
Your agent sends the file to Nutrient as part of the task. In the Claude app, just attach the file to your message. There’s no folder to configure and nothing to upload by hand.
PDFs, scans and images, and Office documents, up to 25 MB per file. It’s the same list the Data Extraction and Processor APIs accept. See the supported file types.
Nutrient MCP uses the credits on your Nutrient account at the same credit rates as the API. There’s no separate fee for MCP. The free plans include 5,000 Data Extraction API credits and 50 Processor API credits a month. On the free Processor plan, processed files carry a “For Evaluation Purposes Only” watermark until you turn on pay-as-you-go or upgrade. See Data Extraction pricing and Processor pricing.
It depends on the operation and the number of pages, at the same credit rates as the API. To get the best results from scans and complex layouts, the server reads documents in agentic mode by default, which uses 18 credits a page. For simple digital PDFs, ask your agent to use a lighter mode. Your agent can also check your remaining credits at any time. See the Data Extraction credit rates and Processor credits per tool.
Yes, in your Nutrient account. Nutrient MCP itself keeps nothing, but each extraction run saves the document and its results to your run history, where they stay until you delete them. Files your agent uploads expire after 24 hours. If you open a result in the document viewer in Claude, that copy is also kept until you delete it. See how Nutrient handles your data.
Nutrient MCP uses the same Data Extraction and Processor APIs. The APIs are for code you write. MCP lets your agent call the same operations from a prompt, without code.
No. The local MCP server is no longer supported. To switch, remove it from your MCP client and add https://mcp.nutrient.io/mcp instead. You don’t need an API key or a sandbox folder.