The MCP server exposes the full GroupDocs.Signature engine: every format the .NET library can sign, verify, and search — 30+ document, spreadsheet, presentation, image, and archive formats — is available to your AI agent. The canonical matrix lives in the library documentation: supported document formats.
What agents are asked for most:
PDF — the full range: text, QR, barcode, image, and digital signatures, plus verification.
DOCX / XLSX / PPTX — Office documents support digital signatures as well as visual marks, so a signed contract stays a Word file if that is what your process expects.
Images (PNG, JPG, TIFF) — visual marks and code search work on scans; digital signing does not apply.
Not every type works on every format. Digital certificate signatures are supported on PDF and Office documents; visual marks (text, qrcode, barcode) work far more widely. If a signing call fails with an unsupported-format message, that mismatch is usually why — get_document_info tells you what you are actually holding.
Not sure what is already in a file? Ask — “what signatures does this document have?” — and the agent runs the search tools and reports back.
Was this page helpful?
Any additional feedback you'd like to share with us?
Please tell us how we can improve this page.
Thank you for your feedback!
We value your opinion. Your feedback will help us improve our documentation.