How do I install Remote Filesystem?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Remote Filesystem need an API key?

The publisher lists these environment variables: GCS_BUCKET, GCS_PROJECT_ID, GCS_CLIENT_EMAIL, GCS_PRIVATE_KEY, GOOGLE_APPLICATION_CREDENTIALS, GCS_ROOT_PATH, GCS_MAKE_PUBLIC, ENABLED_TOOLGROUPS.

What transport does Remote Filesystem use?

Remote Filesystem runs locally over stdio.

When was Remote Filesystem last checked?

Last checked 2026-11-08. MCP server for remote filesystem operations on cloud storage (Google Cloud Storage).

Remote Filesystem MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y [email protected]

Credentials from the publisher

GCS_BUCKET — Google Cloud Storage bucket name.
GCS_PROJECT_ID — Google Cloud project ID.
GCS_CLIENT_EMAIL — Service account email for inline credentials.
GCS_PRIVATE_KEY — Service account private key for inline credentials.
GOOGLE_APPLICATION_CREDENTIALS — Path to Google Cloud service account key file.
GCS_ROOT_PATH — Root path prefix to restrict access within bucket.
GCS_MAKE_PUBLIC — Make uploaded files publicly accessible.
ENABLED_TOOLGROUPS — Comma-separated tool groups: readonly or readwrite.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1GCS_BUCKET=<value> GCS_PROJECT_ID=<value> GCS_CLIENT_EMAIL=<value> GCS_PRIVATE_KEY=<secret> GOOGLE_APPLICATION_CREDENTIALS=<value> GCS_ROOT_PATH=<value> GCS_MAKE_PUBLIC=<value> ENABLED_TOOLGROUPS=<value> claude mcp add com.pulsemcp-remote-filesystem -- npx -y remote-filesystem-mcp-server@0.1.5

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "com.pulsemcp-remote-filesystem": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ],9      "env": {10        "GCS_BUCKET": "<value>",11        "GCS_PROJECT_ID": "<value>",12        "GCS_CLIENT_EMAIL": "<value>",13        "GCS_PRIVATE_KEY": "<secret>",14        "GOOGLE_APPLICATION_CREDENTIALS": "<value>",15        "GCS_ROOT_PATH": "<value>",16        "GCS_MAKE_PUBLIC": "<value>",17        "ENABLED_TOOLGROUPS": "<value>"18      }19    }20  }21}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

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:

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.

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.

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.

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.

Reliability. You should have confidence that you can deploy our servers in a production application serving mass market consumers or business clients.

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 AppSignal
claude-code-agent	Claude Code Agent MCP Server for managing Claude Code CLI sessions	0.0.8	Not Started	No	Developers building AI-powered automation workflows	Requires Claude Code CLI installed locally
dynamodb	AWS DynamoDB table and item operations with fine-grained access	0.2.7	Not Started	Yes	Developers using AWS DynamoDB	Requires AWS credentials; Fine-grained tool access control
remote-filesystem	Remote filesystem operations on cloud storage (GCS)	0.1.5	Not Started	Yes	Developers needing cloud storage integration	Requires GCS credentials; Full CRUD operations; Published as `remote-filesystem-mcp-server`
s3	AWS S3 bucket and object management	0.0.5	Not Started	Yes	Developers needing S3 storage integration	Requires AWS credentials; Fine-grained tool access control; Published as

Contributing

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Remote Filesystem?

Does Remote Filesystem need an API key?

What transport does Remote Filesystem use?

When was Remote Filesystem last checked?

Documentation

PulseMCP's MCP Servers

Design principles

Servers Available

Productionized Servers

Experimental Servers

Contributing