Search
Model Context Protocol
Four Nutrient MCP connections are available. Use Nutrient MCP to extract data from documents and process them. Use Document Engine or Workflow to manage documents where they run, and Web SDK docs MCP when building with the Web SDK.
Nutrient MCP
Hosted server for data extraction and document processing. Nothing to install.
Document Engine MCP
Local server connected to your Document Engine instance.
Workflow MCP
In-product connection for Workflow 8.20 and later.
Web SDK docs MCP
Local, keyless documentation server for AI coding agents building with the Web SDK.
Hosted
Nutrient MCP runs at https://mcp.nutrient.io/mcp. Add the URL to your agent and sign in with your Nutrient account. Nothing to install, and no API key.
https://mcp.nutrient.io/mcp Hosted by Nutrient.
Your Nutrient account, in the browser. Requests use your organization’s access and credits.
Nothing to install, and no API key.
Claude, Claude Code, Codex, and other MCP clients.
Connect
Add the server. Then sign in with your Nutrient account in the browser.
Go to Settings → Connectors, add a custom connector, and paste this URL.
https://mcp.nutrient.io/mcpClick 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/mcpRun /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 nutrientThe login command opens your browser. Sign in with your Nutrient account.
Add this URL as a remote (HTTP) MCP server.
https://mcp.nutrient.io/mcpSign in with your Nutrient account when the client asks.
Self-hosted
Local server connected to your Document Engine instance.
Connects an MCP client to your Document Engine instance.
Locally, against your own Document Engine instance.
The API authentication token for your instance.
@nutrient-sdk/document-engine-mcp-server MCP clients.
Set up
Configure the package with the base URL and API authentication token for your instance. Read the release post for the product announcement.
Connects an MCP client to your Document Engine instance.
@nutrient-sdk/document-engine-mcp-serverThe base URL of your Document Engine instance.
DOCUMENT_ENGINE_BASE_URLThe API authentication token for that instance.
DOCUMENT_ENGINE_API_AUTH_TOKENIn-product
In-product connection for Workflow 8.20 and later.
Connects desktop AI apps to your Workflow environment.
In-product, in Workflow 8.20 and later.
API key. OAuth for web-based AI apps is planned.
Nothing to install. Connect from your Workflow environment.
Claude Desktop and other desktop apps that accept API keys.
Set up
Workflow MCP is available in-product for Workflow 8.20 and later. From your Workflow environment, connect Claude Desktop and other desktop apps that accept API keys.
Local
Local, keyless documentation server for AI coding agents building with the Web SDK.
On-demand access to Web SDK documentation, API type declarations, guides, examples, and the changelog.
Locally, over stdio.
None. No account or API key.
@nutrient-sdk/viewer-mcp Claude Code, Cursor, VS Code, and other AI coding agents.
Set up
Add the package to your coding agent. It runs locally over stdio, so there’s no account or API key to set up.
claude mcp add Nutrient -- npx @nutrient-sdk/viewer-mcp{
"mcpServers": {
"Nutrient": {
"command": "npx",
"args": ["@nutrient-sdk/viewer-mcp"]
}
}
}Use this standard MCP configuration shape for Cursor, VS Code, and other compatible clients.