MCP (Model Context Protocol) servers for Aspose document processing products. Connect your AI assistant to Aspose tools for working with Word documents, PDFs, spreadsheets, presentations, email, images, and more — all without leaving your AI client.
Each Aspose product runs as its own isolated MCP server.
- Python 3.10 or later (Python 3.12 required for CAD)
- An MCP-compatible AI client (Claude Desktop, VS Code, Cursor, Cline, Windsurf, etc.)
- An Aspose license (optional — free evaluation mode available)
git clone https://github.com/aspose-total/Aspose.Total-for-Python-via-.NET-MCP-Server
cd Aspose.Total-for-Python-via-.NET-MCP-ServerRun the setup script from the servers/ folder. It creates an isolated virtual
environment for each product and installs the required Aspose package.
Windows — all products:
servers\setup_all.batWindows — specific products only:
servers\setup_all.bat ocr words pdf cells slidesmacOS / Linux — all products:
bash servers/setup_all.shmacOS / Linux — specific products only:
bash servers/setup_all.sh ocr words pdf cells slidesAll tools read input files from and write output files to a single directory you control. Create it anywhere, e.g.:
C:\asposefiles (Windows)
~/asposefiles (macOS / Linux)
Drop your input files (Word docs, PDFs, images, etc.) into this folder before calling any tool.
Add one entry per product to your MCP host config. Every entry follows the same pattern — only the product name changes.
Two environment variables are required for each entry:
| Variable | Value |
|---|---|
ASPOSE_FILES_PATH |
Path to the directory created in step 3 |
ASPOSE_LICENSE_FILE |
Full path to your .lic file (omit to use evaluation mode) |
Config file location:
| Platform | Path |
|---|---|
| Windows (direct install) | %APPDATA%\Claude\claude_desktop_config.json |
| Windows (Store install) | %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\claude_desktop_config.json |
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
{
"mcpServers": {
"aspose-words": {
"command": "C:\\path\\to\\mcp-aspose-python\\servers\\words\\.venv\\Scripts\\python.exe",
"args": ["C:\\path\\to\\mcp-aspose-python\\servers\\words\\server.py"],
"env": {
"ASPOSE_FILES_PATH": "C:\\asposefiles",
"ASPOSE_LICENSE_FILE": "C:\\asposefiles\\Conholdate.Total.Product.Family.lic"
}
},
"aspose-pdf": {
"command": "C:\\path\\to\\mcp-aspose-python\\servers\\pdf\\.venv\\Scripts\\python.exe",
"args": ["C:\\path\\to\\mcp-aspose-python\\servers\\pdf\\server.py"],
"env": {
"ASPOSE_FILES_PATH": "C:\\asposefiles",
"ASPOSE_LICENSE_FILE": "C:\\asposefiles\\Conholdate.Total.Product.Family.lic"
}
}
}
}On macOS / Linux use forward slashes and .venv/bin/python instead of .venv\Scripts\python.exe.
Fully quit and restart Claude Desktop after editing (File → Quit, not just close the window).
Claude Desktop app supports MCP. The claude.ai browser tab does not.
{
"servers": {
"aspose-words": {
"type": "stdio",
"command": "/path/to/mcp-aspose-python/servers/words/.venv/bin/python",
"args": ["/path/to/mcp-aspose-python/servers/words/server.py"],
"env": {
"ASPOSE_FILES_PATH": "/home/user/asposefiles",
"ASPOSE_LICENSE_FILE": "/home/user/asposefiles/Conholdate.Total.Product.Family.lic"
}
}
}
}Same JSON shape as VS Code — just use the appropriate config file location for each tool.
| Server key | Product | Handles |
|---|---|---|
aspose-words |
Aspose.Words | DOCX, DOC, RTF, ODT, Markdown |
aspose-pdf |
Aspose.PDF | PDF create, convert, extract, sign |
aspose-cells |
Aspose.Cells | XLSX, XLS, CSV, ODS |
aspose-slides |
Aspose.Slides | PPTX, PPT, ODP |
aspose-email |
Aspose.Email | MSG, EML, PST, MBOX, MHTML |
aspose-ocr |
Aspose.OCR | Image/scan → text extraction |
aspose-imaging |
Aspose.Imaging | PNG, JPEG, TIFF, BMP, SVG, WebP |
aspose-barcode |
Aspose.BarCode | Generate and read barcodes / QR codes |
aspose-zip |
Aspose.ZIP | ZIP, RAR, 7z, TAR |
aspose-html |
Aspose.HTML | HTML ↔ PDF/image conversion |
aspose-psd |
Aspose.PSD | Photoshop PSD / PSB files |
aspose-svg |
Aspose.SVG | SVG processing and conversion |
aspose-tex |
Aspose.TeX | TeX / LaTeX typesetting |
aspose-page |
Aspose.Page | XPS, EPS, PS files |
aspose-cad |
Aspose.CAD | DWG, DXF, DWF and other CAD formats |
aspose-3d |
Aspose.3D | FBX, OBJ, STL, GLTF and 3D formats |
aspose-tasks |
Aspose.Tasks | MPP, MPT (Microsoft Project files) |
aspose-diagram |
Aspose.Diagram | VSD, VSDX (Visio diagrams) |
aspose-finance |
Aspose.Finance | XBRL, iXBRL financial reports |
Each product runs as a separate MCP server process with its own Python virtual environment. Separate venvs guarante complete isolation.
All tools accept a bare filename (e.g. report.docx) and resolve it against
ASPOSE_FILES_PATH automatically. Never pass full paths to tool parameters.
List all tools of an aspose mcp server with a prompt like "list all aspose tasks mcp server tools"
Run an individual aspose mcp tool with a prompt like "Create a project file with 5 tasks for a Hello World app using aspose tasks mcp tool"
| Symptom | Fix |
|---|---|
| No tools appear in the AI client | Verify command points to the product's .venv Python, not the system Python. Fully restart the client. |
ModuleNotFoundError: No module named 'aspose.xxx' |
Run setup_venv.bat (or .sh) for that product — the venv is missing or incomplete. |
| File not found errors | Confirm ASPOSE_FILES_PATH is set and your file is in that directory. |
| Watermarked or limited output | Set ASPOSE_LICENSE_FILE to your .lic file path. |
| CAD server fails to start | aspose-cad requires Python 3.12. Ensure py -3.12 is available before running setup_venv.bat. |


