cloud-storage-mcp
One MCP server and Claude-powered CLI to manage Mega.nz, Box, and OneDrive — all from a single install.
Install
pip install cloud-storage-mcp
Supported Providers
| Provider | Status |
|---|---|
| Mega.nz | ✅ Full support |
| Box | ✅ Full support |
| OneDrive | ✅ Full support |
Setup
Credentials are stored locally at ~/.config/cloud-storage-mcp/config (mode 600) and are never included in the package.
On first use, you'll be prompted for each provider's credentials. Or set env vars:
# Mega.nz
export MEGA_EMAIL=your@email.com
export MEGA_PASSWORD=yourpassword
# Box — create app at https://developer.box.com
export BOX_CLIENT_ID=...
export BOX_CLIENT_SECRET=...
export BOX_ACCESS_TOKEN=...
# OneDrive — register app at https://portal.azure.com
export ONEDRIVE_CLIENT_ID=...
export ONEDRIVE_CLIENT_SECRET=...
export ONEDRIVE_TENANT_ID=common # or your Azure tenant ID
# Claude API (CLI only)
export ANTHROPIC_API_KEY=sk-ant-...
Usage
CLI
cloud-storage
# or pre-select a provider
cloud-storage --provider mega
Example prompts:
show storage usage on boxlist all files on onedrivesearch for invoices on megaupload /home/user/report.pdf to boxcreate a folder called Backups on onedrivedownload photo.jpg from mega to /tmp
MCP Server
cloud-storage-mcp
Add to Claude Code (~/.claude/settings.json):
{
"mcpServers": {
"cloud-storage": {
"command": "cloud-storage-mcp",
"env": {
"MEGA_EMAIL": "your@email.com",
"MEGA_PASSWORD": "yourpassword",
"BOX_CLIENT_ID": "...",
"BOX_CLIENT_SECRET": "...",
"BOX_ACCESS_TOKEN": "...",
"ONEDRIVE_CLIENT_ID": "...",
"ONEDRIVE_CLIENT_SECRET": "..."
}
}
}
}
Available MCP Tools
| Tool | Description |
|---|---|
storage_info |
Get storage usage and quota |
storage_list |
List files and folders |
storage_search |
Search by name |
storage_upload |
Upload a local file |
storage_download |
Download a file |
storage_create_folder |
Create a folder |
storage_delete |
Delete a file or folder |
All tools take a provider parameter: "mega", "box", or "onedrive".
License
MIT
Metadata
Release files for cloud-storage-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| cloud_storage_mcp-0.1.0.tar.gz | 11.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cloud_storage_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.0 kB
Release files / cloud_storage_mcp-0.1.0.tar.gz
| Download URL | cloud_storage_mcp-0.1.0.tar.gz |
|---|---|
| Size | 11.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f00f561ec665725580189d92438e5dc324294c0b55d81f146d0f4733b488bc1c
|
|
BLAKE2b-256 checksum How to use checksums |
25d072d82fdfc1013f825f8f7e447f2d9fd769d7f506705ff965169191a64dc1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / cloud_storage_mcp-0.1.0-py3-none-any.whl
| Download URL | cloud_storage_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 13.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7fd95390dcd6014edbf34feab9ad4131b0229590e984eeefb21d246eb3a16440
|
|
BLAKE2b-256 checksum How to use checksums |
bf5bc44e7865ff3e4c40be9828245e21a0e91dde68a3fcf85c2e58d1854137e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for cloud-storage-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.