Google AlloyDB for PostgreSQL
Generally AvailableFerentin's Google AlloyDB MCP server connects agents through OAuth2 + Cloud IAM, with tools for cluster/instance/user lifecycle management, SQL and read-only SQL execution, backups, and Cloud Storage import/export. Access is scoped by the signing-in identity's IAM grants.
- Database
- PostgreSQL
- Vector Search
- Authentication
- OAuth 2.0
- Hosting
- Vendor-hosted endpoint
- Required scopes
- 1
- Data actions
- Read and write
How it works
Every agent request passes through Ferentin policy before it reaches Google AlloyDB for PostgreSQL.
- AI agentAsks for something
- Ferentin policies
- OAuth 2.0 consent
- Cloud iam authorization
- No API keys
- Audit logging
- Google AlloyDB for PostgreSQL MCP serverAuthorized connection
- Governed resultMasked, logged, returned
What agents can do
17 tools · you choose which ones agents may callSearch and browse what exists, without opening the content itself.
- list_clusters
- list_instances
- list_users
Permissions requested
The OAuth 2.0 scopes Google AlloyDB for PostgreSQL asks you to approve when you connect.
| Scope | Access |
|---|---|
| https://www.googleapis.com/auth/alloydb | Not rated |
Before you connect
- Google does not support Dynamic Client Registration (DCR) — each tenant must create its own OAuth client in Google Cloud Console.
- Authentication is OAuth 2.0 + Google Cloud IAM. API keys are not accepted; access is enforced by the signing-in identity's IAM roles.
- Use access_type=offline to receive a refresh token for long-lived access.
- The scope https://www.googleapis.com/auth/alloydb is required; cloud-platform works as a superset.
3 more technical notes
- The target instance must have the Data Access API enabled (data_api_access = ALLOW_DATA_API_ACCESS).
- Tool responses larger than 10 MB may be truncated. execute_sql_read_only requires PostgreSQL 17+.
- Query-performance diagnostics are provided by the separate Database Insights MCP server.
About Google AlloyDB for PostgreSQL
AlloyDB is Google Cloud's PostgreSQL-compatible database for demanding enterprise workloads, with columnar acceleration and AlloyDB AI (pgvector) for vector-similarity search.
Frequently asked about Google AlloyDB for PostgreSQL
- What can AI agents do with Google AlloyDB for PostgreSQL through Ferentin?
- Ferentin exposes 17 Google AlloyDB for PostgreSQL MCP tools to your AI agents, grouped as Discover (3 tools), Access (5 tools) and Manage (9 tools). Every call is checked against your Ferentin policies before it reaches Google AlloyDB for PostgreSQL.
- How is Google AlloyDB for PostgreSQL access secured?
- Requests through the Google AlloyDB for PostgreSQL integration are covered by OAuth 2.0 consent, cloud iam authorization, no API keys and audit logging. These controls are applied by Ferentin, not by Google AlloyDB for PostgreSQL, so they hold across every connected agent.
- What permissions does the Google AlloyDB for PostgreSQL integration require?
- The Google AlloyDB for PostgreSQL integration requests 1 OAuth 2.0 scope: https://www.googleapis.com/auth/alloydb
- How do I connect Google AlloyDB for PostgreSQL to Ferentin?
- Open the Ferentin admin console, add Google AlloyDB for PostgreSQL as a new connection and authenticate with OAuth 2.0. You then choose which permissions and which tools your agents may use, and the connection goes live for everyone covered by your policies.
- Is the Google AlloyDB for PostgreSQL integration generally available?
- Yes. The Google AlloyDB for PostgreSQL integration is generally available on Ferentin, including the free tier.
Related integrations
3
Google Cloud SQL
Natural-language database operations on Cloud SQL (PostgreSQL/MySQL/SQL Server): run SQL, manage instances, users, and backups.
Google Cloud Spanner
Manage Cloud Spanner instances and databases and run multi-model (SQL + graph GQL) queries — governed by Cloud IAM.
Google BigQuery
Query and explore BigQuery data warehouses. Discover datasets/tables, inspect schema, and run read-only SQL — governed by Cloud IAM.