Groupdocs Conversion Mcp
Convert uploaded Office, PDF, and other formats inside the agent loop so docs and exports match what your product promises.
Overview
GroupDocs Conversion MCP is a MCP server for the Build phase that converts documents, inspects them, and lists supported formats via AI agents.
What is this MCP server?
- Convert documents between supported formats via MCP-exposed tools
- Inspect document properties and list supported conversion formats
- stdio MCP via NuGet GroupDocs.Conversion.Mcp (v26.5.2)
- Shared GroupDocs env pattern: storage path, optional output path, optional license path
- Evaluation mode when GROUPDOCS_LICENSE_PATH is omitted
- Package version 26.5.2
- stdio transport type
- NuGet identifier GroupDocs.Conversion.Mcp
What problem does it solve?
Your agent hits binary Office or PDF inputs and cannot convert them to the format your docs site or API expects without external manual steps.
Who is it for?
Builders creating export/import features, migrating help docs, or batch-normalizing customer files during product development.
Skip if: Pure code-only repos with no document IO, or workflows that only need a single static Markdown source.
What do I get? / Deliverables
Conversions land in your configured output directory with format support discoverable from the agent before you commit to a pipeline design.
- Converted files in output path
- Format capability lists the agent can plan around
- Inspection metadata on source documents pre-conversion
Recommended MCP Servers
Journey fit
Format conversion is foundational while you build content pipelines, help centers, and export features—canonical shelf is Build. Docs subphase covers normalizing source files into shippable formats the rest of your stack can ingest.
How it compares
Multi-format document conversion MCP, not a screenshot or browser automation server.
Common Questions / FAQ
Who is GroupDocs Conversion MCP for?
Solo developers building document import/export, knowledge bases, or compliance archives who want conversion inside their MCP agent.
When should I use GroupDocs Conversion MCP?
Use it during Build docs when you need to transform source files and verify which output formats the GroupDocs engine exposes.
How do I add GroupDocs Conversion MCP to my agent?
Add the stdio NuGet server GroupDocs.Conversion.Mcp to MCP settings, configure GROUPDOCS_MCP_STORAGE_PATH, and optionally license and output paths.