How to watermark documents with AI agents using MCP

Watermarking through an agent is the small task nobody schedules and everybody needs: mark this before it goes out, brand these before the client sees them, stamp DRAFT until it is approved.

Note
The commands and config snippets on this page are for the .NET build of the server — the only platform available today. Installation and client setup: MCP server for .NET. Other platforms will expose the same tools with their own launch command; everything else on this page applies unchanged.

The pattern

  1. Put the document in the storage folder the server can see.
  2. Ask: “Add a diagonal CONFIDENTIAL watermark to contract.pdf.”
  3. The agent calls add_watermark with the text, a font size, and a rotation.
  4. A watermarked copy appears in your output folder; the original is untouched.

Text or image

You wantToolKey parameters
CONFIDENTIAL / DRAFT / a dateadd_watermarktext, fontSize, rotation
A logo, stamp, or signature scanadd_image_watermarkwatermarkImage, opacity, rotation

rotation: -45 gives the classic diagonal. For image watermarks, opacity between 0.2 and 0.4 usually reads as branding rather than as an obstruction.

Chaining

Every call writes a new file. To put a logo and a text mark on the same document, the second call must take the file the first one produced:

Add the logo at 30% opacity, then add a DRAFT text watermark to that result.

Without “to that result”, the second call starts from the original and only the DRAFT survives.

Check the licence before a batch

Unlicensed output carries evaluation limitations — which on a watermarking tool means the copies you were about to distribute are not distributable. One call to get_license_status settles it; see Licensing.

Setup

dnx GroupDocs.Watermark.Mcp --yes

with GROUPDOCS_MCP_STORAGE_PATH pointing at your documents folder — per-client config or the installer.

Where to go next