Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB MCP tools for automated database operations including AI-powered search and vector capabilities.
AlloyDB for PostgreSQL is a managed, PostgreSQL-compatible database service designed for enterprise-grade performance and availability. It utilizes a disaggregated compute and storage architecture to scale resources independently. It also provides AlloyDB AI, a collection of features that includes AI-powered search (vector, hybrid search, and AI functions), natural language capabilities, conversational analytics, and inference features like forecasting and model endpoint management to help developers build AI apps faster.
Enable the AlloyDB API:
gcloud services enable alloydb.googleapis.com --quiet
Create a Cluster:
gcloud alloydb clusters create my-cluster --region=us-central1 \
--password=my-password --network=my-vpc \
--quiet
Note: For production, we recommend using IAM database authentication instead of passwords. If passwords must be used, use secure secret management (e.g., Secret Manager) instead of passing passwords in cleartext.
Create a Primary Instance:
gcloud alloydb instances create my-primary --cluster=my-cluster \
--region=us-central1 --instance-type=PRIMARY --cpu-count=2 \
--quiet
Core Concepts: Architecture, disaggregated storage, and performance features.
CLI Usage: Essential gcloud alloydb commands
for cluster and instance management.
Client Libraries & Connectors: Connecting to AlloyDB using Python, Java, Node.js, and Go.
MCP Usage: Using the AlloyDB remote MCP server and Gemini CLI extension.
Infrastructure as Code: Terraform configuration and deployment examples.
IAM & Security: Predefined roles, service agents, and database authentication.
If you need product information not found in these references, use the
Developer Knowledge MCP server search_documents tool.
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/alloydb-basics · pinned to the source commit
# Run from your project root
git clone https://github.com/davila7/claude-code-templates.git .skillboard-tmp
git -C .skillboard-tmp checkout 5cc17cf267132cc690dee82239b80a99ec82e4f8
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/cli-tool/components/skills/database/alloydb-basics" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/davila7/claude-code-templates.git .skillboard-tmp
git -C .skillboard-tmp checkout 5cc17cf267132cc690dee82239b80a99ec82e4f8
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/cli-tool/components/skills/database/alloydb-basics" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/alloydb-basics
Scanner static-checks@0.1.0 · commit 5cc17cf26713. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
References credentials, tokens or secret files that a skill should not need.
Evidence: [redacted]· fingerprint 5e884898da280471