# Oracle Database@Google Cloud MCP > Google Cloud managed MCP server for Oracle Database@Google Cloud. Exact tool names and accessible operations depend on the published server reference and configured Google Cloud permissions. Canonical: https://www.mcpfolio.com/servers/google-cloud-oracle-database-google-cloud ## Catalog record - Publisher: Google Cloud - Categories: database, cloud-service ## Website https://docs.cloud.google.com/oracle/database/docs/reference/mcp ## Transports Streamable HTTP ## 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. ## Tools ### list_autonomous_databases List autonomous databases (ADBs) in a Google Cloud project in the given location. Input schema is not included in the available catalog record. ### create_autonomous_database Create an Autonomous Database (ADB). This request can be used to create a new ADB instance or a clone of an existing ADB or an ADB Disaster Recovery (DR) instance. If the source config is not specified, a new ADB instance is created. If the source config is specified, a clone of the source is created. If the source is specified and the source is an ADB DR instance, then a new ADB DR instance is created. While creating a new ADB instance, it can have Public IP support or Private IP support. In case of Private IP support, the request should contain the ODBSubnetwork details. If a request is Public IP mLTS is required mandatorily. Input schema is not included in the available catalog record. ### get_autonomous_database Get details for an autonomous database (ADB) in a Google Cloud project in the given location. Input schema is not included in the available catalog record. ### create_exadata_infrastructure Create a Cloud Exadata Infrastructure. A user needs a Cloud Exadata Infrastructure to create a Cloud Exadata VM cluster. Input schema is not included in the available catalog record. ### get_exadata_infrastructure Get details for an Exadata Infrastructure in a Google Cloud project in the given location. Input schema is not included in the available catalog record. ### list_exadata_infrastructures List Exadata Infrastructures in a Google Cloud project in the given location. Input schema is not included in the available catalog record. ### list_db_servers List Db Servers in a Google Cloud project in the given location for a given Cloud Exadata Infrastructure. For creation of a Cloud Vm Cluster, we need to know the Db Servers in a Cloud Exadata Infrastructure. This API will be used by the MCP service to get the Db Servers. Input schema is not included in the available catalog record. ### create_cloud_vm_cluster Create a Cloud Vm Cluster. A Cloud Vm Cluster is a set of Virtual Machines (VMs) on a Cloud Exadata Infrastructure. Input schema is not included in the available catalog record. ### get_cloud_vm_cluster Get details for a Cloud Vm Cluster in a Google Cloud project in the given location. Input schema is not included in the available catalog record. ### list_cloud_vm_clusters List Cloud Vm Clusters in a Google Cloud project in the given location. Input schema is not included in the available catalog record. ### create_exascale_db_storage_vault Create an Exascale Db Storage Vault. Input schema is not included in the available catalog record. ### get_exascale_db_storage_vault Get details for an Exascale DB Storage Vault in a Google Cloud project in the given location. Input schema is not included in the available catalog record. ### list_exascale_db_storage_vaults List Exascale DB Storage Vaults in a Google Cloud project in the given location. Input schema is not included in the available catalog record. ### create_exadb_vm_cluster Create an Exadb Vm Cluster. An Exadb Vm Cluster is a set of Virtual Machines (VMs) on an Exadata Infrastructure. Input schema is not included in the available catalog record. ### get_exadb_vm_cluster Get details for an Exadb Vm Cluster in a Google Cloud project in the given location. Input schema is not included in the available catalog record. ### list_exadb_vm_clusters List Exadb Vm Clusters in a Google Cloud project in the given location. Input schema is not included in the available catalog record. ### create_db_system Create a DbSystem (BaseDB). Input schema is not included in the available catalog record. ### get_db_system Get details for a Db system in a Google Cloud project in the given location. Input schema is not included in the available catalog record. ### list_db_systems List Db systems in a Google Cloud project in the given location. Input schema is not included in the available catalog record. ### create_odb_network Create an ODB Network. An ODB Network connects a Google Cloud VPC network to Oracle Database resources. Input schema is not included in the available catalog record. ### get_odb_network Get details for an ODB Network in a Google Cloud project in the given location. Input schema is not included in the available catalog record. ### list_odb_networks List ODB Networks in a Google Cloud project in the given location. Input schema is not included in the available catalog record. ### create_odb_subnet Create an ODB Subnet. An ODB Subnet is a subnetwork within an ODB Network. Input schema is not included in the available catalog record. ### get_odb_subnet Get details for an ODB Subnet in a Google Cloud project in the given location. Input schema is not included in the available catalog record. ### list_odb_subnets List ODB Subnets in a Google Cloud project in the given location. Input schema is not included in the available catalog record. ### get_operation Get the status of a long-running operation. A long-running operation can take several minutes to complete. If an operation takes an extended amount of time, then use a command line tool to pause for 30 seconds before rechecking the status of the operation. Input schema is not included in the available catalog record. ## Sources - [official_tool_reference](https://docs.cloud.google.com/oracle/database/docs/reference/mcp) - [official_server_catalog](https://docs.cloud.google.com/mcp/supported-products) - [official_setup_guide](https://docs.cloud.google.com/mcp/configure-mcp-ai-application) - [official_authentication_guide](https://docs.cloud.google.com/mcp/authenticate-mcp) ## Client setup instructions ### Cursor Status: ready to configure. Configuration: ```json { "mcpServers": { "google-cloud-oracle-database-google-cloud": { "url": "https://oracledatabase.googleapis.com/mcp" } } } ``` Prerequisites: - 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. Authentication: - If OAuth is required, connect through Cursor's MCP tools settings and finish the browser sign-in yourself. For credential-based servers, store credentials in a local environment variable or the client's supported secret facility; do not paste secrets into chat. Setup steps: - Choose the correct global or regional endpoint for your data location; this catalog lists the documented endpoint. - In the Google Cloud project, enable the MCP service and the underlying product API if the product guide requires it. - Authenticate the client with Google Cloud ADC (simplest with Antigravity/Gemini CLI) or configure OAuth 2.0 credentials in a compatible client. - Grant the connecting identity roles/mcp.toolUser and only the product IAM roles needed for the intended operations. - Add oracledatabase.googleapis.com to the client as a Streamable HTTP MCP server and complete sign-in. - Refresh the client tool list and check that the tools match the product reference; availability may depend on permissions and selected toolset. Reload: - Open Cursor Settings → Tools & MCP; restart or reconnect the server if Cursor does not pick up the saved project configuration. Verify the connection: - Open Cursor Settings → Tools & MCP and confirm the server is enabled with its tools listed. Ask for a harmless read-only operation only after authentication. Official client guide: [Cursor](https://docs.cloud.google.com/oracle/database/docs/reference/mcp) ### VS Code Status: ready to configure. Configuration: ```json { "mcpServers": { "google-cloud-oracle-database-google-cloud": { "type": "http", "url": "https://oracledatabase.googleapis.com/mcp" } } } ``` Prerequisites: - 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. Authentication: - For OAuth, use VS Code's MCP server controls and complete the browser sign-in yourself. For credential-based servers, use a supported local environment variable/input mechanism; never write a real secret into a tracked workspace file. Setup steps: - Choose the correct global or regional endpoint for your data location; this catalog lists the documented endpoint. - In the Google Cloud project, enable the MCP service and the underlying product API if the product guide requires it. - Authenticate the client with Google Cloud ADC (simplest with Antigravity/Gemini CLI) or configure OAuth 2.0 credentials in a compatible client. - Grant the connecting identity roles/mcp.toolUser and only the product IAM roles needed for the intended operations. - Add oracledatabase.googleapis.com to the client as a Streamable HTTP MCP server and complete sign-in. - Refresh the client tool list and check that the tools match the product reference; availability may depend on permissions and selected toolset. Reload: - Run `MCP: List Servers` from the Command Palette and use its Start/Restart action, or reload the VS Code window if needed. Verify the connection: - Run `MCP: List Servers`; confirm the server is running and its tools appear in Copilot Chat's Agent mode. Official client guide: [VS Code](https://docs.cloud.google.com/oracle/database/docs/reference/mcp) ### Claude Desktop Status: ready to configure. Configuration: ```json Remote connector URL: https://oracledatabase.googleapis.com/mcp Add it in Claude Desktop → Settings → Connectors → Add custom connector. ``` Prerequisites: - 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. Authentication: - Remote connector: review Claude's detected authentication and complete OAuth in its browser flow, or enter a required API credential in the connector's request-header UI. Local extensions may request settings in Claude Desktop; enter secrets only into its secure settings UI. Setup steps: - Choose the correct global or regional endpoint for your data location; this catalog lists the documented endpoint. - In the Google Cloud project, enable the MCP service and the underlying product API if the product guide requires it. - Authenticate the client with Google Cloud ADC (simplest with Antigravity/Gemini CLI) or configure OAuth 2.0 credentials in a compatible client. - Grant the connecting identity roles/mcp.toolUser and only the product IAM roles needed for the intended operations. - Add oracledatabase.googleapis.com to the client as a Streamable HTTP MCP server and complete sign-in. - Refresh the client tool list and check that the tools match the product reference; availability may depend on permissions and selected toolset. Reload: - For a remote connector, enable it from Claude's Connectors UI. For a newly installed local desktop extension, restart Claude Desktop if its tools do not appear. Verify the connection: - Open the Connectors/tools picker and confirm the server and its tools are available. Check Developer settings and logs for local extension failures. Official client guide: [Claude Desktop](https://docs.cloud.google.com/oracle/database/docs/reference/mcp) ### Claude Code Status: ready to configure. Configuration: ```text claude mcp add --transport http google-cloud-oracle-database-google-cloud --scope project "https://oracledatabase.googleapis.com/mcp" ``` Prerequisites: - 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. Authentication: - For OAuth, run 'claude /mcp' in a regular terminal and authenticate google-cloud-oracle-database-google-cloud if prompted. Complete the browser sign-in yourself; do not paste credentials into chat. Setup steps: - Choose the correct global or regional endpoint for your data location; this catalog lists the documented endpoint. - In the Google Cloud project, enable the MCP service and the underlying product API if the product guide requires it. - Authenticate the client with Google Cloud ADC (simplest with Antigravity/Gemini CLI) or configure OAuth 2.0 credentials in a compatible client. - Grant the connecting identity roles/mcp.toolUser and only the product IAM roles needed for the intended operations. - Add oracledatabase.googleapis.com to the client as a Streamable HTTP MCP server and complete sign-in. - Refresh the client tool list and check that the tools match the product reference; availability may depend on permissions and selected toolset. Reload: - Start or restart the Claude Code session in the project if it was already open. Review and approve a new project-scoped server when Claude Code asks. Verify the connection: - Run 'claude mcp get google-cloud-oracle-database-google-cloud' or 'claude mcp list'; in an interactive session, use '/mcp'. Confirm the status is connected and tools are listed. A configured entry alone is not proof of connection. Official client guide: [Claude Code](https://docs.cloud.google.com/oracle/database/docs/reference/mcp) ### Gemini CLI Status: ready to configure. Configuration: ```text gemini mcp add --transport http google-cloud-oracle-database-google-cloud "https://oracledatabase.googleapis.com/mcp" ``` Prerequisites: - 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. Authentication: - For OAuth, run '/mcp auth google-cloud-oracle-database-google-cloud' inside Gemini CLI and complete the browser flow yourself. Setup steps: - Choose the correct global or regional endpoint for your data location; this catalog lists the documented endpoint. - In the Google Cloud project, enable the MCP service and the underlying product API if the product guide requires it. - Authenticate the client with Google Cloud ADC (simplest with Antigravity/Gemini CLI) or configure OAuth 2.0 credentials in a compatible client. - Grant the connecting identity roles/mcp.toolUser and only the product IAM roles needed for the intended operations. - Add oracledatabase.googleapis.com to the client as a Streamable HTTP MCP server and complete sign-in. - Refresh the client tool list and check that the tools match the product reference; availability may depend on permissions and selected toolset. Reload: - Gemini CLI reads its settings on startup. Restart the CLI after direct file edits; its `mcp add` command writes the configuration. Verify the connection: - Run 'gemini mcp list' and confirm google-cloud-oracle-database-google-cloud reports Connected. For local stdio servers, trust the current folder if Gemini CLI requires it. Official client guide: [Gemini CLI](https://docs.cloud.google.com/oracle/database/docs/reference/mcp) ### Codex CLI Status: ready to configure. Configuration: ```text codex mcp add google-cloud-oracle-database-google-cloud --url "https://oracledatabase.googleapis.com/mcp" ``` Prerequisites: - 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. Authentication: - For OAuth, run 'codex mcp login google-cloud-oracle-database-google-cloud' and complete the browser flow yourself. Do not paste credentials into chat. Setup steps: - Choose the correct global or regional endpoint for your data location; this catalog lists the documented endpoint. - In the Google Cloud project, enable the MCP service and the underlying product API if the product guide requires it. - Authenticate the client with Google Cloud ADC (simplest with Antigravity/Gemini CLI) or configure OAuth 2.0 credentials in a compatible client. - Grant the connecting identity roles/mcp.toolUser and only the product IAM roles needed for the intended operations. - Add oracledatabase.googleapis.com to the client as a Streamable HTTP MCP server and complete sign-in. - Refresh the client tool list and check that the tools match the product reference; availability may depend on permissions and selected toolset. Reload: - Restart an already-open Codex session or IDE extension if the server does not appear; the IDE extension offers a Restart action. Verify the connection: - Run 'codex mcp list' or '/mcp' in the Codex TUI. Confirm the server is enabled/connected and its tools are available. Official client guide: [Codex CLI](https://docs.cloud.google.com/oracle/database/docs/reference/mcp) ### Windsurf Status: ready to configure. Configuration: ```json { "mcpServers": { "google-cloud-oracle-database-google-cloud": { "serverUrl": "https://oracledatabase.googleapis.com/mcp" } } } ``` Prerequisites: - 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. Authentication: - OAuth is supported for remote and stdio server transports; complete any browser sign-in from Cascade. For a fixed credential, store it using documented environment interpolation rather than a literal secret in JSON. Setup steps: - Choose the correct global or regional endpoint for your data location; this catalog lists the documented endpoint. - In the Google Cloud project, enable the MCP service and the underlying product API if the product guide requires it. - Authenticate the client with Google Cloud ADC (simplest with Antigravity/Gemini CLI) or configure OAuth 2.0 credentials in a compatible client. - Grant the connecting identity roles/mcp.toolUser and only the product IAM roles needed for the intended operations. - Add oracledatabase.googleapis.com to the client as a Streamable HTTP MCP server and complete sign-in. - Refresh the client tool list and check that the tools match the product reference; availability may depend on permissions and selected toolset. Reload: - Save `mcp_config.json`, then restart or reconnect the server from Cascade's MCP controls. Verify the connection: - Open Cascade's MCP panel and confirm the server is enabled and lists tools. Note: this documentation applies to legacy Cascade; newer Devin Local setup may differ. Official client guide: [Windsurf](https://docs.cloud.google.com/oracle/database/docs/reference/mcp) ### ChatGPT Status: ready to configure. Configuration: ```json Remote MCP endpoint: https://oracledatabase.googleapis.com/mcp Add it in ChatGPT web → Settings/Workspace Settings → Apps → Create. ``` Prerequisites: - 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. Authentication: - If OAuth is configured, complete the authorization prompt while ChatGPT scans tools. Workspace admin/developer permissions may be required. Do not paste credentials into chat. Setup steps: - Choose the correct global or regional endpoint for your data location; this catalog lists the documented endpoint. - In the Google Cloud project, enable the MCP service and the underlying product API if the product guide requires it. - Authenticate the client with Google Cloud ADC (simplest with Antigravity/Gemini CLI) or configure OAuth 2.0 credentials in a compatible client. - Grant the connecting identity roles/mcp.toolUser and only the product IAM roles needed for the intended operations. - Add oracledatabase.googleapis.com to the client as a Streamable HTTP MCP server and complete sign-in. - Refresh the client tool list and check that the tools match the product reference; availability may depend on permissions and selected toolset. Reload: - Save/Create the app draft, then open a new chat and select the app from the tools menu. Admin approval or publishing may be required for workspace use. Verify the connection: - Confirm the app appears as a draft or enabled app, its tool scan completes, and the tools are available in a chat. ChatGPT web cannot connect directly to local stdio servers. Official client guide: [ChatGPT](https://docs.cloud.google.com/oracle/database/docs/reference/mcp) ### Manual Status: ready to configure. Configuration: ```json { "mcpServers": { "google-cloud-oracle-database-google-cloud": { "url": "https://oracledatabase.googleapis.com/mcp" } } } ``` Prerequisites: - 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. Authentication: - Follow the selected client's official OAuth flow or store a required credential in its local secret/environment mechanism. Never paste secrets into chat or commit them. Setup steps: - Choose the correct global or regional endpoint for your data location; this catalog lists the documented endpoint. - In the Google Cloud project, enable the MCP service and the underlying product API if the product guide requires it. - Authenticate the client with Google Cloud ADC (simplest with Antigravity/Gemini CLI) or configure OAuth 2.0 credentials in a compatible client. - Grant the connecting identity roles/mcp.toolUser and only the product IAM roles needed for the intended operations. - Add oracledatabase.googleapis.com to the client as a Streamable HTTP MCP server and complete sign-in. - Refresh the client tool list and check that the tools match the product reference; availability may depend on permissions and selected toolset. Reload: - Restart/reload the selected client only if its documentation requires it. Verify the connection: - Use the selected client's MCP status view and verify the server exposes tools; do not report connected based only on a saved config. Official client guide: [Manual](https://docs.cloud.google.com/oracle/database/docs/reference/mcp)