Ext Ops Panel
Open dashboard
Comparison

db-context-engineering vs Camber - Remote Agentic Data Science

db-context-engineering is a plugin bundle for AI coding tools published by GoogleCloudPlatform. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Camber - Remote Agentic Data Science is an MCP server published by camber-mcp.cambercloud.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
Marketplacedb-context-engineeringCamber - Remote Agentic Data Science
Community marketplace google/skills Listed
Version: 0.7.2
Forks (GitHub): 20
Stars (GitHub): 41
Not marked · First seen
Not listed
Community marketplace googlecloudplatform/data-cloud-plugins Listed
Version: 0.6.0
Forks (GitHub): 20
Stars (GitHub): 41
Not marked · First seen
Not listed
Community marketplace googlecloudplatform/db-context-enrichment Listed
Version: 0.7.5
Forks (GitHub): 20
Stars (GitHub): 41
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.4
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

db-context-engineering vs Camber - Remote Agentic Data Science
Factdb-context-engineeringCamber - Remote Agentic Data Science
Marketplaces that list it11
Stars (GitHub) (differs)41No figure on GitHub
Forks (GitHub) (differs)20No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (camber-mcp.cambercloud.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)9Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/googlecloudplatform/db-context-enrichmentNot stated
Changes in the last 7 days (differs)40
First seen (differs)2026-10-202026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 18 h ago

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

db-context-engineering

In its own words, on Community GitHub marketplaces:

Context Engineering Agent for generating and maintaining QueryData / Conversational Analytics API context sets (templates, facets, value searches) for natural language to SQL tasks. Works with AlloyDB, Cloud SQL for MySQL, Cloud SQL for PostgreSQL, and Spanner.

Camber - Remote Agentic Data Science

In its own words, on Official MCP Registry:

Remote data science agents for Snowflake, Databricks & BigQuery in Claude/Cursor via MCP

How to run each

db-context-engineering As a Claude Code plugin

Claude Code
/plugin marketplace add google/skills
/plugin install db-context-engineering@google-plugins

Camber - Remote Agentic Data Science As a remote MCP server

Claude Code
claude mcp add --transport http camber-mcp-server https://camber-mcp.cambercloud.com/mcp --header "Authorization: Bearer <YOUR_CAMBER_API_KEY>"

Requires: Authorization header

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

Only Camber - Remote Agentic Data Science has a remote endpoint we check. How we check endpoints

Tools each declares

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

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: db-context-engineering · What it can do: Camber - Remote Agentic Data Science · Compare two other plugins

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