Ext Ops Panel
Open dashboard
Comparison

data-agent-kit vs Wherobots

data-agent-kit is a plugin bundle for AI coding tools published by GoogleCloudPlatform. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-official). Wherobots is an MCP server published by wherobots.com. 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
Marketplacedata-agent-kitWherobots
Claude Code: claude-plugins-official Listed
Version: 1.0.0
Forks (GitHub): 69
Stars (GitHub): 219
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
No figure published
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

data-agent-kit vs Wherobots
Factdata-agent-kitWherobots
Marketplaces that list it11
Stars (GitHub) (differs)219No figure on GitHub
Forks (GitHub) (differs)69No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.cloud.wherobots.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)50Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/googlecloudplatform/data-agent-kit-pluginNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

data-agent-kit

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

This plugin provides a specialized suite of skills for data engineers and database practitioners working on Google Cloud. It acts as an expert assistant, allowing you to use natural language prompts in your preferred coding agent to architect complex data pipelines, transform data with dbt, write Spark and BigQuery SQL notebooks, and orchestrate end-to-end workflows across GCP's data ecosystem.

Wherobots

In its own words, on Official MCP Registry:

Generate and run high performance queries on open and private spatial data at-scale in the cloud

How to run each

data-agent-kit As a Claude Code plugin

Claude Code
/plugin install data-agent-kit@claude-plugins-official

Wherobots As a remote MCP server

Claude Code
claude mcp add --transport http wherobots https://api.cloud.wherobots.com/mcp/ --header "X-API-Key: <YOUR_X_API_KEY>"

Requires: X-API-Key header

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 Wherobots publish no settings it asks for, so we do not compare settings.

What it can do: data-agent-kit · What it can do: Wherobots · 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 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