Use the Personalized Service Health remote MCP server

This document shows you how to use the Personalized Service Health remote Model Context Protocol (MCP) server to connect with AI applications including Gemini CLI, ChatGPT, Claude, and custom applications you are developing.

The Personalized Service Health remote MCP server provides a secure environment that lets you send natural language prompts to your AI application to retrieve incident information, audit incidents, and automate debugging on your behalf. The Personalized Service Health remote MCP server is enabled when you enable the Personalized Service Health API.

Model Context Protocol (MCP) standardizes how large language models (LLMs) and AI applications or agents connect to external data sources. MCP servers let you use their tools, resources, and prompts to take actions and get updated data from their backend service.

What's the difference between local and remote MCP servers?

Local MCP servers

Typically run on your local machine and use the standard input and output streams (stdio) for communication between services on the same device.

Remote MCP servers

Run on the service's infrastructure and offer an HTTP endpoint to AI applications for communication between the AI MCP client and the MCP server. For more information about MCP architecture, see MCP architecture.

Google and Google Cloud remote MCP servers

Google and Google Cloud remote MCP servers have the following features and benefits:

• Simplified, centralized discovery
• Managed global or regional HTTP endpoints
• Fine-grained authorization
• Optional prompt and response security with Model Armor protection
• Centralized audit logging

For information about other MCP servers and information about security and governance controls available for Google Cloud MCP servers, see Google Cloud MCP servers overview.

Before you begin

Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.

In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

Roles required to select or create a project

• Select a project: Selecting a project doesn't require a specific IAM role—you can select any project that you've been granted a role on.
• Create a project: To create a project, you need the Project Creator role (roles/resourcemanager.projectCreator), which contains the resourcemanager.projects.create permission. Learn how to grant roles.

Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

Go to project selector

If you're using an existing project for this guide, verify that you have the permissions required to complete this guide. If you created a new project, then you already have the required permissions.

Verify that billing is enabled for your Google Cloud project.

Enable the Service Health API.

Roles required to enable APIs

To enable APIs, you need the serviceusage.services.enable permission. If you created the project, then you likely already have this permission through the Owner role (roles/owner). Otherwise, you can get this permission through the Service Usage Admin role (roles/serviceusage.serviceUsageAdmin). Learn how to grant roles.

Enable the API

In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

Roles required to select or create a project

• Select a project: Selecting a project doesn't require a specific IAM role—you can select any project that you've been granted a role on.
• Create a project: To create a project, you need the Project Creator role (roles/resourcemanager.projectCreator), which contains the resourcemanager.projects.create permission. Learn how to grant roles.

Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

Go to project selector

If you're using an existing project for this guide, verify that you have the permissions required to complete this guide. If you created a new project, then you already have the required permissions.

Verify that billing is enabled for your Google Cloud project.

Enable the Service Health API.

Roles required to enable APIs

To enable APIs, you need the serviceusage.services.enable permission. If you created the project, then you likely already have this permission through the Owner role (roles/owner). Otherwise, you can get this permission through the Service Usage Admin role (roles/serviceusage.serviceUsageAdmin). Learn how to grant roles.

Enable the API

Required roles

To get the permissions that you need to use the Personalized Service Health MCP server, ask your administrator to grant you the following IAM roles on the project where you want to use the Personalized Service Health MCP server:

• Make MCP tool calls: MCP Tool User (roles/mcp.toolUser)

For more information about granting roles, see Manage access to projects, folders, and organizations.

These predefined roles contain the permissions required to use the Personalized Service Health MCP server. To see the exact permissions that are required, expand the Required permissions section:

Required permissions

The following permissions are required to use the Personalized Service Health MCP server:

• Make MCP tool calls: mcp.tools.call

You might also be able to get these permissions with custom roles or other predefined roles.

Authentication and authorization

The Personalized Service Health remote MCP server uses the OAuth 2.0 protocol with Identity and Access Management (IAM) for authentication and authorization. All Google Cloud identities are supported for authentication to MCP servers.

We recommend that you create a separate identity for agents that are using MCP tools so that access to resources can be controlled and monitored. For more information about authentication, see Authenticate to MCP servers.

Personalized Service Health MCP OAuth scopes

OAuth 2.0 uses scopes and credentials to determine if an authenticated principal is authorized to take a specific action on a resource. For more information about OAuth 2.0 scopes at Google, see Using OAuth 2.0 to access Google APIs.

Personalized Service Health has the following MCP tool OAuth scopes:

Scope URI for gcloud CLI	Description
https://www.googleapis.com/auth/servicehealth.read-only	Lets a user authorize an agent to read data only.

Configure an MCP client to use the Personalized Service Health MCP server

AI applications and agents, such as Claude or Antigravity, can instantiate an MCP client that connects to a single MCP server. An AI application can have multiple clients that connect to different MCP servers. If your application isn't listed in the client-specific guidance, then you can use the following information to connect from most applications.

In your AI application, look for a way to add or connect to a remote MCP server. For the Personalized Service Health MCP server, enter the following information as required:

• Server name: Personalized Service Health MCP server
• Server URL or Endpoint: https://servicehealth.googleapis.com/mcp
• Transport: HTTP
• Authentication details: Depending on how you want to authenticate, you can enter your Google Cloud credentials, your OAuth Client ID and secret, or an agent identity and credentials. For more information about authentication, see Authenticate to MCP servers.
• OAuth scope: the OAuth 2.0 scope that you want to use when connecting to the Personalized Service Health MCP server.

Redirect URIs

For web-based applications, and some desktop applications, you must allowlist a redirect URI when you create a client ID and secret for authentication. Redirect URIs are used by the authorization server to send tokens to your application. Your application's documentation should specify the redirect URI that you must use. Custom redirect URIs aren't supported.

For application-specific guidance about setting up and connecting to MCP server, see Client-specific guidance.

For more general guidance, see the following resources:

• Connect to remote MCP servers.
• Configure MCP in an AI application.

Available tools

The Personalized Service Health remote MCP server exposes the following tools:

• list_project_events

• get_project_event

To view details of available MCP tools and their descriptions for the Personalized Service Health MCP server, see the Personalized Service Health MCP reference.

List tools

Use the MCP inspector to list tools, or send a tools/list HTTP request directly to the Personalized Service Health remote MCP server. The tools/list method doesn't require authentication.

POST /mcp HTTP/1.1
Host: servicehealth.googleapis.com
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "method": "tools/list",
}

Example use cases

The following sections provide example use cases for the Personalized Service Health MCP server.

Active incident triage

When your Personalized Service Health service experiences unexpected errors, latency, or deployment failures, an agent can use the Personalized Service Health MCP server to check whether active Google Cloud incidents are impacting your project resources.

Sample prompt:

"Are there any active Google Cloud service disruptions or incidents affecting my project projects/ecommerce-prod right now?"

Workflow:

1. The agent calls the list_project_events tool:

   {
     "parent": "projects/ecommerce-prod/locations/global",
     "filter": "state=ACTIVE"
   }
   

2. The agent inspects the returned list of events, checking category, title, detailed_state, and impacts such as affected products and locations.

3. The agent summarizes any active incidents for the user. These summaries highlight affected services, such as Cloud SQL and BigQuery, and show ongoing mitigation status.

Incident detail and status timeline inspection

After the agent has identified an incident, the agent can use the MCP server to retrieve the full chronological timeline of updates, workarounds, and next estimated update times.

Sample prompt:

"Get the latest update timeline and details for incident projects/ecommerce-prod/locations/global/events/YXFBQBKWLAER."

Workflow:

1. The agent calls the get_project_event tool:

   {
     "name": "projects/ecommerce-prod/locations/global/events/YXFBQBKWLAER"
   }
   

2. The agent parses the event_updates list and extracts the root cause summary, latest communication, affected components, and resolution status.

3. The agent provides a structured, user-friendly timeline summary.

Historical incident and post-mortem audit

During reliability reviews, SLA tracking, or post-incident reviews, an agent can use the MCP server to retrieve historical service disruptions over a specific timeframe.

Sample prompt:

"List all Google Cloud incidents that impacted projects/analytics-platform over the past seven days (since 2026-08-06)."

Workflow:

1. The agent constructs a time-filtered query and calls list_project_events:

   {
      "parent": "projects/analytics-platform/locations/global",
      "filter": "category=INCIDENT update_time>=2026-08-06T00:00:00Z",
      "page_size": 25
   }
   

2. If more results exist (next_page_token) is present, the agent calls list_project_events with the page_token to fetch the remaining pages.

3. The agent compiles an incident audit report summarizing incident start times, resolution timestamps, total impact durations, and affected Google Cloud products.

Autonomous troubleshooting and alert correlation

Autonomous debugging agents, such as on-call bots or CI/CD triage agents, can use the MCP server to cross-reference infrastructure errors against Personalized Service Health before attempting application rollbacks or restarts.

Sample prompt:

"We are seeing elevated 503 errors and connection timeouts in Spanner on projects/payment-service-prod. Check if there are known Google Cloud infrastructure incidents before we trigger a rollback."

Workflow:

1. The agent invokes list_project_events:

   {
     "parent": "projects/payment-service-prod/locations/global",
     "filter": "category=INCIDENT state=ACTIVE"
   }
   

2. The agent correlates the reported application symptoms against the impacted products (spanner.googleapis.com) in the incident payload.

3. If an incident is active, the agent calls get_project_event to get the latest mitigation steps. The agent advises the operator that the issue is due to an active cloud platform incident rather than a code defect.

Optional security and safety configurations

MCP introduces new security risks and considerations due to the wide variety of actions that you can do with the MCP tools. To minimize and manage these risks, Google Cloud offers default settings and customizable policies to control the use of MCP tools in your Google Cloud organization or project.

For more information about MCP security and governance, see AI security and safety.

Use Model Armor

Model Armor is a Google Cloud service designed to enhance the security and safety of your AI applications. It works by proactively screening LLM prompts and responses, protecting against various risks and supporting responsible AI practices. Whether you are deploying AI in your cloud environment, or on external cloud providers, Model Armor can help you prevent malicious input, verify content safety, protect sensitive data, maintain compliance, and enforce your AI safety and security policies consistently across your diverse AI landscape.

When Model Armor is enabled with logging enabled, Model Armor logs the entire payload. This might expose sensitive information in your logs.

MCP request routing to Model Armor

The Personalized Service Health MCP server uses cross-jurisdictional routing. When you enable Model Armor, the MCP server sends all requests to Model Armor for screening. Cross-jurisdictional routing might break existing data residency compliance commitments for in-use and in-transit data. For more information about the behavior of other MCP servers, see Model Armor supported products.

Enable Model Armor

You must enable Model Armor APIs before you can use Model Armor.

Console

1. Enable the Model Armor API.

   Roles required to enable APIs

   To enable APIs, you need the serviceusage.services.enable permission. If you created the project, then you likely already have this permission through the Owner role (roles/owner). Otherwise, you can get this permission through the Service Usage Admin role (roles/serviceusage.serviceUsageAdmin). Learn how to grant roles.

   Enable the API

2. Select the project where you want to activate Model Armor.

gcloud

Before you begin, follow these steps using the Google Cloud CLI with the Model Armor API:

1. In the Google Cloud console, activate Cloud Shell.

   Activate Cloud Shell

   At the bottom of the Google Cloud console, a Cloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.

2. Run the following command to set the API endpoint for the Model Armor service.

   gcloud config set api_endpoint_overrides/modelarmor "https://modelarmor.LOCATION.rep.googleapis.com/"

   Replace LOCATION with the region where you want to use Model Armor.

Configure protection for Google and Google Cloud remote MCP servers

To help protect your MCP tool calls and responses you can use Model Armor floor settings. A floor setting defines the minimum security filters that apply across the project. This configuration applies a consistent set of filters to all MCP tool calls and responses within the project.

Tip: Don't enable the prompt injection and jailbreak filter unless your MCP traffic carries natural language data.

Set up a Model Armor floor setting with MCP sanitization enabled. For more information, see Configure Model Armor floor settings.

Note: If the agent and the MCP server are in different projects, you can create floor settings in both projects (the client project and the resource project). In this case, Model Armor is invoked twice, once for each project.

See the following example command:

gcloud model-armor floorsettings update \
--full-uri='projects/PROJECT_ID/locations/global/floorSetting' \
--enable-floor-setting-enforcement=TRUE \
--add-integrated-services=GOOGLE_MCP_SERVER \
--google-mcp-server-enforcement-type=INSPECT_AND_BLOCK \
--enable-google-mcp-server-cloud-logging \
--malicious-uri-filter-settings-enforcement=ENABLED \
--add-rai-settings-filters='[{"confidenceLevel": "MEDIUM_AND_ABOVE", "filterType": "DANGEROUS"}]'

Replace PROJECT_ID with your Google Cloud project ID.

Note the following settings:

• INSPECT_AND_BLOCK: The enforcement type that inspects content for the Google MCP server and blocks prompts and responses that match the filters.
• ENABLED: The setting that enables a filter or enforcement.
• MEDIUM_AND_ABOVE: The confidence level for the Responsible AI - Dangerous filter settings. You can modify this setting, though lower values might result in more false positives. For more information, see Model Armor confidence levels.

Disable scanning MCP traffic with Model Armor

To stop Model Armor from automatically scanning traffic to and from Google MCP servers based on the project's floor settings, run the following command:

gcloud model-armor floorsettings update \
  --full-uri='projects/PROJECT_ID/locations/global/floorSetting' \
  --remove-integrated-services=GOOGLE_MCP_SERVER

Replace PROJECT_ID with the Google Cloud project ID. Model Armor doesn't automatically apply the rules defined in this project's floor settings to any Google MCP server traffic.

Model Armor floor settings and general configuration can impact more than just MCP. Because Model Armor integrates with services like Vertex AI, any changes you make to floor settings can affect traffic scanning and safety behaviors across all integrated services, not just MCP.

Control MCP use with IAM policies

Identity and Access Management (IAM) deny policies and allow policies help you secure Google Cloud and Google MCP servers.

You can combine multiple criteria to build customized security and governance policies by allowing or denying access based on the following:

• The principal.
• Tool properties like the read-only attribute.
• The service name or tool name.
• The application's OAuth client ID.

For more information, see Control MCP use with Identity and Access Management.

What's next

• Read the Personalized Service Health MCP reference documentation.
• Learn more about Google Cloud MCP servers.