An MCP server that exposes the same 14 tools and schemas as `mcp-server-filesystem`, but stores files in cloud object storage instead of local disk. It supports S3, Azure Blob Storage, and Google Cloud Storage, with optional caching and sync flush behavior.
From the registry: Cloud replacement for mcp-server-filesystem — 20 tools for S3, Azure Blob, and GCS
Please install the `mcp-server-cloud-fs` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Node.js and npx** — Install Node.js so you can run the server with npx. (https://nodejs.org/)
- **Cloud provider credentials** — Configure credentials using the provider SDK credential chain. For AWS S3, use the standard AWS credential chain. For Azure Blob Storage, use DefaultAzureCredential. For Google Cloud Storage, use Application Default Credentials.
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","@nogoo9/mcp-server-cloud-fs","s3","s3://<your-bucket>"]
- optional environment variables:
- `AWS_ACCESS_KEY_ID`: AWS access key ID for S3 or S3-compatible backends when using environment-based AWS credentials. (example: `<your-aws-access-key-id>`)
- `AWS_SECRET_ACCESS_KEY`: AWS secret access key for S3 or S3-compatible backends when using environment-based AWS credentials. (example: `<your-aws-secret-access-key>`)
- `AZURE_TENANT_ID`: Azure tenant ID when using service principal authentication via DefaultAzureCredential. (example: `<your-azure-tenant-id>`)
- `AZURE_CLIENT_ID`: Azure client ID when using service principal authentication via DefaultAzureCredential. (example: `<your-azure-client-id>`)
- `AZURE_CLIENT_SECRET`: Azure client secret when using service principal authentication via DefaultAzureCredential. (example: `<your-azure-client-secret>`)
- `GOOGLE_APPLICATION_CREDENTIALS`: Path to Google Cloud service account credentials JSON for Application Default Credentials. (example: `<path-to-your-gcp-credentials-json>`)
- `REDIS_URL`: Redis connection URL when using --cache-store redis. (example: `redis://<your-redis-host>:<your-redis-port>`)
Note: The server is configured via stdio. Replace the provider and root URI as needed: s3 with s3://<your-bucket>, azure with az://<your-container>, or gcs with gs://<your-bucket>. Optional CLI args may be added to args, including --region <region>, --endpoint <url> for S3-compatible backends, --cache-store <memory|fs|redis>, --cache-ttl <seconds>, --sync-debounce <ms>, --cache-dir <path>, or --no-cache. Credentials are not passed as CLI flags; they come from the relevant SDK credential chain.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.AWS_ACCESS_KEY_IDrequiredAWS/S3 access key used by the standard AWS credential chainAWS_SECRET_ACCESS_KEYrequiredAWS/S3 secret access key used by the standard AWS credential chainAZURE_TENANT_IDrequiredUsed by Azure DefaultAzureCredential for Azure Blob Storage authenticationAZURE_CLIENT_IDrequiredUsed by Azure DefaultAzureCredential for Azure Blob Storage authenticationAZURE_CLIENT_SECRETrequiredUsed by Azure DefaultAzureCredential for Azure Blob Storage authenticationGOOGLE_APPLICATION_CREDENTIALSrequiredPath to Google Cloud service account credentials for Application Default CredentialsREDIS_URLrequiredRedis connection URL when using the Redis cache backendAn MCP Server for computer-use in Windows OS