The MCP server exposes the full GroupDocs.Parser engine: every format the .NET library can read — 50+ document, spreadsheet, presentation, email, e-book, and image formats — is available to your AI agent. The canonical matrix lives in the library documentation: supported document formats.
What each family gives you:
PDF — text, tables, images, metadata, and barcodes. The format most extraction requests arrive as.
DOCX / XLSX / PPTX — the cleanest extractions, because structure is explicit in the source. Spreadsheet tables come out as tables.
Email (MSG, EML) — message text and properties, which is how a lot of business context is stored.
E-books (EPUB) and HTML — long-form text with structure.
Images (JPG, PNG, TIFF) — metadata (EXIF, XMP, IPTC) and barcode detection; no text extraction, because there is no text layer.
The one rule worth internalising:extract_text reads a text layer. Born-digital documents have one; scans do not. On a scan, text extraction returns little or nothing while extract_barcodes still works — the engine’s models detect codes in the rasterized image. There is no OCR step in this server, so printed words in a scan stay pixels.
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.