What is the key difference between Nutrient Dws MCP Server and Fetch?

Nutrient Dws MCP Server belongs to the Other Tools and Integrations category with local stdio execution, while Fetch belongs to the Other Tools and Integrations category with local stdio execution.

How do I install Nutrient Dws MCP Server or Fetch in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Nutrient Dws MCP Server and Fetch free or paid?

Nutrient Dws MCP Server operates under a Free / Open Source model (OAuth 2.0). Fetch operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Nutrient Dws MCP Server lists 8 tools with 2 views and 70 GitHub stars. Fetch lists 4 tools with 2 views and 90,185 GitHub stars.

Can I use both Nutrient Dws MCP Server and Fetch together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Nutrient Dws MCP Server vs Fetch

In-depth architectural comparison of the Nutrient Dws MCP Server and Fetch MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Nutrient Dws MCP Server

Other Tools and Integrations · Local stdio

Quality: 64/100 (Good) | Auth: OAuth 2.0

Fetch

Other Tools and Integrations · Local stdio

Quality: 75/100 (Great) | Auth: No auth required

Verdict Summary: Choose Nutrient Dws MCP Server if you need specialized Other Tools and Integrations tools running via a local process. Choose Fetch if your workspace requires Other Tools and Integrations integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Nutrient Dws MCP Server when:

You need dedicated capabilities in the Other Tools and Integrations domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: SANDBOX_PATH, NUTRIENT_DWS_API_KEY.
Primary tools included: document_processor, parse_document, extract_fields.

Explore Nutrient Dws MCP Server Details

Choose Fetch when:

You need dedicated capabilities in the Other Tools and Integrations domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Fetches web content over HTTP, Converts web pages for efficient LLM usage, Reference implementation demonstrating MCP SDK usage.

Feature & Specification Comparison

Specification	Nutrient Dws MCP Server PSPDFKit Other Tools and Integrations	Fetch VerifiedOther Tools and Integrations
Summary	MCP server for the Nutrient DWS Processor API. Convert, merge, redact, sign, OCR, watermark, and extract data from PDFs and Office documents via natural language. Works with Claude Desktop, LangGraph, and OpenAI Agents.	Web content fetching and conversion for efficient LLM usage.
Category & Scope

Tools & Capabilities Breakdown

Nutrient Dws MCP Server Tools (8)

document_processor

Document processing for conversions, OCR, watermarking, rotation, annotation flattening, and redaction workflows

parse_document

Structured data extraction (DWS Data Extraction API): typed JSON elements with bounding boxes and confidence, or whole-document Markdown

extract_fields

Schema-guided field extraction (DWS Data Extraction API): pulls specific named fields into a JSON shape you define, with per-field citations

document_signer

PDF signing with CMS / PKCS#7 and CAdES signatures plus visible or invisible appearance options

ai_redactor

AI redaction for detecting and permanently removing sensitive content such as names, addresses, SSNs, emails, and custom criteria

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Nutrient Dws MCP Server Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "pspdfkit-nutrient-dws-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@nutrient-sdk/dws-mcp-server"
      ],
      "env": {
        "SANDBOX_PATH": "YOUR_SANDBOX_PATH_HERE",
        "NUTRIENT_DWS_API_KEY": "YOUR_NUTRIENT_DWS_API_KEY_HERE"
      }
    }
  }
}

Fetch Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "fetch": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ]
    }
  }
}

Frequently Asked Questions

Nutrient Dws MCP Server is categorized under Other Tools and Integrations and uses a local stdio subprocess. In contrast, Fetch belongs to Other Tools and Integrations using local stdio subprocess. Select Nutrient Dws MCP Server when you need capabilities focused on other tools and integrations and Fetch when you require tools for other tools and integrations.

More alternatives to Nutrient Dws MCP Server More alternatives to Fetch Other Tools and Integrations category hub Canonical compare URL