AgentSidekick

Better agent tooling for Google Cloud

Integration gap · Measured demandOverall 45.2 / 100 DERConfidence Medium DERCalculated

897 public GitHub issues mention "Google Cloud mcp" (checked 2026-11-21) SRC, while 105 indexed products mention Google Cloud DER. On the six weighted components it scores 45.2 of 100, confidence Medium, as of 2026-11-21.

Score breakdown

Contribution = weight × component score. The contributions add up to the overall score.

ComponentWeightScoreScore (0–100)ContributionKind
Demand0.2553.00.25 × 53.0 = 13.25Measured
Competition gap0.200.00.20 × 0.0 = 0.00Measured
Monetisation0.2065.00.20 × 65.0 = 13.00Heuristic
Growth (relative)0.1520.00.15 × 20.0 = 3.00Measured
Feasibility0.1080.00.10 × 80.0 = 8.00Heuristic
Distribution0.1079.00.10 × 79.0 = 7.90Measured
Overall1.0045.15 → 45.2

Solid bars are measured components; dashed outlines are rules of thumb. The full formula is on the radar page.

Confidence: Medium

Rule: Medium when at least 50 GitHub issues mention the integration and at least 10 indexed products mention it; otherwise Low. Nothing is rated High.

What would raise it

  • Medium is the highest level the rules assign. High would need a second, independent demand source (search volume or marketplace installs), which is not connected.

The opportunity

All text in this section is generated by rule from the record. It is a starting point, not research.

Description
Developers are asking for Google Cloud access from AI agents more than the current supply of well-maintained tools would suggest.DER
Problem
Agents need to read from and act on Google Cloud. Only some of the existing tools are both documented and actively maintained.DER
Target users
Teams that already pay for Google Cloud and want agents to work inside itHEU
Product form
MCP server (optionally bundled as a plugin with skills)HEU
Revenue model
Hosted/remote server with per-seat or usage pricingHEU
Complexity
Low to mediumHEU
Competition level
HighDER
Subject
Google Cloud (integration)

Evidence for

4 row(s) from opportunity_evidence.

  • DemandMeasuredDERvalue 897

    897 public GitHub issues contain the phrase "Google Cloud mcp" (checked 2026-11-21); that is the 53th percentile of the 108 integrations tracked. Issue mentions measure developer discussion, not buyers.

    Source

  • MonetisationHeuristicHEU

    Google Cloud is sold mainly to businesses on paid plans, which suggests buyers with budget. This is a rule of thumb, not revenue data.

  • FeasibilityHeuristicHEU

    Google Cloud has a public API (documentation linked).

    Source

  • DistributionMeasuredDERvalue 37

    37 of 47 tracked agent platforms document MCP support, so one MCP server can reach all of them.

    /platforms/

Evidence against

3 row(s) from opportunity_evidence.

  • Competition gapMeasuredDERvalue 74

    105 indexed products mention Google Cloud; 74 of them have a complete record and a repository pushed in the last 180 days.

    /integrations/google-cloud/

  • Growth (relative)MeasuredDERvalue 35

    35 products launched in the last 90 days versus 22 in the previous 90; the whole catalogue went from 14427 to 45454, and the score is relative to that.

  • Competition gapMeasuredDERvalue 1

    1 indexed product(s) are published under a namespace matching Google Cloud itself (Agent Runtime (Gemini Enterprise Agent Platform)). The gap score was reduced by 25 points for that.

    /integrations/google-cloud/

Existing products

All Google Cloud products

The most notable profiled products mentioning Google Cloud (up to 8). 105 indexed in total.

agents-cli

Agent projectby googleHEU

6.4k GitHub starspushed 4d agoApache-2.0

Google Cloud Data Agent Kit

IDE extensionby googlecloudtoolsSRC

push date unknownSEE LICENSE IN LICENSE

thesvg

MCP serverby glinckerHEU

3.0k GitHub starspushed todayMIT

TerraVision

MCP serverby patrickchughSRC

1.7k GitHub starspushed 1d agoAGPL-3.0

Where it could be distributed

All platforms

37 of 47 tracked agent platforms document MCP support CUR, so one MCP server could reach all of them. No pairing has been tested.

ContinueOpenCodeClaude CodeCodexGemini CLIZedOpenHandsClineWarpgooseQwen CodeRoo Code+25 more

Channels: Official MCP Registry listing, plugin marketplaces for Claude/Cursor/Codex, and the integration vendor's own app directory where one exists. HEU

Data coverage

Indexed products
105DER
With a full profile
8+DER
Launches, last 90 days
35 vs 22 in the 90 beforeSRC
Demand measured
SRC
Segment calculated
Score calculated

Risks and counterarguments

  • The vendor may ship (or already ships) an official Google Cloud server, which usually becomes the default.
  • Issue mentions measure developer discussion, not willingness to pay.
  • 105 indexed products mention Google Cloud; 74 of them have a complete record and a repository pushed in the last 180 days.
  • 35 products launched in the last 90 days versus 22 in the previous 90; the whole catalogue went from 14427 to 45454, and the score is relative to that.
  • 1 indexed product(s) are published under a namespace matching Google Cloud itself (Agent Runtime (Gemini Enterprise Agent Platform)). The gap score was reduced by 25 points for that.

Assumptions

What has to be true for the score to mean anything.

  • Mentions of "Google Cloud mcp" in GitHub issues reflect developers wanting Google Cloud access from agents.
  • Products that mention the integration in their description or package metadata are the competing supply; ones that do not name it are missed.
  • "Well-maintained" means data completeness ≥ 0.6 and a repository push in the last 180 days.
  • Percentiles compare this integration only with the other integrations tracked, not with the wider market.
  • A platform that documents MCP support can run any MCP server; no pairing has been tested.

How to verify this yourself

  1. Run the demand query on GitHub: https://github.com/search?q=%22Google%20Cloud%20mcp%22%20in%3Atitle%2Cbody%20is%3Aissue&type=issues. Compare the count with 897 on 2026-11-21; read a sample of issues to see whether they ask for agent access or merely mention it.
  2. Check the supply on the Google Cloud page and search the official MCP Registry and the vendor's own app directory for an official server.
  3. Download the record with all evidence: /api/dataset/opportunities.json.

All opportunities · Methodology · Report an error

Page data last updated .