Ext Ops Panel
Open dashboard
Comparison

google-cloud-storage vs io.github.AIBOLLINGMO/eustore

google-cloud-storage is a plugin bundle for AI coding tools published by gemini-cli-extensions. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Community GitHub marketplaces). io.github.AIBOLLINGMO/eustore is an MCP server published by AIBOLLINGMO. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacegoogle-cloud-storageio.github.AIBOLLINGMO/eustore
Claude Code: claude-plugins-official Listed
Version: 1.1.0
Forks (GitHub): 3
Stars (GitHub): 31
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.2
Downloads/month (PyPI): 156
Downloads/week (PyPI): 70
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

google-cloud-storage vs io.github.AIBOLLINGMO/eustore
Factgoogle-cloud-storageio.github.AIBOLLINGMO/eustore
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)31No figure on GitHub
Forks (GitHub) (differs)3No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@toolbox-sdk/server)On your machine (eustore)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Parts of the bundle (differs)8Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/gemini-cli-extensions/google-cloud-storagegithub.com/aibollingmo/eustore
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

google-cloud-storage

In its own words, on Claude Code: claude-plugins-official:

Official Google Cloud Storage (GCS) plugin. Manage buckets and objects, transfer data, and configure MCP, FUSE, IAM, security, lifecycle rules, signed URLs, Terraform, and the CLI.

io.github.AIBOLLINGMO/eustore

In its own words, on Official MCP Registry:

S3-compatible European object storage for AI agents. GDPR-compliant, EU-hosted, crypto payments.

How to run each

google-cloud-storage As a Claude Code plugin

Claude Code
/plugin install google-cloud-storage@claude-plugins-official

io.github.AIBOLLINGMO/eustore As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio eustore -- uvx eustore

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of io.github.AIBOLLINGMO/eustore publish no settings it asks for, so we do not compare settings.

What it can do: google-cloud-storage · What it can do: io.github.AIBOLLINGMO/eustore · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built