Nutrient DWS MCP Server
Related Servers
Alternatives to Nutrient DWS MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityNot gradedmaintenanceA Model Context Protocol server that extracts and processes content from PDF documents, providing text extraction, metadata retrieval, page-level processing, and PDF validation capabilities.41-
- AlicenseCqualityDmaintenanceA Model Context Protocol server for enterprise-grade document automation, enabling AI assistants to create, read, manipulate, and analyze Microsoft Word documents programmatically.541MIT
- AlicenseCqualityFmaintenanceA Model Context Protocol server that enables AI assistants to create, read, edit, and format Microsoft Word documents through standardized tools and resources.5417,843 PyPI2,110MIT
- AlicenseAqualityCmaintenanceA Model Context Protocol server that enables the extraction of text, metadata, and embedded images from PDF files. It provides tools for searching text with context, reading specific pages, and counting total pages within a document.714 npm1MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides document analysis capabilities to LLM applications, including extraction, chunking, summarization, and semantic search for PDF, DOCX, and plaintext documents.-
- FlicenseAqualityDmaintenanceA Model Context Protocol server that enables AI assistants to read PDF files, extract text, retrieve metadata, read specific pages, and search within PDFs.45-
TDQS
Scored across 7 tools
Most tools have clearly distinct purposes: signing, processing, redaction, parsing, field extraction, credit checking, and file browsing. However, document_processor and parse_document both handle document transformation/extraction, and their overlap is only partially clarified by the cross-reference in document_processor.
Tool names use a consistent pattern of noun-based verbs (document_signer, document_processor, ai_redactor) and clear action verbs (check_credits, parse_document, extract_fields). One exception is sandbox_file_tree, which describes a resource rather than an action, but it remains readable and doesn't break the overall pattern.
Seven tools is well within the ideal 3-15 range. Each tool addresses a distinct capability (signing, processing, redaction, extraction, field extraction, credit checking, sandbox browsing) without redundancy, making the set appropriately scoped for the server's document workflow purpose.
The server covers a comprehensive document lifecycle: signing, processing, redaction, parsing, and field extraction, plus account management and file access. Minor gaps exist—such as no explicit tool for document creation or conversion beyond document_processor's transformation features—but these are covered indirectly, and the core workflows are well supported.