The AlloyDB API is the control plane for AlloyDB for PostgreSQL on Google Cloud — Google's PostgreSQL-compatible managed database service tuned for transactional and analytical workloads. It provisions and manages clusters and primary or read-pool instances, runs failover and switchover, drives backups and exports, and supports cluster restore. Application data access still goes through the standard PostgreSQL wire protocol; this API is for lifecycle and operations.
28 endpointsThe Backup and DR Service API manages Google Cloud's enterprise backup product for Compute Engine, VMware, databases, and file storage. It exposes operations to provision management servers, control data sources, initiate and finalise backups, and manage the long-running operations associated with each step. The API is the integration surface for orchestrating backups from external schedulers, ticketing systems, or compliance workflows. It manages backup orchestration, not the actual virtual machines, databases, or file systems being protected.
30 endpointsThe BigLake API provides programmatic access to BigLake Metastore, a serverless metastore for open-source data formats — primarily Apache Iceberg tables — that can be queried from BigQuery and Spark. It exposes operations to manage catalogs, databases, and tables, including a rename operation for schema evolution. Resources are scoped to a project and location, and the metastore makes the same data discoverable to multiple compute engines without per-engine setup. The API does not run queries or process data; it manages metadata only.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"find live events near a location"
# → Jentic returns the GET /events tool with parameter schema, agent executes.