Aspose.Email Cloud MCP Server
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Aspose.Email Cloud MCP ServerConvert the email file meeting.msg to EML format and show the result."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Aspose.Email Cloud MCP Server
Email, calendar, and contact processing — read/convert messages, calendars, and contacts; manage mail client accounts, folders, and threads; parse and format personal names.
An MCP server exposing Aspose.Email 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: MSG, EML, ICS, VCF, PST, MHTML.
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: mail-mcp
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-storage-cloud-python-mcp.git@v1.0.5 git+https://github.com/aspose-cloud/aspose-email-cloud-python-mcp.git@v1.4.0This installs the aspose-email-mcp command into your virtual environment. The first package is the shared file-tool library (upload, download, list, delete) that every Aspose Cloud MCP server depends on; it is not on PyPI, so it is installed from GitHub in the same command.
2. Configure your AI client
Three environment variables are required. The first two come from your Aspose Cloud dashboard's Applications page; the third is a folder you create on your own computer (see Your files folder below):
Variable | Value |
| Your application's Client ID |
| Your application's Client Secret |
| Full path of the folder on your computer where your input files are placed and results are saved |
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.
Your files folder (ASPOSE_FILES_PATH)
Create a folder on your computer (for example C:\Users\you\Documents\aspose-files on Windows, or
/home/you/aspose-files on macOS/Linux) and set ASPOSE_FILES_PATH to its full path. It is the one
place this server reads your files from and writes results to:
Input: put the document you want processed in that folder, then ask your assistant to upload it with
storage_upload_file, giving only the bare filename (for examplereport.docx). The upload sends it to your Aspose Cloud Storage, where the processing tools read it. Subfolders and full paths are rejected.Output:
storage_download_filesaves a result from Cloud Storage back into the same folder, and its reply contains the full local path of the saved file.The file and folder arguments of the other tools name locations in your Aspose Cloud Storage, not your computer.
Claude Desktop
Config file location:
Platform | Path |
Windows |
|
macOS |
|
{
"mcpServers": {
"email": {
"command": "C:\\path\\to\\.venv\\Scripts\\aspose-email-mcp.exe",
"env": {
"ASPOSE_CLIENT_ID": "your-client-id",
"ASPOSE_CLIENT_SECRET": "your-client-secret",
"ASPOSE_FILES_PATH": "C:\\Users\\you\\Documents\\aspose-files"
}
}
}
}On macOS/Linux, use /path/to/.venv/bin/aspose-email-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": {
"email": {
"type": "stdio",
"command": "/path/to/.venv/bin/aspose-email-mcp",
"env": {
"ASPOSE_CLIENT_ID": "your-client-id",
"ASPOSE_CLIENT_SECRET": "your-client-secret",
"ASPOSE_FILES_PATH": "/home/you/aspose-files"
}
}
}
}Available tools
Tool | What it does | Read-only | Dry-run |
| Retrieves the specified iCalendar file from cloud storage. | yes | - |
| Retrieves a paginated list of iCalendar files stored in a specified folder. | yes | - |
| Retrieves an iCalendar file from Aspose Cloud storage and returns its AlternateView representation based on the specified calendar action. | yes | - |
| This tool fetches a calendar document from Aspose Cloud storage, converts it to the specified format, and returns the resulting file. | yes | - |
| The tool converts an uploaded calendar file into a structured calendar model representation. | no | yes |
| The tool retrieves a contact document from the specified storage location. | yes | - |
| Retrieves a list of email contacts from a specified folder and storage using the given contact document format. | yes | - |
| Converts a contact document stored in Aspose Cloud from one format to another and returns the resulting file as binary data. | yes | - |
| Converts a contact document file (VCard, WebDav, or Msg) into its Aspose.Email model representation. | no | yes |
| The tool retrieves a list of email files stored in a specified folder of Aspose Cloud storage. | yes | - |
| The tool fetches an email document from Aspose Cloud storage, converts it to a specified format, and returns the result as a downloadable file. | yes | - |
| This tool converts an email document file into a structured email model representation. | no | yes |
| It converts an uploaded email document from a given source format to a specified target format and returns the resulting file. | yes | - |
| This tool retrieves a MAPI calendar file from Aspose Cloud storage. | yes | - |
| Retrieves a MAPI contact document from Aspose Cloud storage in the format you specify. | yes | - |
| This tool retrieves a specific email document stored as a MAPI message from Aspose Cloud. | yes | - |
| This tool determines whether a given email address is a disposable (temporary) address. | yes | - |
| The tool discovers email server configuration settings for a given email address without validating the discovered accounts. | yes | - |
| The tool creates or updates an email client account file (*.account) in the specified storage location using the supplied credentials. | no | yes |
| Retrieves the email client account configuration stored in a specified file on Aspose Cloud storage. | yes | - |
| Retrieves a multi‑account email client file (must have the “.multi.account” extension) from Aspose Cloud storage. | yes | - |
| The tool creates a new mail folder in a specified email account. | no | yes |
| Deletes a specified folder from a user's email account. | no | yes |
| The tool retrieves the list of folders (or sub‑folders) for a specified email account. | yes | - |
| Retrieves a single email message from a specified email account (and optional folder) and returns it in the requested representation. | yes | - |
| Deletes a specific email message from the user's mailbox. | no | yes |
| Fetches a single email message from a specified account and returns it as a downloadable file in the chosen format. | yes | - |
| Adds an email message from a supplied file into a specified folder of a given email account. | no | yes |
| Retrieves a list of email messages from a specified folder in a given email account, optionally filtered by a query string and returned in a chosen representation. | yes | - |
| The tool retrieves a list of email message threads from a specified folder in a given email account, returning only partial information for each message (no body or full… | yes | - |
| Retrieves all messages that belong to a given email thread, optionally scoped to a specific folder or storage location. | yes | - |
| Deletes an email thread identified by its ID, removing all messages contained in that thread. | no | yes |
| The tool parses one or more email image files stored in Aspose Cloud storage and creates corresponding vCard files in a specified output folder. | no | yes |
| The tool extracts contact information from an uploaded image and returns it as structured vCard document models. | no | yes |
| Parse a personal name into its constituent components (e.g., given name, middle name, surname, title, etc.) using the Aspose Cloud AiName service. | yes | - |
| This tool invokes the Aspose Cloud AI Name genderize endpoint to infer the most likely gender for a given personal name. | yes | - |
| This tool returns up to k suggested full names that best complete the supplied name prefix. | yes | - |
| Formats a given person’s name into the correct case and order using optional language, region, script, style, and formatting settings, and returns the formatted name. | yes | - |
| This tool expands a given personal name into a list of possible alternative spellings or forms based on optional language, location, encoding, script, and style settings. | yes | - |
| This tool compares two personal names and returns a similarity assessment. | yes | - |
| This tool extracts a person’s name from a given email address using Aspose Cloud’s AiName parsing service. | yes | - |
| The tool downloads a file from Aspose Cloud Email storage and returns the file’s binary contents. | yes | - |
| Deletes a file stored in Aspose Cloud at the specified path. | no | yes |
| Copies a file from a specified source path in Aspose Cloud storage to a given destination path, optionally using different source or destination storages or a particular… | no | yes |
| Moves a file from a source location to a destination location within Aspose Cloud storage, optionally specifying different storage names or a file version. | no | yes |
| Retrieves a list of all files and sub‑folders that exist inside a given email storage folder. | yes | - |
| Creates a new folder in the specified Aspose Cloud email storage at the given path. | no | yes |
| Deletes a specified folder from Aspose Cloud email storage. | no | yes |
| Copies a folder from a source path to a destination path in Aspose Email Cloud storage. | no | yes |
| Moves an existing folder from one location to another within Aspose Cloud storage. | no | yes |
| The tool checks whether a specified Aspose Cloud storage container exists. | yes | - |
| The tool returns the current disc usage statistics for Aspose.Email cloud storage. | yes | - |
| Retrieves the complete version history for a specified file stored in Aspose Email Cloud. | yes | - |
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.
This server cannot be deployed
Maintenance
Related MCP Connectors
Hosted email MCP for your own Gmail, Outlook.com, Microsoft 365, iCloud or IMAP inbox: read, search, draft, reply in thread, forward and file mail. It moves or flags up to 500 messages in one call, and a send leaves exactly one copy in Sent. A calendar is a separate connection, and connecting one adds diary and scheduling tools.
Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.
Your mailbox for MCP clients: search, read, draft, send, rules and notes. Sending is off by default.
- EusendOAuthdev.eusend
Send transactional email and manage domains, audiences, and broadcasts from any MCP client.
Related MCP Servers
- FlicenseAqualityCmaintenanceEnables unified email and attachment reading through a local stdio MCP interface, supporting multiple email accounts, inbox listing, message retrieval, attachment downloads, and full email export.51-
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients to access locally structured personal email data, with tools to list, search, retrieve emails and action items, and get mailbox statistics.-
- AlicenseNot gradedqualityAmaintenanceLets MCP clients read local Thunderbird mail, search messages and contacts, request bounded mailbox changes such as moves or tags, and prepare outgoing messages in Thunderbird’s native composer for user review and manual sending.MIT
- AlicenseBqualityAmaintenanceEnables AI agents to read, search, send, and organize mail, folders, messages, and threads through a local MCP server. It supports multiple data centers, attachments, and secure credential storage.332MIT