Provides tools for uploading, listing, and managing files on AWS S3 buckets, including public and private file handling with temporary URLs.
Supports DigitalOcean Spaces as an S3-compatible storage provider for file management operations.
Allows integration with MinIO or other S3-compatible storage services for file upload, listing, and URL generation.
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., "@saveformedearai upload the file README.md to my documents"
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.
A Model Context Protocol (MCP) server for managing files on S3 storage, supporting AWS S3 and DigitalOcean Spaces.
🚀 Upload public and private files with metadata
📋 List files with descriptions and information
🔗 Immediate URL access - URLs returned directly in upload response
🌍 Global and local configuration for projects
⚡ Multi-provider support (AWS S3, DigitalOcean Spaces, S3-compatible)
🎯 Claude Code integration via MCP
Related MCP server: @zhigang1992/uploadfile-mcp
npm install -g saveformedearaigit clone https://github.com/bramato/saveForMeDearAi.git
cd saveForMeDearAi
npm install
npm run build
npm install -g .Install and configure:
npm install -g saveformedearai
saveformedearai setupAdd to Claude MCP config:
{
"mcpServers": {
"saveformedearai": {
"command": "saveformedearai"
}
}
}# Configure S3 drive (global)
saveformedearai setup
# Initialize local project
saveformedearai init
# Start MCP server (automatic when called by Claude)
saveformedearaiSaved in ~/.saveformedearai/config.json:
{
"defaultDrive": "my-aws-drive",
"drives": {
"my-aws-drive": {
"endpoint": "https://s3.amazonaws.com",
"region": "us-east-1",
"accessKeyId": "YOUR_ACCESS_KEY",
"secretAccessKey": "YOUR_SECRET_KEY",
"bucketName": "my-bucket"
}
}
}Saved in .claude/saveformedearai.json:
{
"driveName": "my-project-drive",
"projectDirectory": "my-project",
"s3Config": {
"endpoint": "https://nyc3.digitaloceanspaces.com",
"region": "nyc3",
"accessKeyId": "YOUR_DO_KEY",
"secretAccessKey": "YOUR_DO_SECRET",
"bucketName": "my-space"
}
}save_public_fileSave a file as public and return the permanent URL.
{
"filePath": "/path/to/file.jpg",
"filename": "optional-custom-name.jpg", // optional
"description": "File description" // optional
}Response:
{
"success": true,
"url": "https://bucket.endpoint.com/file.jpg",
"key": "file.jpg",
"urlType": "permanent",
"isPublic": true,
"message": "File uploaded successfully as public file. URL: https://bucket.endpoint.com/file.jpg",
"driveName": "my-drive"
}save_private_fileSave a file as private.
{
"filePath": "/path/to/private-file.pdf",
"filename": "document.pdf",
"description": "Private document"
}Response:
{
"success": true,
"key": "document.pdf",
"url": "https://presigned-url...",
"temporaryUrl": "https://presigned-url...",
"urlType": "temporary",
"expiresIn": 3600,
"expirationDate": "2024-01-15T11:30:00Z",
"message": "File uploaded successfully as private file. Temporary URL provided (expires in 1 hour).",
"driveName": "my-drive"
}list_filesList all files with metadata.
{
"prefix": "images/" // optional, filter by prefix
}Response:
{
"success": true,
"files": [
{
"filename": "image.jpg",
"description": "Sample photo",
"uploadDate": "2024-01-15T10:30:00Z",
"isPublic": true,
"size": 1024000,
"contentType": "image/jpeg",
"sizeFormatted": "1.02 MB"
}
],
"count": 1,
"driveName": "my-drive"
}get_file_urlGet URL for a file (permanent for public, temporary for private).
{
"filename": "document.pdf",
"expiresIn": 3600 // optional, seconds (max 7 days)
}Response for public file:
{
"success": true,
"url": "https://bucket.endpoint.com/document.pdf",
"urlType": "permanent",
"isPublic": true,
"filename": "document.pdf"
}Response for private file:
{
"success": true,
"url": "https://presigned-url...",
"urlType": "temporary",
"isPublic": false,
"expiresIn": 3600,
"expirationDate": "2024-01-15T11:30:00Z"
}Endpoint: https://s3.amazonaws.com
Force Path Style: falseEndpoint: https://[region].digitaloceanspaces.com
Force Path Style: falseEndpoint: https://your-endpoint.com
Force Path Style: true (typically)# Clone repository
git clone https://github.com/bramato/saveForMeDearAi.git
cd saveForMeDearAi
# Install dependencies
npm install
# Build
npm run build
# Development with watch
npm run dev
# Test locally
npm startRun saveformedearai setup to configure an S3 drive.
Verify:
Correct credentials
Correct endpoint for provider
Bucket exists and is accessible
Adequate permissions (read/write for bucket)
Use list_files to verify file names in the bucket.
MIT
Contributions are welcome! Please open an issue or pull request.
Love coding with chill vibes? Support this project by listening to my developer album:
Perfect background music for your coding sessions
Every stream helps support the development of free tools like this one! 🙏
Get a temporary or permanent URL for a file. For public files, returns permanent URL. For private files, returns temporary presigned URL.
Inputs: filename (required), expiresIn.
List all files stored in the S3 bucket with their metadata including descriptions.
Inputs: prefix.
Save a file to S3 storage as private. Use get_file_url to get temporary access URLs.
Inputs: filePath (required), filename, description.
Save a file to S3 storage and make it publicly accessible. Returns the public URL.
Inputs: filePath (required), filename, description.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 4 tools
Each tool has a distinct purpose: saving public/private files with different access semantics, listing files, and retrieving URLs. The only minor overlap is that save_public_file also returns a URL, but its primary action (saving) is clearly differentiated from get_file_url (retrieving URLs for existing files).
All tool names use snake_case and follow a verb_noun pattern (save_public_file, save_private_file, list_files, get_file_url). The convention is predictable and consistent throughout.
Four tools is a well-scoped set for a focused S3 file storage server, covering the core operations of saving, listing, and URL retrieval without unnecessary bloat.
The surface covers save (public/private), list, and URL retrieval, but lacks any delete or update/replace operation, which are important for a file storage lifecycle. There is also no way to set file descriptions or metadata despite list_files returning them.
An MCP server for the STRG.com s3-compatible object storage network for all management operations. Full documentation access, ask questions, create buckets, configure scoped access keys, CORS rules, lifecycle policies and perform any S3 operation.
MCP server for the FFmpeg Micro video transcoding API — create, monitor, download transcodes.
MCP server for interacting with the Supabase platform
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
