All MCP Servers
Databases & StorageMCP RegistrynpmA · 83

remote-filesystem MCP server

com.pulsemcp · Updated

MCP server for remote filesystem operations on cloud storage (Google Cloud Storage).

At a glance

remote-filesystem is an MCP server in the Databases & Storage category. It runs locally over stdio via `npx -y remote-filesystem-mcp-server`, and needs GCS_BUCKET and GCS_PRIVATE_KEY. It scores A (83/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 81GitHub stars

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install remote-filesystem in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install remote-filesystem in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add remote-filesystem -e 'GCS_BUCKET=<GCS_BUCKET>' -e 'GCS_PRIVATE_KEY=<GCS_PRIVATE_KEY>' -- npx -y remote-filesystem-mcp-server
  2. Fill in your credentials

    Replace <GCS_BUCKET>, <GCS_PRIVATE_KEY> with your real values. Keep secrets out of any config file you commit.

  3. Verify it's connected

    bash
    claude mcp list
  4. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  5. Use it in a session

    Ask Claude to use the tools this server exposes. It discovers them automatically.

What does remote-filesystem need from you?

API key — Service account private key for inline credentials.

  • GCS_BUCKETrequiredEnvironment variable

    Google Cloud Storage bucket name.

  • GCS_PROJECT_IDoptionalEnvironment variable

    Google Cloud project ID.

  • GCS_CLIENT_EMAILoptionalEnvironment variable

    Service account email for inline credentials.

  • GCS_PRIVATE_KEYoptionalsecretEnvironment variable

    Service account private key for inline credentials.

  • GOOGLE_APPLICATION_CREDENTIALSoptionalEnvironment variable

    Path to Google Cloud service account key file.

  • GCS_ROOT_PATHoptionalEnvironment variable

    Root path prefix to restrict access within bucket.

  • GCS_MAKE_PUBLICoptionalEnvironment variable

    Make uploaded files publicly accessible.

  • ENABLED_TOOLGROUPSoptionalEnvironment variable

    Comma-separated tool groups: readonly or readwrite.

Pass secrets through your shell environment rather than committing them into a config file.

What tools does remote-filesystem expose?

This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.

What the code can do

Read from the published package source — never executed. Parsed 17 of 17 source files.

This server can read and write files, make network requests and read your environment variables.

How it was published

  • No provenance attestation — there is nothing linking this published artifact to a specific source commit.
  • 1 npm maintainer — a single point of compromise · last published by tadasant.

Maintainer of this package and think something here is wrong? Tell us and we'll correct it.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
  • Downloads at launch — The package is fetched from its registry each run unless you pin a version.
  • Last commit 19 days ago — Actively maintained.
  • 81 GitHub stars — Community adoption signal.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

A · 83

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%100%

    Last commit 19 days ago.

  • Adoption20%58%

    81 stars.

  • Transparency20%75%

    3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.

  • Provenance15%75%

    Links to its own repository; package linkage unverified.

  • Packaging15%100%

    Publishes a pinned version (0.1.5).

Documentation

Full README

PulseMCP's MCP Servers

We build reliable servers thoughtfully designed for MCP Client-powered workflows.

Design principles

You can have confidence that any Pulse-branded MCP server was built with these north stars in mind:

  1. Purpose-built. LLM-powered MCP clients offer uniquely new user interaction patterns that necessitate a different layer of abstraction than the REST API's from a pre-AI era. We thoughtfully scope drawing lines like building a new server, versus incorporating a new feature in another server. Or deciding where one slew of REST API endpoints might be better packaged as a single Tool call. And more.
  2. Easy set up. Many MCP servers die before ever getting a chance to be used. We offer guides and a frustration-free experience to get going with our MCP servers inside your favorite MCP clients.
  3. Time savings. By minimizing the number of tool chain steps or conversational turns you need to accomplish a task, our MCP servers will save you (and your agents) time waiting for a task to be completed.
  4. Inference cost savings. By minimizing the number of tokens you need to consume to a accomplish a task, our MCP servers will save you on your LLM inference bills.
  5. Reliability. You should have confidence that you can deploy our servers in a production application serving mass market consumers or business clients.
  6. Future-proof. We sit on the bleeding edge of the MCP specification, working to push the ecosystem forward. As such, you can be sure that if you commit to baking our server into your workflow, it will self-improve over time to take advantage of the latest and greatest MCP features.

Servers Available

Productionized Servers

These are PulseMCP-branded servers that we intend to maintain indefinitely as our own offerings.

The MCP Registry column controls whether the server is published to the official MCP Registry (com.pulsemcp/<server-name>) by the publish-mcp-registry.yml workflow.

| Name | Description | Local Status | Remote Status | MCP Registry | Target Audience | Notes | | -------------------------------------------------------- | ------------------------------------ | ------------ | ------------- | ------------ | ------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------- | | pulse-fetch | Pull internet resources into context | 0.3.3 | Not Started | Yes | Agent-building frameworks (e.g. fast-agent, Mastra, PydanticAI) and MCP clients without built-in fetch | Supports Firecrawl and BrightData integrations; HTML noise stripping; Resource caching; LLM extraction | | pulse-subregistry | Browse the PulseMCP Sub-Registry | 0.0.8 | Not Started | Yes | Developers discovering MCP servers from the PulseMCP Sub-Registry | Search and pagination; Version selection; Integrates with PulseMCP Sub-Registry API | | image-diff | Programmatic image comparison | 0.1.3 | Not Started | Yes | Developers comparing design mocks against UI implementations | Pixel-level diff with clustering; Heatmap visualization; Anti-aliasing detection; Auto-alignment for different-sized images | | svg-tracer | Bitmap-to-SVG vector tracing | 0.1.3 | Not Started | Yes | Developers converting bitmap images to SVG vector graphics | Supports PNG, JPG, WebP, BMP, GIF, TIFF; Alpha channel preprocessing; Target size scaling; Customizable tracing parameters |

Experimental Servers

These are high-quality servers that we may discontinue if the official provider creates and maintains a better MCP server.

| Name | Description | Local Status | Remote Status | MCP Registry | Target Audience | Notes | | -------------------------------------------------------- | ------------------------------------------------------------------------------ | ------------ | ------------- | ------------ | --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | agent-orchestrator | Agent parallelization system for agentic coding and ops | 0.8.12 | Not Started | No | PulseMCP team for agent orchestration | Requires AGENT_ORCHESTRATOR_BASE_URL and API_KEY; Internal use only | | appsignal | AppSignal application performance monitoring and error tracking | 0.5.4 | Not Started | Yes | Developers using AppSignal for application monitoring | Requires AppSignal API key; NOT officially affiliated with AppSigna

…

Excerpt — the full document is on GitHub.

Maintain remote-filesystem? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![remote-filesystem on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/com-pulsemcp-remote-filesystem)](https://mcp-skills-hub.vercel.app/mcps/com-pulsemcp-remote-filesystem)

Catalog data refreshed . Something wrong? Report it.