Configuration
Leave feedback
On this page
Configure the GroupDocs.Conversion MCP server through one config file: the documents folder, output folder, license path, delivery channel (Docker or NuGet), and target clients — set once, applied everywhere. This is the installer’s groupdocs-mcp.config.json:
{
"channel": "docker",
"registry": "ghcr",
"clients": ["claude-desktop", "vscode"],
"version": "latest",
"storagePath": "D:/Storage/Documents",
"outputPath": "D:/Storage/Output",
"licensePath": "D:/Storage/Licenses/GroupDocs.Total.lic",
"products": ["conversion"]
}
channel—docker(self-contained, recommended) ornuget(dnx, needs the .NET 10 SDK).storagePath— where the server reads input documents (created if missing).outputPath— optional separate folder for converted files; empty = same as storage.licensePath— empty string = evaluation mode (safe, no error); see Licensing.version—"latest"or a pin such as"26.7.2". Pinning is recommended for shared/committed configs.- Any CLI switch overrides the file:
-Channel,-Products,-Clients,-Version.
When you register the server manually, the same settings travel as environment variables:
| Variable | Description | Default |
|---|---|---|
GROUPDOCS_MCP_STORAGE_PATH | Base folder for input and output files | current directory |
GROUPDOCS_MCP_OUTPUT_PATH | Optional separate folder for output files | same as storage |
GROUPDOCS_LICENSE_PATH | Path to a GroupDocs license file | empty = evaluation mode |
On the docker channel, host folders map into the container:
storagePath→/data(withGROUPDOCS_MCP_STORAGE_PATH=/data)outputPath→/data/output(when set)- license folder →
/license:rowithGROUPDOCS_LICENSE_PATH=/license/<file>.lic
docker run --rm -i \
-v /path/to/documents:/data \
-v /path/to/license-folder:/license:ro \
-e GROUPDOCS_LICENSE_PATH=/license/GroupDocs.Total.lic \
ghcr.io/groupdocs-conversion/conversion-net-mcp:latest
For container fleets without client registration, generate a docker-compose.yml:
./install-groupdocs-mcp.ps1 -EmitCompose -Clients @()
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.