Supported formats

View as MarkdownMarkdown

Set up your AI agent

Give your coding agent live access to the GroupDocs documentation and API reference through the GroupDocs Docs MCP server — no install, no API key. Learn more

claude mcp add --transport http groupdocs-docs https://docs.groupdocs.com/mcp

Also process documents locally

The GroupDocs.Signature MCP server lets your agent work with files on your machine; they are never uploaded. It needs the .NET 10 SDK or Docker.

claude mcp add groupdocs-signature -- dnx GroupDocs.Signature.Mcp --yes
Folders, licensing and more →

On this page

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.

On this page