| name | storage-mcp |
| description | Use when MCP servers for cloud storage. Connect AI agents to S3, Google Drive, Dropbox, and file storage for automated backup, sync, and management. |
| domain | integrations |
| author | oyi77 |
| license | Apache-2.0 |
| subdomain | integrations |
| tags | ["ai-agent","api","integrations","mcp","storage","third-party"] |
| version | 1.0.0 |
Storage MCP Skill
When NOT to Use
- Task is outside your authorization scope
- You need to implement controls (use implementing-* skills)
- Task is about analysis, not action (use analyzing-* skills)
- You don't have access to target systems
- Task requires compliance expertise (consult professionals)
- Task is about defense, not offense (use defensive skills)
Overview
MCP servers enabling AI agents to interact with cloud storage services. Automate backups, file sync, data migration, and storage management across S3, Google Drive, and Dropbox.
Supported: AWS S3, Google Drive, Dropbox, Azure Blob
Use Cases: Backup, sync, file management, data migration
When to Use
Trigger phrases:
AWS S3 MCP Setup
{
"enabled": true,
"autoRun": false,
"timeout": 30000,
"retries": 3
}
Set environment variables as needed for authentication and endpoints.
Installation
{
"mcpServers": {
"s3": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-s3"],
"env": {
"AWS_ACCESS_KEY_ID": "${AWS_ACCESS_KEY_ID}",
"AWS_SECRET_ACCESS_KEY": "${AWS_SECRET_ACCESS_KEY}"
}
}
}
}
S3 Tools
s3.listBuckets()
s3.listObjects({
Bucket: "my-bucket",
Prefix: "documents/"
})
s3.uploadFile({
Bucket: "my-bucket",
Key: "backup/database.sql",
Body: fileContent,
ContentType: "application/sql"
})
s3.downloadFile({
Bucket: "my-bucket",
Key: "data/export.csv"
})
s3.copyObject({
Bucket: "destination-bucket",
CopySource: "source-bucket/old-file",
Key: "new-location/new-file"
})
s3.deleteObjects({
Bucket: "backups",
Keys: ["old-backup-1.tar", "old-backup-2.tar"]
})
Google Drive MCP Setup
{
"enabled": true,
"autoRun": false,
"timeout": 30000,
"retries": 3
}
Set environment variables as needed for authentication and endpoints.
Installation
{
"mcpServers": {
"gdrive": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-gdrive"],
"env": {
"GOOGLE_CLIENT_ID": "${GOOGLE_CLIENT_ID}",
"GOOGLE_CLIENT_SECRET": "${GOOGLE_CLIENT_SECRET}"
}
}
}
}
Google Drive Tools
gdrive.listFiles({
folderId: "root",
pageSize: 100
})
gdrive.uploadFile({
name: "report.pdf",
parents: ["folder-id"],
content: pdfBuffer,
mimeType: "application/pdf"
})
gdrive.createFolder({
name: "Backups",
parents: ["root"]
})
gdrive.createPermission({
fileId: "file-id",
type: "anyone",
role: "reader"
})
gdrive.getShareLink({
fileId: "file-id"
})
Dropbox MCP Setup
{
"enabled": true,
"autoRun": false,
"timeout": 30000,
"retries": 3
}
Set environment variables as needed for authentication and endpoints.
Installation
{
"mcpServers": {
"dropbox": {
"command": "npx",
"args": ["-y", "mcp-dropbox"],
"env": {
"DROPBOX_ACCESS_TOKEN": "${DROPBOX_ACCESS_TOKEN}"
}
}
}
}
Dropbox Tools
dropbox.listFolder({
path: "/backups"
})
dropbox.uploadFile({
path: "/backups/backup.zip",
contents: fileBuffer
})
dropbox.downloadFile({
path: "/documents/report.pdf"
})
dropbox.createSharedLink({
path: "/documents/report.pdf",
settings: { requested_visibility: "public" }
})
dropbox.move({
from: "/temp/file.txt",
to: "/archive/file.txt"
})
Use Cases
This section covers use cases for the storage-mcp skill.
Key operations include input validation, core processing, and output verification.
Refer to the skill overview for detailed usage instructions.
1. Automated Backups
Schedule: Daily 2 AM
Action:
1. Database dump
2. Compress
3. Upload to S3
4. Delete local
5. Notify success
2. Cross-Cloud Sync
Trigger: File change
Action:
1. Detect change
2. Upload to S3
3. Sync to Google Drive
4. Update metadata
3. Archive Management
Schedule: Monthly
Action:
1. Find old files
2. Compress
3. Move to cold storage
4. Update index
4. Content Distribution
Trigger: New upload
Action:
1. Upload to CDN
2. Generate URLs
3. Update database
4. Notify team
Backup Strategy
- Focus on high-impact, low-effort improvements first
- Measure before and after to validate changes
- Document learnings for future reference
- Share successful patterns across the skill portfolio
Incremental Backup
async function incrementalBackup() {
const lastBackup = await getLastBackupTimestamp();
const changes = await getChangesSince(lastBackup);
for (const change of changes) {
await s3.uploadFile({
Bucket: "backups",
Key: `incremental/${date}/${change.file}`,
Body: change.content
});
}
await updateLastBackupTimestamp(Date.now());
}
Versioning
s3.putBucketVersioning({
Bucket: "my-bucket",
VersioningConfiguration: {
Status: "Enabled"
}
})
Integration with 1ai-skills
- Connects with existing toolchain via standard interfaces
- Supports webhook-based event notifications
- Compatible with CI/CD pipelines for automated workflows
- Provides structured output for downstream consumption
With Database
database-mcp → storage-mcp → backup
↓ ↓
Export data Upload to S3
With Development
deployment → storage-mcp → artifacts
↓ ↓
Build Store binaries
Best Practices
This section covers best practices for the storage-mcp skill.
Key operations include input validation, core processing, and output verification.
Refer to the skill overview for detailed usage instructions.
Do's
✅ Enable versioning
✅ Use lifecycle policies
✅ Encrypt sensitive data
✅ Regular test restores
Don'ts
❌ Don't store credentials in files
❌ Don't skip encryption
❌ Don't ignore retention policies
Version History
- v1.0 (2026-02-27) - Initial creation
- S3, Google Drive, Dropbox support
Anti-Rationalization Table
| Rationalization | Reality |
|---|
| "I will handle auth later" | Retrofitting auth is 10x harder. Build it from day one. |
| "APIs do not change" | APIs change. Version your integrations and handle deprecations. |
| "Webhooks are optional" | Without webhooks, you miss real-time events. They are essential. |
Related Skills
How to Use
- Invoke the skill when relevant domain keywords appear in the request
- Provide required inputs as specified in the skill definition
- Review the output for correctness before delivering to the user
- Combine with related skills for complex multi-step workflows
Verification
After completing this skill, confirm:
Process
- Analyze the task requirements
- Apply domain expertise
- Verify output quality