MCP Server Cloud Fs

Name: MCP Server Cloud Fs
Author: nogoo9

by nogoo9version 0.7.0i★ –iRuns on your computer

Registry nameio.github.nogoo9/mcp-server-cloud-fs

Install

Overview

Description from the maker (original English)

Cloud replacement for mcp-server-filesystem — 20 tools for S3, Azure Blob, and GCS

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Developer tools
You need to fill in: AZURE_STORAGE_CONNECTION_STRING, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: AZURE_STORAGE_CONNECTION_STRING, GOOGLE_CLOUD_PROJECT, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, REDIS_URL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add cloud-fs --env AZURE_STORAGE_CONNECTION_STRING=your-value --env GOOGLE_CLOUD_PROJECT=your-value --env AWS_ACCESS_KEY_ID=your-value --env AWS_SECRET_ACCESS_KEY=your-value --env REDIS_URL=your-value -- npx -y @nogoo9/mcp-server-cloud-fs

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "cloud-fs": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@nogoo9/mcp-server-cloud-fs"
      ],
      "env": {
        "AZURE_STORAGE_CONNECTION_STRING": "your-value",
        "GOOGLE_CLOUD_PROJECT": "your-value",
        "AWS_ACCESS_KEY_ID": "your-value",
        "AWS_SECRET_ACCESS_KEY": "your-value",
        "REDIS_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

AZURE_STORAGE_CONNECTION_STRING secret env
Azure Blob Storage connection string (required when using the azure provider)
GOOGLE_CLOUD_PROJECT env
Google Cloud project ID (optional when using the gcs provider)
AWS_ACCESS_KEY_ID secret env
AWS Access Key ID (optional for S3 — falls back to ~/.aws/credentials or IAM role)
AWS_SECRET_ACCESS_KEY secret env
AWS Secret Access Key (optional for S3 — falls back to ~/.aws/credentials or IAM role)
REDIS_URL env
Redis connection URL (required when --cache-store redis, defaults to redis://localhost:6379)

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account nogoo9, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

More stars than 0% of the other 1395 servers in this category
Published to the registry more recently than 22% of the other 1395 servers in this category
Basic checks equal to or better than 100% of the other 1395 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MCP Server Cloud Fs safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: AZURE_STORAGE_CONNECTION_STRING, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.7.0) reached the registry 6 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 4 days ago

Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 16 days ago

Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@nogoo9/mcp-server-cloud-fs

Cloud replacement for mcp-server-filesystem — 30 tools for S3, Azure Blob, and GCS.

Deploy locally via STDIO or remotely over HTTP/WebSocket with OAuth 2.1 auth.

Also available as an npm library and interactive TUI.

📖 Read the full documentation →

Providers: Amazon S3 · Azure Blob Storage · Google Cloud Storage · MinIO · RustFS · Cloudflare R2 · Backblaze B2 · Wasabi · LocalStack · SQLite · In-Memory

What it does
Quick start
Interactive Shell
Transports
Authentication & Authorization
Production Features
CLI Reference
Provider Setup
MCP Client Config
Tool Reference
Architecture: VFS
Caching
Programmatic Usage
MCP Inspector
Development & Testing
AI Agent Skill
Documentation
License

What it does

@nogoo9/mcp-server-cloud-fs exposes all 14 tools defined by mcp-server-filesystem — same tool names, same parameter schemas — over cloud object storage. Drop it into any MCP client config that currently points at mcp-server-filesystem and your AI assistant gains read/write access to S3, Azure Blob Storage, or Google Cloud Storage buckets.

It also includes 5 extended tools inspired by claude-code's filesystem tool surface: line-range reads, byte-range chunk reads, in-process regex search (single file and multi-file), server-side copy, and opt-in deletion. Plus 6 cloud-native tools (presigned URLs, object metadata/tags, tag-based search, version history, version restore), 2 AI-native tools (schema extraction, file summarization), and 1 macro tool (patch_file for atomic diffs).

A Virtual Filesystem (VFS) layer provides FUSE-like cache coherence with ETag-based concurrency control, a shell tool lets you run POSIX-like commands (ls, grep, jq, cat | wc, etc.) against cloud storage, and the package is available as a programmatic npm library.

v0.7.0 Highlights

Dynamic tool surface reduction: scope-aware tool filtering — clients only see tools they're authorized to use
DLP content sanitization: regex-based middleware redacts PII, API keys, and credentials from tool responses (--enable-dlp)
AI-native tools: get_file_schema extracts CSV/JSON structure; summarize_file returns compact head/tail previews
ETag concurrency control: SHA-256 content-addressable ETags with expected_etag conflict detection on edit_file and patch_file
`patch_file` macro tool: atomic read-diff-write in a single tool call — supports unified diffs and line-range replacements

v0.6.0 Highlights

Cloud-native tools: presigned URLs, object metadata/tags, version history, version restore
Byte-range reads: read_file_chunk fetches specific byte ranges without downloading the full object
Structured audit logging: tool invocation audit trail with pluggable sinks (stderr, file)
Multi-provider routing: MultiProvider serves S3 + Azure + GCS from a single server instance
Azure Managed Identity: DefaultAzureCredential for OIDC and federated auth
Connection health-check: startup credential validation with diagnostic reporting
MCP Resources: browse cloud storage as native MCP Resources (no tool calls needed)
Structured errors: CloudError with typed codes and provider-specific error mappers

v0.5.0 Highlights

Interactive TUI (`cloud-fs`): Terminal shell with cd, tab completion, and command history
Multi-transport: STDIO (default), Streamable HTTP, and WebSocket
Dual runtime: Bun-native and Node.js support (HTTP transport + SQLite provider)
OAuth 2.1: Built-in auth server or external IdP token validation
ext-auth extensions: Client Credentials (M2M) and Enterprise-Managed Authorization (SSO)
Production hardening: Rate limiting, CORS, security headers, health checks, structured logging
AI agent skill: Installable skills/cloud-fs for Claude Code, Gemini CLI, and other AI assistants

Quick start

Local (STDIO — default)

npx @nogoo9/mcp-server-cloud-fs s3 s3://my-bucket

Remote (HTTP)

# Bun (zero Express dependency)

bunx @nogoo9/mcp-server-cloud-fs s3 s3://my-bucket --transport http --port 3000

Node.js (requires express peer dep)

npx @nogoo9/mcp-server-cloud-fs s3 s3://my-bucket --transport http --port 3000

Remote (WebSocket — Bun only)

bunx @nogoo9/mcp-server-cloud-fs s3 s3://my-bucket --transport ws --port 3000

Demo (no cloud credentials needed)

bunx @nogoo9/mcp-server-cloud-fs memory mem://demo --enable-shell --seed-demo

Interactive Shell (`cloud-fs`)

Drop into an interactive terminal for exploring and managing cloud storage — no MCP client needed:

# S3

npx -p @nogoo9/mcp-server-cloud-fs cloud-fs s3 s3://my-bucket

In-memory demo with sample files

npx -p @nogoo9/mcp-server-cloud-fs cloud-fs memory mem://demo --seed-demo

With a config file (cloud-fs.json in CWD)

npx -p @nogoo9/mcp-server-cloud-fs cloud-fs

Features

`cd` navigation — cd data, cd .., cd / with dynamic prompt showing current directory
Tab completion — context-aware path and command completion
Command history — persistent across sessions (~/.cloud-fs_history)
Relative paths — all commands resolve relative to cwd, just like a real shell
19 built-in commands — ls, cat, head, tail, cp, mv, rm, mkdir, touch, stat, find, grep, wc, du, echo, tee, diff, jq, cd
Pipes & redirects — cat config.json | jq '.database', echo hello > file.txt

Local development

bun src/cli-tui.ts memory mem://demo --seed-demo

Transports

The server supports three MCP transports, selected via --transport:

Transport	Flag	Runtime	Use case
STDIO	`--transport stdio` (default)	Bun, Node	Local `npx`, Claude Desktop, Claude Code
Streamable HTTP	`--transport http`	Bun ✅, Node ✅	Remote deployment, multi-user, enterprise
WebSocket	`--transport ws`	Bun only	Low-latency bidirectional, real-time apps

Streamable HTTP

Implements the MCP Streamable HTTP specification with a single /mcp endpoint for POST (requests), GET (SSE notifications), and DELETE (session termination).

Dual runtime support:

Bun: Uses WebStandardStreamableHTTPServerTransport with Bun.serve() directly — zero Express dependency, maximum performance.
Node.js: Falls back to StreamableHTTPServerTransport with Express. Requires express as an optional peer dependency (npm install express).

Runtime is auto-detected at startup.

Session management:

Sessions use UUID v7 (RFC 9562) — time-ordered and K-sortable, making them ideal for logging, debugging, and database indexing. Sessions are tracked via the Mcp-Session-Id header.

Resumability:

When an EventStore is configured, clients can reconnect and resume receiving messages from where they left off via the Last-Event-ID SSE header.

# Basic HTTP server

cloud-fs-mcp s3 s3://my-bucket --transport http --port 3000

With authentication

cloud-fs-mcp s3 s3://my-bucket --transport http --port 3000 --auth builtin --auth-issuer https://my-server.example.com

Production deployment

cloud-fs-mcp s3 s3://my-bucket \ --transport http --port 3000 --host 0.0.0.0 \ --auth external --auth-jwks-uri https://login.example.com/.well-known/jwks.json \ --cors-origin https://app.example.com \ --rate-limit 60 --rate-limit-burst 10 \ --security-headers \ --request-logging

WebSocket

Bun-native WebSocket transport using Bun.serve() with WebSocket upgrade handling. Provides lower latency than HTTP for high-frequency tool invocations.

JSON-RPC message framing over WebSocket
UUID v7 session assigned on upgrade
WS ping/pong heartbeat for connection liveness

cloud-fs-mcp s3 s3://my-bucket --transport ws --port 3000

Authentication & Authorization

Authentication is disabled by default and only applies to HTTP/WS transports. STDIO mode never requires auth.

Auth modes

Mode	Flag	Description
`none`	`--auth none` (default)	No authentication. Suitable for local/trusted networks.
`builtin`	`--auth builtin`	Self-hosted OAuth 2.1 Authorization Server. The MCP server acts as both AS and RS.
`external`	`--auth external`	Validate bearer tokens against an external IdP (Okta, Auth0, Keycloak, Azure AD).

Built-in OAuth server (`--auth builtin`)

The server runs a full OAuth 2.1 Authorization Server using the MCP SDK's mcpAuthRouter():

Authorization Code + PKCE (mandatory) — interactive user consent flow
Dynamic Client Registration — MCP clients auto-register on first connect
Refresh token rotation — single-use refresh tokens prevent replay
Metadata discovery — /.well-known/oauth-authorization-server (RFC 8414) and /.well-known/oauth-protected-resource (RFC 9728)

cloud-fs-mcp s3 s3://my-bucket \

--transport http --port 3000 \ --auth builtin --auth-issuer https://my-server.example.com

External IdP (`--auth external`)

The server only validates bearer tokens — it does not issue tokens. Use this when you have an existing identity provider.

JWKS validation — fetches and caches signing keys from your IdP
JWT verification — checks signature, issuer,

Only the beginning is shown; read the rest in the repo

MCP Server Cloud Fs

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

Table of Contents

What it does

v0.7.0 Highlights

v0.6.0 Highlights

v0.5.0 Highlights

Quick start

Local (STDIO — default)

Remote (HTTP)

Node.js (requires express peer dep)

Remote (WebSocket — Bun only)

Demo (no cloud credentials needed)

Interactive Shell (cloud-fs)

In-memory demo with sample files

With a config file (cloud-fs.json in CWD)

Features

Local development

Transports

Streamable HTTP

With authentication

Production deployment

WebSocket

Authentication & Authorization

Auth modes

Built-in OAuth server (--auth builtin)

External IdP (--auth external)

Interactive Shell (`cloud-fs`)

Built-in OAuth server (`--auth builtin`)

External IdP (`--auth external`)