
Groupdocs Watermark Mcp
Let your coding agent add or search text/image watermarks on Office and PDF files through GroupDocs without hand-rolling REST calls.
Overview
GroupDocs Watermark MCP is a MCP server for the Build phase that lets AI agents add and search watermarks on documents via GroupDocs.Watermark on local file paths.
What is this MCP server?
- stdio MCP server (NuGet GroupDocs.Watermark.Mcp 26.5.0) for agent-driven watermark workflows
- Configurable GROUPDOCS_MCP_STORAGE_PATH and optional GROUPDOCS_MCP_OUTPUT_PATH for input/output folders
- GROUPDOCS_LICENSE_PATH for full GroupDocs.Total.lic or evaluation mode without a license
- Designed for AI agents to add and search document watermarks via GroupDocs.Watermark
- Registry version 26.5.0
- Transport stdio via NuGet identifier GroupDocs.Watermark.Mcp
- 3 documented environment variables: storage path, optional output path, optional license path
What problem does it solve?
Agents cannot safely watermark PDFs and Office files without a documented bridge to a serious document SDK and clear folder conventions.
Who is it for?
Indie builders automating contract packs, course PDFs, or client deliverables that need visible or invisible watermarks through an agent.
Skip if: Teams that only need a single static image on one PDF and have no GroupDocs license budget or .NET MCP runtime tolerance.
What do I get? / Deliverables
After registration, your agent can produce watermarked outputs under your configured storage paths and query existing marks using the same tool surface.
- Watermarked document files under configured output paths
- Agent-callable search results for existing watermarks in supported formats
- Repeatable local watermark pipeline without custom GroupDocs REST glue
Recommended MCP Servers
Journey fit
Document watermarking is wired when you integrate file-processing into the product pipeline, which sits in Build before you ship protected assets. This is an MCP bridge to a third-party document SDK—canonical placement is integrations alongside other external services.
How it compares
Filesystem-backed GroupDocs integration MCP, not a hosted document SaaS or a generic PDF skill.
Common Questions / FAQ
Who is GroupDocs Watermark MCP for?
Solo and small teams building document workflows who want Claude or Cursor to call GroupDocs watermark APIs via MCP instead of custom scripts.
When should I use GroupDocs Watermark MCP?
Use it during Build when you integrate outbound files—reports, decks, agreements—and need repeatable add-or-search watermark steps from the agent.
How do I add GroupDocs Watermark MCP to my agent?
Register the stdio server from NuGet package GroupDocs.Watermark.Mcp, set GROUPDOCS_MCP_STORAGE_PATH (and optional OUTPUT_PATH and LICENSE_PATH), then connect it in your MCP client config.