Model Context Protocol

Related topics

• API Gateway works with Model Context Protocol From the official documentation: “This document describes how to configure API Gateway to act as a remote Model Context Protocol (MCP) server.”
• BigQuery works with Model Context Protocol From the official documentation: “It uses the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction), an open protocol for connecting large language models (LLMs) to data sources like BigQuery, allowing you to run SQL queries and interact with your project directly from your existing tools.”
• data lineage works with Model Context Protocol From the official documentation: “This page explains how to connect data lineage to developer tools such as the Gemini CLI and other Model Context Protocol (MCP) clients.”
• Gemini Enterprise Agent Platform works with Model Context Protocol From the official documentation: “Agent Platform also ensures seamless ecosystem integration, enabling agents to connect effortlessly across your enterprise with support for inter-agent collaboration with Model Context Protocol (MCP) and Agent-to-Agent (A2A) protocol.”
• Knowledge Catalog works with Model Context Protocol From the official documentation: “Connect AI agents and developer tools to Knowledge Catalog using Model Context Protocol.”
• Model Armor secures Model Context Protocol From the official documentation: “To enable Model Armor, complete the steps in [Configure Model Armor protection for Google and Google Cloud MCP servers](/model-armor/model-armor-mcp-google-cloud-integration).”
• VPC Service Controls secures Model Context Protocol From the official documentation: “[VPC Service Controls](/vpc-service-controls/docs/overview) lets you protect Model Context Protocol (MCP) integrations by establishing context-aware security boundaries around your resources.”
• BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Cloud Storage From the official documentation: “External BigQuery data source backed by Cloud Storage”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• BigQuery works with Knowledge Catalog From the official documentation: “Some Knowledge Catalog functionalities trigger job execution using BigQuery.”
• BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
• Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
• BigQuery works with Gemini Enterprise Agent Platform From the official documentation: “The BigQuery dataset stores all versions for the associated Gemini Enterprise Agent Platform dataset.”
• BigQuery works with Cloud Audit Logs From the official documentation: “Cloud Audit Logs maintain a record of Google Cloud events, including BigQuery events.”
• Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• API Gateway works with Cloud Run From the official documentation: “API Gateway only supports Cloud Run gRPC services at this time.”
• Cloud Audit Logs works with VPC Service Controls From the official documentation: “VPC Service Controls integrate with Cloud Audit Logs to monitor access to the control plane.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with data lineage From the official documentation: “Use data lineage to identify unused assets and optimize costs in your BigQuery project.”
• BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
• Cloud Audit Logs works with Cloud Storage From the official documentation: “Use Cloud Audit Logs to generate logs for API operations performed in Cloud Storage.”
• Cloud Logging works with Model Armor From the official documentation: “Use Cloud Logging to analyze Model Armor usage patterns, errors, and performance metrics.”
• Gemini Enterprise Agent Platform works with Model Armor From the official documentation: “If you use floor settings for the [Agent Platform integration](/model-armor/model-armor-vertex-integration), all Model Armor features are available in the following locations.”
• VPC Service Controls secures Gemini Enterprise Agent Platform From the official documentation: “The API for Agent Platform can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
• BigQuery works with Cloud Run From the official documentation: “You can then use Cloud Run to transcode data present in the bucket and move it to BigQuery.”
• Cloud Logging works with Cloud Monitoring From the official documentation: “If a log entry matches the filter of the alerting policy, then Cloud Logging extracts labels and forwards the data to Cloud Monitoring.”
• Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
• Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
• Cloud Monitoring works with Model Armor From the official documentation: “This graph uses the metrics that Model Armor publishes to Cloud Monitoring.”
• Cloud Run works with Identity and Access Management From the official documentation: “Cloud Run also offers the ability to control access to a service with Identity and Access Management (IAM).”
• Cloud Storage works with Gemini Enterprise Agent Platform From the official documentation: “This page describes how to use Gemini Enterprise Agent Platform to export your image AutoML Edge models to Cloud Storage.”
• Identity and Access Management secures Gemini Enterprise Agent Platform From the official documentation: “Agent Platform uses IAM to manage access to resources.”
• Identity and Access Management secures Knowledge Catalog From the official documentation: “IAM controls access to your Knowledge Catalog resources at the Google Cloud resource level.”
• Identity and Access Management works with VPC Service Controls From the official documentation: “VPC Service Controls perimeters and Identity and Access Management (IAM) roles work together.”
• Model Armor secures Gemini Enterprise Agent Platform From the official documentation: “This document describes how to configure Model Armor to protect Gemini models on Gemini Enterprise Agent Platform by screening prompts and responses.”
• VPC Service Controls secures Knowledge Catalog From the official documentation: “The API for Knowledge Catalog can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
• API Gateway works with Cloud Audit Logs From the official documentation: “Describes the audit logs created by API Gateway as part of Cloud Audit Logs.”
• API Gateway secures Cloud Run From the official documentation: “This page shows you how to set up API Gateway to manage and secure a [Cloud Run](/run/docs) backend service with gRPC.”
• BigQuery depends on Cloud Storage From the official documentation: “BigQuery relies on Cloud Storage for staging file data and supports reading from and writing to several other sources and Google Cloud services.”
• BigQuery works with VPC Service Controls From the official documentation: “BigQuery integrates with VPC Service Controls to restrict access to your BigQuery resources from specific networks.”
• Cloud Audit Logs works with Cloud Logging From the official documentation: “For real-time analysis, alerting, and visualization, stream the audit logs to [Cloud Logging](/logging/docs/overview).”
• Cloud Audit Logs works with Cloud Run From the official documentation: “The sample code shows you how to read Cloud Storage events using Cloud Audit Logs in a service deployed to Cloud Run.”
• Cloud Audit Logs secures Gemini Enterprise Agent Platform From the official documentation: “You can use Cloud Audit Logs to track changes to Identity and Access Management policies for your Agent Platform resources.”
• Cloud Audit Logs works with Knowledge Catalog From the official documentation: “This document describes audit logging for Knowledge Catalog. Google Cloud services generate audit logs that record administrative and access activities within your Google Cloud resources.”
• Cloud Audit Logs works with Model Armor From the official documentation: “Model Armor uses audit logs to record administrative and resource management activities.”
• Cloud Logging is an alternative to Cloud Monitoring From the official documentation: “To see the status of your invalidation request or find a definitive list of recently submitted requests, you can use Cloud Logging or Cloud Monitoring.”
• Cloud Logging is an alternative to Cloud Storage From the official documentation: “When you specify your own service account for builds, you must store your build logs either in Cloud Logging or in a user-created Cloud Storage bucket.”
• Cloud Logging works with Gemini Enterprise Agent Platform From the official documentation: “This page provides information about how to use Cloud Logging to view details about a Gemini Enterprise Agent Platform model.”
• Cloud Logging works with Knowledge Catalog From the official documentation: “Knowledge Catalog sends logs for service operations and job executions to Cloud Logging.”
• Cloud Logging works with VPC Service Controls From the official documentation: “This page describes how you can find VPC Service Controls errors using Cloud Logging.”
• Cloud Monitoring works with Gemini Enterprise Agent Platform From the official documentation: “Gemini Enterprise Agent Platform exports metrics to [Cloud Monitoring](/monitoring/docs).”
• Cloud Monitoring depends on Identity and Access Management From the official documentation: “To use Monitoring, you must have the appropriate [Identity and Access Management](/iam/docs/overview) (IAM) permissions.”
• Cloud Monitoring works with Knowledge Catalog From the official documentation: “Knowledge Catalog is integrated with Cloud Monitoring, which collects metrics, events, and metadata from Knowledge Catalog services.”
• Cloud Monitoring works with VPC Service Controls From the official documentation: “Cloud Monitoring performs the VPC perimeter check when a project is *added* to a metrics scope:”