Remote Filesystem
Expose Google Cloud Storage buckets to your agent as a remote filesystem for artifacts, uploads, and shared build outputs.
Overview
PulseMCP Remote Filesystem is an MCP server for the Build phase that performs filesystem-style operations on Google Cloud Storage from your agent.
What is this MCP server?
- Remote filesystem operations on Google Cloud Storage buckets
- Required GCS_BUCKET with optional GCS_ROOT_PATH prefix scoping
- Credentials via GOOGLE_APPLICATION_CREDENTIALS or inline GCS_CLIENT_EMAIL / GCS_PRIVATE_KEY
- Optional GCS_PROJECT_ID for project context
- stdio remote-filesystem-mcp-server 0.1.2 via npx -y
- Package version 0.1.2 (remote-filesystem-mcp-server)
- GCS_BUCKET is required
- Supports GOOGLE_APPLICATION_CREDENTIALS or inline GCS_CLIENT_EMAIL plus GCS_PRIVATE_KEY
What problem does it solve?
Agents and solo builders lack a safe, scoped way to read and write GCS objects without custom SDK scripts and scattered credentials.
Who is it for?
Indie builders already on GCP who want agent access to a single bucket for artifacts, assets, or pipeline files.
Skip if: Teams on AWS-only stacks, local-only workflows, or production setups that refuse service-account keys in the MCP host.
What do I get? / Deliverables
After setup, your agent can manage bucket objects under configured roots using standard MCP tools aligned to your GCS project.
- Agent-driven list/read/write operations within configured GCS scope
- Bucket access constrained by optional GCS_ROOT_PATH prefix
- Repeatable cloud file workflows without custom gsutil scripts
Recommended MCP Servers
Journey fit
How it compares
GCS-backed MCP storage integration, not a generic local filesystem or full IaC deploy skill.
Common Questions / FAQ
Who is PulseMCP Remote Filesystem for?
Solo builders and small teams using GCP buckets who want Claude Code, Cursor, or similar agents to perform storage operations via MCP.
When should I use PulseMCP Remote Filesystem?
Use it when building or operating workflows that store or retrieve files in GCS and you want those steps inside the agent instead of one-off CLI commands.
How do I add PulseMCP Remote Filesystem to my agent?
Register stdio remote-filesystem-mcp-server with npx -y, set GCS_BUCKET and credentials (key file or inline service account), optional GCS_ROOT_PATH, then reload MCP.