Hosting

Google-managed remote

Transport

Streamable HTTP

Endpoint

https://backupdr.googleapis.com/mcp

Authentication

Google Cloud authentication: OAuth 2.0 using Application Default Credentials (ADC) in supported Google clients, or a client OAuth ID/secret or bearer token in compatible third-party clients. The principal needs mcp.tools.call plus the underlying product permissions; API key authentication is only available for services that explicitly support it.

Requirements

• A Google Cloud project and access to the target product/resource.
• Enable this MCP service and its underlying Google Cloud API as required by the product guide.
• An MCP client that supports Streamable HTTP.
• An identity with the MCP Tool User role (roles/mcp.toolUser) or equivalent mcp.tools.call permission, plus permissions for the underlying product operations.

Setup steps

1. Choose the correct global or regional endpoint for your data location; this catalog lists the documented endpoint.
2. In the Google Cloud project, enable the MCP service and the underlying product API if the product guide requires it.
3. Authenticate the client with Google Cloud ADC (simplest with Antigravity/Gemini CLI) or configure OAuth 2.0 credentials in a compatible client.
4. Grant the connecting identity roles/mcp.toolUser and only the product IAM roles needed for the intended operations.
5. Add backupdr.googleapis.com to the client as a Streamable HTTP MCP server and complete sign-in.
6. Refresh the client tool list and check that the tools match the product reference; availability may depend on permissions and selected toolset.

The stored 23 PascalCase tools correspond to Google’s managed remote Backup and DR MCP service. A separate local @google-cloud/backupdr-mcp package exposes 23 snake_case tools with READ_ONLY/UPSERT/ALL modes; do not merge the two inventories. Managed tools can create/delete backup plans, vaults, backups, associations and trigger restores; restores and deletions affect protected data. IAM applies.

• ListBackupPlans

  Lists all BackupPlans in a specified location. BackupPlans define the schedule and retention policies for backups. Use this to discover existing plans.

  01
• CreateBackupPlan

  Creates a new BackupPlan in a given project and location. A BackupPlan specifies how and when backups should be taken.

  02
• GetBackupPlan

  Retrieves the details and configuration of a specific BackupPlan by name.

  03
• UpdateBackupPlan

  Updates an existing BackupPlan's configuration. Use this to modify schedules or retention rules.

  04
• DeleteBackupPlan

  Deletes a BackupPlan. This operation will fail if the plan is currently referenced by any active BackupPlanAssociations. You must first delete the corresponding backup plan associations.

  05
• CreateBackupVault

  Creates a new BackupVault to store backups in a given project and location.

  06
• ListBackupVaults

  Lists all secure storage BackupVaults in a specified location.

  07
• GetBackupVault

  Retrieves the details and status of a specific BackupVault.

  08
• UpdateBackupVault

  Updates the settings of a BackupVault, such as labels or annotations.

  09
• DeleteBackupVault

  Deletes a BackupVault. The vault must have no backups and datasources, for it to be successfully deleted.

  10
• ListBackups

  Lists all backups associated with a specific data source. Use this to find available recovery points.

  11
• GetBackup

  Retrieves details of a specific backup, including its size, state, and creation time.

  12
• DeleteBackup

  Deletes a specific backup from a vault.

  13
• RestoreBackup

  Restores a VM or Disk from a specified Backup. This is a long-running operation and returns an operation ID. You may need to check the status using get_operation .

  14
• ListDataSources

  Lists all data sources (protected workloads) contained within a specific backup vault.

  15
• ListBackupPlanAssociations

  Lists all BackupPlanAssociations. BPAs link a specific workload to a BackupPlan to enable protection.

  16
• CreateBackupPlanAssociation

  Creates a new BackupPlanAssociation, linking a workload to a BackupPlan to start automated backups.

  17
• GetBackupPlanAssociation

  Retrieves details of a specific BackupPlanAssociation.

  18
• UpdateBackupPlanAssociation

  Updates an existing BackupPlanAssociation.

  19
• DeleteBackupPlanAssociation

  Deletes a BackupPlanAssociation. Deleting the association stops scheduled backups for the workload, but existing backups are retained according to the plan's retention policy unless manually deleted.

  20
• TriggerBackup

  Manually triggers an immediate on-demand backup for a resource, bypassing the scheduled plan.

  21
• ListResourceBackupConfigs

  Retrieves backup configuration summaries and protection status for resources with in the specified project and location. CRITICAL: Location is mandatory and must be sent in the request. Location must not be '-' or 'global'. Do NOT attempt to use other tools (like ListBackupVaults,ListBackupPlans,ListBackupPlanAssociations) to discover active locations. You MUST explicitly ask the user for the location and project before calling this tool.

  22
• get_operation

  Get the status of a long-running operation (LRO). Usage Some tools ( create_backup_plan , create_backup_vault ,'restore_backup','delete_backup_plan' etc) return a long-running operation. You can use this tool to get the status of the operation. Parameters name : The name of the operation to get. It corresponds to the name field in the long-running operation. It should be in the format of projects/{project}/locations/{location}/operations/{operation} . Returns An Operation object that contains the status of the operation. If the operation is not complete, the response will be empty. If the operation is complete, the response will contain either: A response field that contains the result of the operation and indicates that it was successful. A error field that indicates any errors that occurred during the operation.

  23

• official server catalog

  Official Google Cloud catalog lists this product as an available remote MCP server.

• official setup guide

  Google Cloud describes remote MCP client setup, Streamable HTTP transport, supported authentication options, and ADC setup.

• official authentication guide

  Google documents supported identity types and authorization requirements for Google Cloud MCP calls.

• official remote tool reference

  Google Cloud remote MCP tool reference covers the PascalCase managed service surface.

• official local server guide

  Current guide documents a distinct local package and its 23 snake_case tool names plus read-only/upsert/all permission modes; treated separately from the managed remote service.

Documentation checked 2026-10-28. Connection has not been runtime tested.