Connectors · MSP & PSA
Google Workspace Alert Center MCP server for AI agents.
actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Google Workspace Alert Center and the rest of your systems. It gives your agent 11 Google Workspace Alert Center actions (5 reads, 4 writes and 2 that wait for a confirmation) and holds the Google Workspace Alert Center credential itself, so the agent never does. It paces Google Workspace Alert Center's limits and records every call. Connecting Google Workspace Alert Center needs your own Google Workspace Alert Center OAuth app and one admin sign-in.
100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.
claude mcp add --transport http actionlake https://connect.actionlake.com/mcpdo { action: "gws_alert_center.alerts.list", intent: "check which Google Workspace Alert Center account is connected"}# Alerts: list · read · 1 upstream call- 11actionsin one signed file
- 5readlook, never change
- 4writecreate and update
- 2wait for a yesdestructive, confirmed first
Set up
Connect Google Workspace Alert Center in three steps.
- 01
Add actionlake to Claude.
Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
https://connect.actionlake.com/mcp - 02
Connect Google Workspace Alert Center.
OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Workspace Alert Center, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. actionlake stores what you paste write-only, sealed under your tenant's key.
Before the first sign-in, Google Workspace Alert Center needs an OAuth app of your own, registered in its developer portal. actionlake has no Google Workspace Alert Center app to lend you.
access_tokenAccess token from one sign-in with your own OAuth apprefresh_tokenRefresh token from the same sign-in; the access token is renewed from itclient_idGoogle OAuth client id (Google Cloud console > APIs & Services > Credentials; enable the Google Workspace Alert…client_secretGoogle OAuth client secret
account { op: "connections.requirements", service: "gws_alert_center" } # free: exactly what to paste, and what is found for you - 03
Make the first call. Check before a write.
Ask in plain words; Claude picks the action. Before anything changes,
checkvalidates the call and prices it, for free.do { action: "gws_alert_center.alerts.list" }# alerts: list · read · 1 upstream callcheck { action: "gws_alert_center.alerts.delete", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent
Google Workspace Alert Center at a glance
- Sign-in
- OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Workspace Alert Center, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on.
- You provide
access_tokenrefresh_tokenclient_idclient_secret- Limits we pace to
- 300 calls a minute, per connection
- API covered
- Google Workspace Alert Center API v1beta1 (alerts, alert metadata, feedback, notification settings) API alertcenter v1beta1 (Discovery revision 20261019)
alertcenter.googleapis.com - Built from
- Google Workspace Alert Center's documentation, read 23 October 2026alertcenter.googleapis.comdevelopers.google.com
- Service file
- Version 1.0.0, signed (Ed25519)
- Cached reads
- 5 of 5 reads, for up to 5 minutes; a write clears what it affects
- Shared entities
- 1, so ask can line Google Workspace Alert Center up with your other systems
- Data
- Processed and stored in Sydney, Australia. No US region yet
Capabilities
What an AI agent can do in Google Workspace Alert Center.
11 actions in 1 area. Every one carries its effect, so a key can allow the reads and hold the rest.
- 5readlook, never change
- 4writecreate and update
- 2destructivewait for a confirmation
Alerting
115 read · 4 write · 2 destructive
Alerts: list · Alerts: get · Alerts: delete · Alerts: batch undelete
Top actions
The Google Workspace Alert Center API, shaped for agents.
The ids your agent types, what each does, and the one name it shares with other systems. 3 of Google Workspace Alert Center's 3 action names are shared with at least one other connector, so an agent learns them once.
| Action | What it does | Effect | Same name in |
|---|---|---|---|
gws_alert_center.alerts.listAlerts: list | Lists the alerts. | read | monitoring.alert.list51 connectors |
gws_alert_center.alerts.getAlerts: get | Gets the specified alert. | read | monitoring.alert.get33 connectors |
gws_alert_center.alerts.deleteAlerts: delete | Marks the specified alert for deletion. | destructive | monitoring.alert.delete13 connectors |
gws_alert_center.alerts.undeleteAlerts: undelete | Restores, or "undeletes", an alert that was marked for deletion within the past 30 days. | write | this connector |
gws_alert_center.alerts.get_metadataAlerts: get metadata | Returns the metadata of an alert. | read | this connector |
gws_alert_center.alert_feedback.listAlert feedback: list | Lists all the feedback for an alert. | read | this connector |
gws_alert_center.alert_feedback.createAlert feedback: create | Creates new feedback for an alert. | write | this connector |
gws_alert_center.settings.updateSettings: update | Updates the customer-level settings. | write | this connector |
Try it
Prompts to paste into Claude.
Each one names the Google Workspace Alert Center actions it will call, so you know what it reads and what it changes before you send it.
- Readread
Which Google Workspace Alert Center alerts are open right now? Group them by service.
calls
gws_alert_center.alerts.list - Writewrite
Alerts: undelete in Google Workspace Alert Center. Show me exactly what you will send before you save it.
calls
gws_alert_center.alerts.undelete
Governance for Google Workspace Alert Center
Destructive actions wait for a yes.
2 Google Workspace Alert Center actions are destructive. These are all of them:
- Alerts: delete
gws_alert_center.alerts.delete - Alerts: batch delete
gws_alert_center.alerts.batch_delete
A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.
Alerts: delete?
intent: the user asked me to alerts: delete
account { op: "keys.create", name: "gws-alert-center-agent", allowed_actions: ["gws_alert_center.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "gws_alert_center.alerts.delete", approver: "[email protected]" }, { match: "gws_alert_center.alerts.batch_delete", approver: "[email protected]" } ]}Cost
What Google Workspace Alert Center costs on actionlake.
Every Google Workspace Alert Center action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Google Workspace Alert Center refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
- 1upstream call per actionall 11 Google Workspace Alert Center actions
- 1actions pageeach page of a long list is one call
- 5reads can be cacheda cache hit costs nothing
- 100,000calls a month, freepaid plans from US$49 a month for 250,000
Action index
Every Google Workspace Alert Center action.
11 actions by area: the id your agent calls, what it does, and its effect.
Alerting11
gws_alert_center.alert_feedback.createAlert feedback: createwritegws_alert_center.alert_feedback.listAlert feedback: listreadgws_alert_center.alerts.batch_deleteAlerts: batch deletedestructivegws_alert_center.alerts.batch_undeleteAlerts: batch undeletewritegws_alert_center.alerts.deleteAlerts: deletedestructivegws_alert_center.alerts.getAlerts: getreadgws_alert_center.alerts.get_metadataAlerts: get metadatareadgws_alert_center.alerts.listAlerts: listreadgws_alert_center.alerts.undeleteAlerts: undeletewritegws_alert_center.settings.getSettings: getreadgws_alert_center.settings.updateSettings: updatewrite
Questions
The Google Workspace Alert Center MCP server, answered.
Is there a Google Workspace Alert Center MCP server for Claude?
Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 11 Google Workspace Alert Center actions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Google Workspace Alert Center.
What do I need to connect Google Workspace Alert Center?
Your own Google Workspace Alert Center OAuth app, registered with Google Workspace Alert Center (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no Google Workspace Alert Center app of its own, so this is not a one-step consent. actionlake renews the access token as it expires. The free call account { op: "connections.requirements", service: "gws_alert_center" } lists exactly what to paste.
Can an AI agent delete or change things in Google Workspace Alert Center?
Only if its key allows it, and only with an explicit confirmation. 2 Google Workspace Alert Center actions are destructive, including alerts: delete and alerts: batch delete. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.
Will an AI agent use up my Google Workspace Alert Center API limit?
actionlake paces every call to the limits in the Google Workspace Alert Center service file: 300 calls a minute per connection. Repeated reads are answered from cache (5 Google Workspace Alert Center actions can be), which never reaches Google Workspace Alert Center.
What does a Google Workspace Alert Center action cost?
One upstream call, the only unit actionlake bills. A list that pages bills one call per page (1 Google Workspace Alert Center actions page). Cache hits, searches, dry runs and calls Google Workspace Alert Center refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
Which Google Workspace Alert Center API does it cover?
The Google Workspace Alert Center API v1beta1 (alerts, alert metadata, feedback, notification settings) API alertcenter v1beta1 (Discovery revision 20261019) at alertcenter.googleapis.com. It is built from Google Workspace Alert Center's documentation as read on 23 October 2026. 11 actions in 1 area, each one in the signed service file (version 1.0.0).
Does actionlake keep my Google Workspace Alert Center data, and where?
actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Google Workspace Alert Center credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.
Which AI clients can use it?
Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.
Give your agent Google Workspace Alert Center today.
Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.