Aspose.Slides Cloud MCP Server

Presentation processing — convert, create, split, replace text, and read slides/images/properties.

An MCP server exposing Aspose.Slides Cloud's REST API as typed, agent-callable tools. Also bundles Aspose Storage Cloud's core file operations (storage_upload_file/storage_download_file/storage_list_files/storage_delete_file), so a client connected to only this server can complete a full upload -> process -> download workflow with no second server connection.

Handles: PPTX, PPT, ODP.

Requirements

• Python 3.11 or later

• An Aspose Cloud account (free evaluation tier available) - you'll need a Client ID and Client Secret from your dashboard's Applications page

• An MCP-compatible AI client (Claude Desktop, Claude Code, VS Code, Cursor, Cline, Windsurf, etc.)

Related MCP server: pharos-ai-doc-genie

Setup

1. Create a virtual environment and install

python -m venv .venv
# Windows:
.venv\Scripts\activate
# macOS / Linux:
source .venv/bin/activate

pip install git+https://github.com/aspose-cloud/aspose-slides-cloud-python-mcp.git

This installs the aspose-slides-mcp command into your virtual environment.

2. Configure your AI client

Two environment variables are required - both come from your Aspose Cloud dashboard's Applications page:

Credentials are never passed as a tool parameter - the server resolves them once at launch from these environment variables, exchanges them for a short-lived OAuth2 token, and caches/refreshes it transparently.

Claude Desktop

Config file location:

{
  "mcpServers": {
    "slides": {
      "command": "C:\\path\\to\\.venv\\Scripts\\aspose-slides-mcp.exe",
      "env": {
        "ASPOSE_CLIENT_ID": "your-client-id",
        "ASPOSE_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

On macOS/Linux, use /path/to/.venv/bin/aspose-slides-mcp instead. Fully quit and restart Claude Desktop after editing.

VS Code (.vscode/mcp.json), Cursor (~/.cursor/mcp.json), Cline, Windsurf

Same shape, under a "servers" key instead of "mcpServers" for VS Code:

{
  "servers": {
    "slides": {
      "type": "stdio",
      "command": "/path/to/.venv/bin/aspose-slides-mcp",
      "env": {
        "ASPOSE_CLIENT_ID": "your-client-id",
        "ASPOSE_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

Available tools

Every mutating tool marked "yes" under Dry-run accepts a dry_run=true parameter to preview the change without applying it.

Tool errors use a fixed taxonomy (bad input / auth failure / server error / rate limited), returned as structured MCP tool errors - never a silent failure or a raw exception message.

Part of the Aspose Cloud MCP family

One MCP server per Aspose Cloud product, published under github.com/aspose-cloud. This server depends on aspose-storage-core-mcp for its bundled storage tools — that repo is a shared library, not a standalone server (there's no real Aspose Cloud API route for storage on its own; every real storage call goes through some product's own gateway, this one included).

License

MIT (see LICENSE) — covers only this repository's own MCP wrapper/integration code. It does not cover, and grants no rights to, the Aspose Cloud product or API themselves, which remain governed entirely by Aspose's own product and usage terms. A valid Aspose Cloud account and subscription/credentials are required to actually call the API, regardless of this code's license.