DocWand

What DocWand MCP server does

DocWand provides browser-based operations for PDF documents. Its stated capabilities are signing PDFs, filling PDF forms, merging multiple PDFs, and splitting PDFs into separate files. These functions cover common document-preparation tasks without requiring the files to leave the user's device.

The available description does not specify whether each operation is exposed as a separate MCP tool, how an MCP client connects, or which document formats are accepted beyond PDFs. Treat the documented scope as limited to the four named PDF actions.

How it works

DocWand runs in a browser. The available product description states that files never leave the device, so the workflow is intended for local document handling rather than an upload-based service. A user can use the browser interface to apply a signature, complete fields, combine PDFs, or divide a PDF into parts.

For an agent-based workflow, the DocWand MCP server would need to be connected through an MCP-compatible setup, but the supplied material does not describe a transport, endpoint, authentication method, or client configuration. Those details should be confirmed before planning an automated integration.

Tools and capabilities

The documented PDF capabilities are:

• Sign PDF documents.
• Fill PDF forms or fields.
• Merge PDFs into a combined document.
• Split PDFs into separate documents.
• Keep files on the device during browser use.

The source does not provide tool names, input schemas, output formats, or limits such as file size, page count, or signature types. The DocWand MCP server should therefore be evaluated against those requirements before it is selected for a production document pipeline.

Limitations and notes

No README or MCP-specific technical documentation is available in the supplied material. There is no confirmed information about installation, environment variables, supported MCP clients, remote access, authentication, API behavior, or licensing. The only stated privacy property is that files never leave the device in the browser-based workflow.

That local-processing description may suit documents that should not be uploaded to a third-party service. It does not, by itself, establish how an external agent invokes the DocWand MCP server or whether browser operations can be controlled programmatically. Confirm those points with the project before implementation.