MCP Server Cloud Fs

MCP Server Cloud Fs runs locally from a Node.js package published to the npm registry: @nogoo9/mcp-server-cloud-fs version 0.7.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @nogoo9/mcp-server-cloud-fs@0.7.0; the entry names bunx as the runtime. It reads these environment variables: AZURE_STORAGE_CONNECTION_STRING (secret), GOOGLE_CLOUD_PROJECT, AWS_ACCESS_KEY_ID (secret), AWS_SECRET_ACCESS_KEY (secret) and REDIS_URL; set them in the client's configuration for this server. Required arguments: s3|azure|gcs and s3://bucket[/prefix].

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "mcp-server-cloud-fs": {
      "command": "npx",
      "args": [
        "-y",
        "@nogoo9/mcp-server-cloud-fs@0.7.0"
      ],
      "env": {
        "AZURE_STORAGE_CONNECTION_STRING": "<secret>",
        "GOOGLE_CLOUD_PROJECT": "<value>",
        "AWS_ACCESS_KEY_ID": "<secret>",
        "AWS_SECRET_ACCESS_KEY": "<secret>",
        "REDIS_URL": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect