Troubleshooting & FAQ Leave feedback
On this page
Solutions to the most common GroupDocs.Conversion MCP server issues — server not appearing in the client, startup failures, missing native dependencies, and first-launch timeouts.
NotePlatform-specific troubleshooting: runtime problems depend on which build you run. For thednxrunner, native graphics libraries, and the Docker channel, see Troubleshooting (.NET). The issues on this page apply to every platform.
- Restart the client — every client reads its MCP config only at startup.
- Check the config file location for your OS (per-client reference) and that the entry sits under the right root key (
mcpServersfor Claude Desktop/Cursor/Windsurf,serversfor VS Code/VS 2022). - Validate the JSON — a trailing comma silently breaks the whole file. If you used the installer, a timestamped
.bakof your previous config sits next to the file for comparison.
A cold cache: on the very first use the server’s package or image is still downloading while the client is already waiting on the connection. Warming it once fixes it for good — the exact command depends on your build: .NET.
These are properties of the build you run rather than of MCP, so the fixes live with the platform:
| Symptom | Where the fix is |
|---|---|
dnx: command not found | .NET troubleshooting — dnx ships inside the .NET 10 SDK |
DllNotFoundException: libgdiplus on Linux/macOS | .NET troubleshooting — install the native graphics libraries, or use the Docker image |
| “docker daemon not reachable” | .NET troubleshooting — start Docker Desktop or dockerd |
Apply your GroupDocs.Conversion (or GroupDocs.Total) license — set licensePath in the installer config or GROUPDOCS_LICENSE_PATH in a manual entry. Evaluation mode also caps a server process at 15 opened documents. Details and license links: Licensing.
Not currently. Conversion works on documents with a text layer; a scanned, image-only PDF converts as images, not recognized text. If OCR is important for your pipeline, tell us in the forum — it directly shapes the roadmap.
Ask your agent “list your GroupDocs conversion tools and the license status” — it should name convert, get_supported_formats, get_document_info, and get_license_status. For a scripted check that performs the real MCP handshake and a live conversion call, see verifying a .NET installation.
Post your config (redact license paths) and the client name in the Conversion forum — we answer MCP questions daily. Bugs: GitHub issues.
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.
