aspose-pdf-cloud-mcp

# Aspose.PDF Cloud CLI + MCP Tools v1.1.0 Aspose.PDF Cloud CLI exposes Aspose PDF Cloud storage and PDF operations through both a command-line interface and an MCP server. Version 1.1.0 adds PDF attachment listing and extraction, upgrades the MCP server to the MCP Python SDK 2.x, and adds Git-based package versioning and release automation. See [CHANGELOG.md](CHANGELOG.md) for the release notes. ## How to Get Your Aspose.PDF Cloud Credentials 1. Go to the [Dashboard](https://dashboard.aspose.cloud/). 2. After logging in, navigate to the **Applications** section in the main menu. 3. Select the first (default) application or create a new one. 4. Copy the **Client ID** and **Client Secret** for later use. ## Installation Requires Python 3.11 or later. Version 1.1.0 uses Aspose.PDF Cloud SDK 26.x and MCP Python SDK 2.x; pip installs these dependencies automatically. Install from PyPI: ```powershell python -m pip install aspose-pdf-cloud-mcp ``` Check that the CLI is available: ```powershell aspose-pdf-cloud-cli --help apdf --help ``` For local development from a checkout: ```powershell python -m pip install -e ".[dev]" ``` ## Configuration Set credentials before running CLI commands or the MCP server. The easiest local setup path is: ```powershell apdf auth login apdf auth status apdf auth test ``` You can also set credentials directly in your shell: ```powershell $env:ASPOSE_CLIENT_ID = "your-client-id" $env:ASPOSE_CLIENT_SECRET = "your-client-secret" ``` Optional environment variables: - `ASPOSE_STORAGE_NAME`: default Aspose storage name. - `ASPOSE_BASE_URL`: alternate Aspose PDF Cloud base URL. - `ASPOSE_SELF_HOST`: set to `1`, `true`, `yes`, or `on` for self-hosted use. You can also create a local `.env` file. See [`.env.example`](https://github.com/aspose-pdf-cloud/aspose-pdf-cloud-mcp/blob/main/.env.example) for a template. Environment variables take precedence over `.env` values. ## CLI Usage The canonical executable is `aspose-pdf-cloud-cl…