Gcs
Give agents controlled read, write, and delete access to Google Cloud Storage buckets and objects for app assets and data files.
Overview
com.pulsemcp/gcs is a MCP server for the Build phase that connects agents to Google Cloud Storage with readonly, readwrite, and delete tool groups.
What is this MCP server?
- Tool groups readonly, readwrite, and delete via GCS_ENABLED_TOOLGROUPS
- Auth via GCS_PROJECT_ID plus service account key file or inline JSON
- Optional GCS_BUCKET lock hides bucket-level tools for single-bucket workflows
- Per-tool allowlisting with GCS_ENABLED_TOOLS for tighter control
- gcs-google-mcp-server on npm with stdio npx entry
- Server version 0.1.8; npm identifier gcs-google-mcp-server
- 3 documented tool groups: readonly, readwrite, delete
- Optional GCS_ENABLED_TOOLS for per-tool filtering beyond groups
Community signal: 70 GitHub stars.
What problem does it solve?
Manually checking buckets and object paths in the GCP console breaks flow when your agent is already editing the code that uses GCS.
Who is it for?
Indie SaaS builders on GCP who store user files or static assets in GCS and want agent help without full console access.
Skip if: AWS-only S3 shops, teams forbidding service account keys in dev machines, or workflows needing multi-cloud abstractions.
What do I get? / Deliverables
Once registered with project and service account credentials, your agent can perform scoped GCS list, read, write, and delete operations in conversation.
- Scoped GCS bucket and object operations via readonly, readwrite, or delete groups
- Single-bucket mode when GCS_BUCKET is set
- Agent-ready cloud storage integration without custom MCP authoring
Recommended MCP Servers
Journey fit
GCS wiring happens while building features that store uploads, exports, or static assets in Google Cloud. Integrations is the right shelf for object-storage MCP tools that connect your product to a cloud provider API.
How it compares
GCS object-storage MCP bridge, not a media pipeline or Firebase skill.
Common Questions / FAQ
Who is com.pulsemcp/gcs for?
Builders using Google Cloud Storage with MCP agents who need fine-grained readonly or readwrite access to buckets and objects.
When should I use com.pulsemcp/gcs?
Use it while integrating uploads, exports, or asset storage during build, with delete tools only when you explicitly enable that group.
How do I add com.pulsemcp/gcs to my agent?
Add npx -y gcs-google-mcp-server, set GCS_PROJECT_ID and service account via GCS_SERVICE_ACCOUNT_KEY_FILE or GCS_SERVICE_ACCOUNT_KEY_JSON, then optional GCS_BUCKET and GCS_ENABLED_TOOLGROUPS.