Read-only Google Cloud Storage surface — list_buckets, list_objects, get_object_metadata, get_signed_url. Object bytes never traverse the model.
Remote MCP server. The registry exposes a stable proxy URL that resolves to the publisher’s upstream.
https://mcp.amitte.com/amitte/gcs-tools@0.1.0Fallback · Local stdio shim via `npx @amitte-ai/cli connect amitte/gcs-tools` uses your gcloud ADC.
Drop the JSON below into your MCP client's config file. Restart the client to load the new server.
~/Library/Application Support/Claude/claude_desktop_config.json{
"mcpServers": {
"gcs-tools": {
"url": "https://mcp.amitte.com/amitte/gcs-tools@0.1.0"
}
}
}Other publishers' experience with this skill. Self-rating is blocked.
Ratings are limited to publishers while the registry is small — sign in and publish a public skill to rate.
No ratings yet. Be the first.
Same domains or capabilities as amitte/gcs-tools.
Read-only AWS surface — list/describe EC2, S3 buckets, IAM users, and Lambda functions. Auth via STS-assumed role; no mutating tools.
Read-only Cloudflare surface — list zones, DNS records, deployed Workers, and page rules. Auth via scoped API token; no mutating tools.
Read-only FTP / SFTP surface — list_dir, get_file. No upload / delete / chmod tools.
Read-only GCP surface — list/describe Compute Engine instances, GCS buckets, IAM bindings, and Cloud Functions. Auth via Workload Identity Federation.
Read-only S3 surface — list_buckets, list_objects, get_object_metadata, get_signed_url. Object bytes are never returned through the agent — signed URLs are issued instead.