GroupDocs.Conversion MCP Server Leave feedback

GroupDocs.Conversion MCP server lets AI agents like Claude, Cursor, and Copilot convert documents between 100+ formats — PDF, Word, Excel, PowerPoint, images, Markdown — locally on your machine. Files are never uploaded to any cloud service.

Run it with one command. The Docker image is self-contained — the runtime and every native dependency the engine needs are inside it:

docker run --rm -i -v $(pwd)/documents:/data \
  ghcr.io/groupdocs-conversion/conversion-net-mcp:latest

With the .NET 10 SDK installed, the same server also runs without Docker:

dnx GroupDocs.Conversion.Mcp --yes

Both are the .NET build of the server and run on Windows, Linux, and macOS. Other platforms will each get their own launcher — see Install for your platform.

Or use the guided installer to register the server in your AI client, verify the setup, and configure shared folders in one pass.

The server exposes these tools to any MCP-compatible agent (full details in the tools reference):

• convert — convert a document to another format (PDF, DOCX, XLSX, PPTX, HTML, PNG, JPG, Markdown, and many more) and save it to your storage folder.
• get_supported_formats — list every target format a given document can be converted to.
• get_document_info — file type, page count, and basic properties, without converting.
• get_license_status — which licensing mode is active (evaluation, license file, or metered) and, under metered, how much has been consumed.

Ask your agent in plain language — “Convert report.docx to PDF”, “Turn this PDF into Markdown” — and it picks the right tool.

Installation, prerequisites, and client configuration are platform-specific; the tools and licensing model below are the same everywhere.

This server does format conversion: full-fidelity transformation of a document into another format (LLM-ready Markdown included), preserving layout, headings, tables, and lists. If you need field-level data extraction — pulling specific values, structured tables, or text spans out of documents — use the companion GroupDocs.Parser MCP server. Many pipelines use both: convert for ingestion, parse for extraction.

Exact config blocks for every client: Register in AI clients.

The server uses MCP’s local stdio transport: your AI client starts the server as a child process and talks to it over standard input/output. There are no inbound ports, no external endpoints, and no telemetry — the data path is agent → local server → local filesystem. That makes it suitable for regulated and internal documents that must not leave your machine. Details: On-premise architecture.

Simple Markdown-extraction servers cover plain text well. Choose this server when you need: complex layouts and tables preserved, Office formats in both directions (DOCX/XLSX/PPTX as output, not only input), PDF/A for archiving, image renditions (PNG/JPG previews), password-protected documents, and the rendering fidelity of the commercial GroupDocs engine trusted by enterprise teams for over a decade.

• Quick start · Use cases · Troubleshooting & FAQ
• GitHub: server source · installer · integration tests
• NuGet package · Docker image · MCP Registry
• Questions: Conversion forum