概览
What is File Store MCP Server?
A file storage service that supports multiple cloud providers, providing a unified API for uploading files and generating presigned URLs. It integrates with AWS S3, Alibaba Cloud OSS, Tencent Cloud COS, Qiniu Cloud, and GitHub, and is intended for developers who need to upload local, clipboard, or URL-based files to cloud storage for online access.
How to use File Store MCP Server?
Install via go install github.com/sjzar/file-store-mcp@latest, set environment variables for your chosen storage provider, then run in stdio mode (file-store-mcp) or SSE server mode (file-store-mcp --sse-port 8080). The server exposes three tools: upload_files, upload_clipboard_files, and upload_url_files.
Key features of File Store MCP Server
- Multi-cloud storage provider support
- Unified API for file uploads
- Presigned URL generation for secure access
- Dual operation modes: stdio and SSE
- Custom domains and CDN support
- Configurable URL expiration times
Use cases of File Store MCP Server
- Uploading local PDFs or images for AI analysis
- Sharing clipboard content as online URLs without saving locally
- Processing web-hosted files by downloading and re-uploading them
- Integrating file storage into MCP-compatible applications
FAQ from File Store MCP Server
What storage providers does File Store MCP Server support?
AWS S3 (and compatible services like Cloudflare R2), Alibaba Cloud OSS, Tencent Cloud COS, Qiniu Cloud Storage, and GitHub Repository.
What are the runtime requirements for File Store MCP Server?
It requires Go to build from source and environment variables configured per storage provider. No other runtime dependencies are mentioned.
Where do uploaded files get stored?
Files are uploaded to the configured cloud storage bucket/repository, and HTTP URLs (presigned or public) are returned.
Does File Store MCP Server support custom domains?
Yes. All storage providers accept custom domain configuration to serve files via CDN or custom endpoints.
What transport modes are available?
Stdio mode for direct integration and SSE mode (via --sse-port) for HTTP-based server integration.
