A connector for creating and working with AlloyDB for PostgreSQL, Google's managed database service. It lets the coding agent interact with the configured database and its data.

Use it to connect to an AlloyDB database, inspect its data, and perform supported database operations.

It removes the need to switch tools or write a separate connection setup for common database work. Access still requires the relevant Google Cloud project, cluster, instance, database, and credentials.

alloydb — Plugin for Gemini CLI by gemini-cli-extensions

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/gemini-cli-extensions/alloydb

Made for: Gemini CLI.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/plugins/gemini-cli-extensions/alloydb/gemini-extension/github.svg)](https://agentmods.dev/plugins/gemini-cli-extensions/alloydb/gemini-extension)

Your own site

<a href="https://agentmods.dev/plugins/gemini-cli-extensions/alloydb/gemini-extension"><img src="https://agentmods.dev/badge/plugins/gemini-cli-extensions/alloydb/gemini-extension/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/plugins/gemini-cli-extensions/alloydb/gemini-extension"><img src="https://agentmods.dev/badge/plugins/gemini-cli-extensions/alloydb/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

alloydb scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

gemini-extension.json · 61 lines

What it actually says

{
  "name": "alloydb",
  "version": "0.2.0",
  "description": "Create, connect, and interact with an AlloyDB for PostgreSQL database and data.",
  "mcpServers": {
    "alloydb-postgres": {
      "command": "npx",
      "args": [
        "-y",
        "@toolbox-sdk/[email protected]",
        "--prebuilt",
        "alloydb-postgres",
        "--stdio"
      ]
    }
  },
  "contextFileName": "ALLOYDB.md",
  "settings": [
    {
      "name": "Project ID",
      "description": "ID of the Google Cloud project",
      "envVar": "ALLOYDB_POSTGRES_PROJECT"
    },
    {
      "name": "Location",
      "description": "Region of the AlloyDB cluster",
      "envVar": "ALLOYDB_POSTGRES_REGION"
    },
    {
      "name": "Cluster ID",
      "description": "ID of the AlloyDB cluster",
      "envVar": "ALLOYDB_POSTGRES_CLUSTER"
    },
    {
      "name": "Instance ID",
      "description": "ID of the AlloyDB instance",
      "envVar": "ALLOYDB_POSTGRES_INSTANCE"
    },
    {
      "name": "Database",
      "description": "Name of the database",
      "envVar": "ALLOYDB_POSTGRES_DATABASE"
    },
    {
      "name": "User",
      "description": "(Optional) Username of the database user (Default: IAM user)",
      "envVar": "ALLOYDB_POSTGRES_USER"
    },
    {
      "name": "Password",
      "description": "(Optional) Password of the database user (Default: IAM user)",
      "envVar": "ALLOYDB_POSTGRES_PASSWORD"
    },
    {
      "name": "IP Type",
      "description": "(Optional) Type of the IP address: PUBLIC, PRIVATE, or PSC (Default: Public)",
      "envVar": "ALLOYDB_POSTGRES_IP_TYPE"
    }
  ]
}

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

today First seen · 61 lines scan A aa3931ad63cd

Subscribe to this mod's changes

alloydb is a plugin published in the GitHub repository gemini-cli-extensions/alloydb (23 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-22.

Databases PostgreSQL antigravity cli codex gemini gemini-cli

alloydb

Getting it into your agent

Wrote this? Show the measurements

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

cloud-sql-postgresql

cloud-sql-postgresql

oracledb

oracledb

alloydb-omni

alloydb-omni