Geminimap
Antigravity · Plugins

Data Agent Kit

Google's BigQuery/Spanner/Looker plugin bundle

Verified 2026-11-12PluginsApache-2.0

1What it does

A Google Cloud-built plugin that shows what Antigravity plugins are for: bundling a whole domain's capability into one installable unit. Data Agent Kit packs skills and MCP server wiring for Google's data stack — BigQuery, Cloud Spanner, AlloyDB, Looker and adjacent services — so a single install gives the agent both the procedural knowledge (how to query, profile, reason about schemas) and the live connection (the MCP servers that actually reach the services). It is the flagship example of the plugin model in the official marketplace: not one tool or one rule file but a coherent, versioned bundle. The repository is the same GoogleCloudPlatform org that maintains the underlying data services, so the skills encode first-party usage patterns rather than community guesses.

2When to use it

Reach for it when the agent's job touches GCP data services — schema exploration, SQL drafting against real table shapes, Looker/semantic-model questions, Spanner or AlloyDB administration tasks. The bundle is exactly the right granularity: you get the whole domain at once instead of assembling four MCP configs and a folder of notes. Skip it on non-GCP data stacks (Postgres, Snowflake, Databricks all need different servers) and on projects where the agent never touches a database — an installed-but-unused plugin is dead context and extra attack surface. It is also the template to study if you are authoring a plugin: this is what a Google-shaped bundle looks like.

3How to get started

Install through Antigravity's plugin system — the marketplace path is agy plugin install with the kit's identifier, or add the GitHub repo as a plugin source if you want to pin a checkout. After install, the bundled skills appear in the agent's skill surface and the MCP servers need your GCP credentials — the kit assumes standard ADC (Application Default Credentials) or the documented auth path for each server; check the repo's README for which services need which env vars or OAuth scopes. A reasonable smoke test is asking the agent to list BigQuery datasets in a project you can read — auth, MCP wiring and skill activation all light up at once if the chain works.

4Configuration

The plugin bundles its own config files — the user-facing knobs are credentials and project scoping, not the bundle internals. Keep GCP auth in the environment (ADC, gcloud auth) rather than baking keys into mcp_config.json; the kit's servers expect the standard credential chain. Project/organization scoping is the meaningful decision — a plugin wired to a broad service account lets the agent read (and potentially write) everything that account can reach, so prefer per-project credentials scoped to the work. If you fork the plugin to add or strip services, the bundle structure — plugin.json plus the skills/MCP directories — is where the change lives.

5Things to know

  • Google-built but not flagged official in this directory — the whitelist policy reserves official for resources on antigravity.google domains; a GoogleCloudPlatform repo is vendor-adjacent, not product-canonical. The distinction matters for trust labels, not for quality.
  • The bundled MCP servers reach live services — unlike a text-only skill, this plugin can execute queries; budget and permission boundaries live in GCP IAM, not the plugin.
  • Best reference implementation for plugin authoring — the repo's structure (plugin.json, bundled skills, MCP wiring) is what agy plugin init scaffolds toward.
  • Data-stack-specific: the skills' value is domain knowledge (BigQuery idioms, Looker semantics) — on a generic web project it contributes nothing but enabled-skill surface. - Plugin updates arrive through the marketplace channel — unlike a cloned repo, an installed plugin's version is the registry's; check the repo's releases when you need a fix that hasn't shipped to the marketplace build yet.
  • Even without installing it, the repo is worth reading — the plugin.json and bundle layout it uses are the de facto reference for how a plugin should be structured.

6Related on the map

References