Click 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 Server Convert 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.
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.
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: Outlook MCP Server
python -m venv .venv
# Windows:
.venv\Scripts\activate
# macOS / Linux:
source .venv/bin/activate
pip install git+https://github.com/aspose-cloud/aspose-email-cloud-python-mcp.gitThis installs the aspose-email-mcp command into your virtual environment.
Two environment variables are required - both come from your Aspose Cloud dashboard's Applications page:
Variable | Value |
| Your application's Client ID |
| Your application's Client Secret |
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.
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"
}
}
}
}On macOS/Linux, use /path/to/.venv/bin/aspose-email-mcp instead. Fully quit and restart Claude Desktop after
editing.
.vscode/mcp.json), Cursor (~/.cursor/mcp.json), Cline, WindsurfSame 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"
}
}
}
}Tool | What it does | Read-only | Dry-run |
| Get calendar file from storage. | yes | - |
| Get iCalendar list from storage folder. | yes | - |
| Get iCalendar from storage as AlternateView | yes | - |
| Converts calendar document from storage to specified format and returns as file. | yes | - |
| Get contact document from storage. | yes | - |
| Get contact list from storage folder. | yes | - |
| Converts contact document from storage to specified format and returns as file | yes | - |
| Get email list from storage folder. | yes | - |
| Converts email document from storage to specified format and returns as file | yes | - |
| Extract structured metadata from a local email file | no | yes |
| Convert a local email file to another format | yes | - |
| Get MAPI calendar document. | yes | - |
| Get MAPI contact document. | yes | - |
| Get MAPI message document. | yes | - |
| Check email address is disposable | yes | - |
| Discover email accounts by email address. Does not validate discovered accounts. | yes | - |
| Get email client account from storage. | yes | - |
| Get email client multi account file (*.multi.account). Will respond error if file extension is not ".multi.account". | yes | - |
| Delete a folder in email account | no | yes |
| Get folders list in email account | yes | - |
| Send an email specified by model in request. | no | yes |
| Fetch message from email account | yes | - |
| Delete message. | no | yes |
| Fetch message as file from email account | yes | - |
| Get messages from folder, filtered by query | yes | - |
| Get message threads from folder. All messages are partly fetched (without email body and some other fields). | yes | - |
| Get messages from thread by id. All messages are fully fetched. For accounts with CacheFile only cached messages will be returned. | yes | - |
| Delete thread by id. All messages from thread will also be deleted. | no | yes |
| Parse name to components. | yes | - |
| Detect person's gender from name string. | yes | - |
| The call proposes k most probable names for given starting characters. | yes | - |
| Formats a person's name in correct case and name order using options for formatting instructions. | yes | - |
| Expands a person's name into a list of possible alternatives using options for expanding instructions. | yes | - |
| Compare people's names. Uses options for comparing instructions. | yes | - |
| Parse person's name out of an email address. | yes | - |
| Download file | yes | - |
| Delete file | no | yes |
| Copy file | no | yes |
| Move file | no | yes |
| Get all files and folders within a folder | yes | - |
| Create the folder | no | yes |
| Delete folder | no | yes |
| Copy folder | no | yes |
| Move folder | no | yes |
| Check if storage exists | yes | - |
| Get disc usage | yes | - |
| Get file versions | 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.
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).
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
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.
Send transactional email and manage domains, audiences, and broadcasts from any MCP client.
Email inboxes for AI agents: send, receive, reply, search, and manage threaded email over MCP.
