---
title: "Google Workspace Directory MCP server - actionlake"
description: "Give Claude 128 Google Workspace Directory actions through one MCP server: directory. Your agent never holds the credential. 100,000 calls a month free."
canonical: https://actionlake.com/connectors/google-workspace-directory
updated: 2026-10-11
---

Connectors · Identity & security

# Google Workspace Directory MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Google Workspace Directory and the rest of your systems. It gives your agent 128 Google Workspace Directory actions (46 reads, 54 writes and 28 that wait for a confirmation) and holds the Google Workspace Directory credential itself, so the agent never does. It paces Google Workspace Directory's limits and records every call. Connecting Google Workspace Directory needs your own Google Workspace Directory OAuth app and one admin sign-in.

[Connect Google Workspace Directory free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

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/mcp`

the first call

```
do {
  action: "gws_directory.customers.get",
  intent: "check which Google Workspace Directory account is connected"
}
# Get one customer · read · 1 upstream call
```

- 128 actions in one signed file
- 46 read look, never change
- 54 write create and update
- 28 wait for a yes destructive, confirmed first

Set up

## Connect Google Workspace Directory in three steps.

1. 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`
2. 02
   ### Connect Google Workspace Directory.
   OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Workspace Directory, 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 Directory needs an OAuth app of your own, registered in its developer portal. actionlake has no Google Workspace Directory app to lend you.
   - `access_token` Access token from one sign-in with your own OAuth app
   - `refresh_token` Refresh token from the same sign-in; the access token is renewed from it
   - `client_id` Google OAuth client id
   - `client_secret` Google OAuth client secret
   ```
   account { op: "connections.requirements", service: "gws_directory" }
   # free: exactly what to paste, and what is found for you
   ```
3. 03
   ### Make the first call. Check before a write.
   Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free.
   ```
   do    { action: "gws_directory.customers.get" }
   # get one customer · read · 1 upstream call
   check { action: "gws_directory.users.create", input: { … } }
   # free: inputs, permissions, cost and confirmations, nothing sent
   ```

Google Workspace Directory at a glance

**Sign-in**

OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Workspace Directory, 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_token` `refresh_token` `client_id` `client_secret`

**Limits we pace to**

2,400 calls a minute, per connection

**API covered**

Google Workspace Directory API 1`admin.googleapis.com/admin/directory/v1`

**Built from**

Google Workspace Directory's documentation, read 15 September 2026[admin.googleapis.com](https://admin.googleapis.com/$discovery/rest?version=directory_v1)

**Service file**

Version 2.0.0, signed (Ed25519)

**Cached reads**

44 of 46 reads, for up to an hour; a write clears what it affects

**Ready-made plans**

8 in the store

**Shared entities**

5, so ask can line Google Workspace Directory 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 Directory.

128 actions in 10 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

- **46** read look, never change
- **54** write create and update
- **28** destructive wait for a confirmation

1. ### Directory
   31
   8 read · 16 write · 7 destructive
   List users · Create a user · Create a guest user · Get one user
2. ### Resources
   19
   6 read · 10 write · 3 destructive
   List buildings · Create a building · List calendar resources · Create a calendar resource
3. ### Groups
   16
   6 read · 7 write · 3 destructive
   List groups · Create a group · Get one group · Update a group
4. ### Printing
   15
   5 read · 6 write · 4 destructive
   List printers · Create a printer · List supported printer models · Get one printer
5. ### Devices
   14
   6 read · 6 write · 2 destructive
   List ChromeOS devices · Get one ChromeOS device · List mobile devices · Run an action on a ChromeOS device
6. ### Access
   11
   5 read · 3 write · 3 destructive
   List admin roles · Create an admin role · Get one admin role · Update an admin role
7. ### Security
   10
   5 read · 2 write · 3 destructive
   List application-specific passwords · List OAuth tokens · Get one application-specific password · Get one OAuth token
8. ### Domains
   8
   4 read · 2 write · 2 destructive
   Create a domain alias · Create a domain · List domain aliases · List domains

**2 more areas · 4 actions**

- Tenant **3**
- Notifications **1**

Top actions

## The Google Workspace Directory API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 87 of Google Workspace Directory's 95 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_directory.users.list` List users | Retrieves a paginated list of either deleted users or all users in a domain. | read | `identity.user.list` 474 connectors |
| `gws_directory.groups.list` List groups | Retrieves all groups of a domain or of a user given a userKey (paginated). | read | `identity.group.list` 262 connectors |
| `gws_directory.users.create` Create a user | Creates a user. Mutate calls immediately following user creation might sometimes fail as the user isn't fully created due to propagation delay in our… | write | `identity.user.create` 262 connectors |
| `gws_directory.groups.create` Create a group | Creates a group. | write | `identity.group.create` 205 connectors |
| `gws_directory.roles.list` List admin roles | Retrieves a paginated list of all the roles in a domain. | read | `identity.role.list` 184 connectors |
| `gws_directory.chromeosdevices.list` List ChromeOS devices | Retrieves a paginated list of Chrome OS devices within an account. | read | `device.endpoint.list` 65 connectors |
| `gws_directory.users.delete` Delete a user | Deletes a user. | destructive | `identity.user.delete` 253 connectors |
| `gws_directory.roles.create` Create an admin role | Creates a role. | write | `identity.role.create` 105 connectors |
| `gws_directory.members.list` List group members | Retrieves a paginated list of all members in a group. This method times out after 60 minutes. For more information, see [Troubleshoot error… | read | `identity.group_member.list` 103 connectors |
| `gws_directory.chromeosdevices.get` Get one ChromeOS device | Retrieves a Chrome OS device's properties. | read | `device.endpoint.get` 57 connectors |
| `gws_directory.asps.list` List application-specific passwords | Lists the ASPs issued by a user. | read | `identity.api_key.list` 96 connectors |
| `gws_directory.members.patch` Update a group member | Updates the membership properties of a user in the specified group. This method supports [patch… | write | `identity.group_member.update` 34 connectors |

Try it

## Prompts to paste into Claude.

Each one names the Google Workspace Directory actions it will call, so you know what it reads and what it changes before you send it.

1. Read read
   Which Google Workspace Directory devices have not checked in for a week?
   calls `gws_directory.chromeosdevices.list`
2. Plan destructive
   Lock down a compromised account in Google Workspace Directory. Ask me before anything is sent or changed.
   calls `gws_directory.users.get` `gws_directory.tokens.list` `gws_directory.asps.list` `gws_directory.users.patch` `gws_directory.users.sign_out` +2 more
3. Plan destructive
   Offboard a departing user in Google Workspace Directory. Ask me before anything is sent or changed.
   calls `gws_directory.users.get` `gws_directory.tokens.list` `gws_directory.asps.list` `gws_directory.users.patch` `gws_directory.users.sign_out` +1 more
4. Write write
   Create a user in Google Workspace Directory. Show me exactly what you will send before you save it.
   calls `gws_directory.users.create`

The plan store

## Ready-made plans for Google Workspace Directory.

8 plans in the store. Install one and your agent runs it by name; the reply says which connections are still missing. A schedule can run a plan on a timetable. There are no triggers or webhooks, by design.

1. ### Audit suspended accounts and their lingering access
   Use it when You need a report of suspended accounts that still hold OAuth tokens, app passwords or aliases.
   **Effect**
   read
   **Steps**
   3 · loops
   **Install**
   `gws_directory-suspended-account-audit`
2. ### Review who holds admin roles
   Use it when You need to see which accounts hold which admin roles and what privileges those roles carry.
   **Effect**
   read
   **Steps**
   4 · loops
   **Install**
   `gws_directory-admin-privilege-review`
3. ### Onboard a new hire
   Use it when A new employee is starting and needs a mailbox, an alias and their team group memberships created.
   A person decides Create _primary email_ in _name_ and add to group _group key_.
   **Effect**
   write
   **Steps**
   6
   **Needs**
   primary email, name, password, org unit path and group key
   **Install**
   `gws_directory-onboard-new-hire`
4. ### Retire a batch of ChromeOS devices
   Use it when A set of Chromebooks in one org unit is being returned or recycled and must be deprovisioned together.
   A person decides Deprovision _number of items_ ChromeOS devices in _org unit path_ with reason _deprovision reason_.
   **Effect**
   write
   **Steps**
   6 · loops
   **Needs**
   org unit path and deprovision reason
   **Install**
   `gws_directory-retire-chromebook-fleet`
5. ### Add a domain and its alias to the tenant
   Use it when A newly acquired or rebranded domain has to be registered on the tenant along with an alias.
   A person decides Add domain _domain name_ with alias _alias domain_ to the tenant.
   **Effect**
   write
   **Steps**
   7
   **Needs**
   domain name and alias domain
   **Install**
   `gws_directory-add-verified-domain`
6. ### Clean suspended members out of a group
   Use it when A group still lists suspended or departed accounts as members and needs pruning.
   A person decides Remove suspended accounts from _email_, which currently has _number of items_ members.
   **Effect**
   destructive
   **Steps**
   6 · loops
   **Needs**
   group key
   **Install**
   `gws_directory-group-membership-cleanup`
7. ### Offboard a departing user
   Use it when An employee has left and their Google Workspace account must be suspended and its access revoked.
   A person decides Suspend _primary email_, sign out all sessions and revoke _number of items_ OAuth tokens.
   **Effect**
   destructive
   **Steps**
   7 · loops
   **Needs**
   user key
   **Install**
   `gws_directory-offboard-departing-user`
8. ### Lock down a compromised account
   Use it when An account is suspected of being compromised and must be locked down and its sessions and credentials cut.
   A person decides Lock down _primary email_: reset password, sign out all sessions and drop _number of items_ app passwords.
   **Effect**
   destructive
   **Steps**
   8 · loops
   **Needs**
   user key and new password
   **Install**
   `gws_directory-reset-compromised-account`

install a plan

```
account { op: "plans.install", slug: "gws_directory-suspended-account-audit" }
# then ask for it by name; a schedule can run it on a timetable
```

Governance for Google Workspace Directory

## Destructive actions wait for a yes.

28 Google Workspace Directory actions are destructive. These are all of them:

- Delete a user `gws_directory.users.delete`
- Delete a group `gws_directory.groups.delete`
- Delete an admin role `gws_directory.roles.delete`
- Delete a group member `gws_directory.members.delete`
- Grant or revoke super-admin `gws_directory.users.make_admin`
- Delete a mobile device `gws_directory.mobiledevices.delete`
- Sign a user out everywhere `gws_directory.users.sign_out`
- Delete an org unit `gws_directory.orgunits.delete`
- Delete a role assignment `gws_directory.role_assignments.delete`
- Create a role assignment `gws_directory.role_assignments.create`
- Delete a domain `gws_directory.domains.delete`
- Delete a domain alias `gws_directory.domain_aliases.delete`
- Delete an application-specific password `gws_directory.asps.delete`
- Delete an OAuth token `gws_directory.tokens.delete`
- Invalidate verification codes `gws_directory.verification_codes.invalidate`
- Delete a user photo `gws_directory.user_photos.delete`
- Delete a custom schema `gws_directory.schemas.delete`
- Delete a user alias `gws_directory.user_aliases.delete`
- Delete a group alias `gws_directory.group_aliases.delete`
- Stop a notification channel `gws_directory.channels.stop`
- Issue a command to a ChromeOS device `gws_directory.chromeos_fleet.issue_command`
- Delete a building `gws_directory.buildings.delete`
- Delete a calendar resource `gws_directory.calendars.delete`
- Delete a resource feature `gws_directory.features.delete`
- Delete a printer `gws_directory.printers.delete`
- Delete many printers at once `gws_directory.printers.batch_delete`
- Delete a print server `gws_directory.print_servers.delete`
- Delete many print servers at once `gws_directory.print_servers.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.

do gws_directory.users.delete confirm_policy: **human**

Delete a user?

**intent:** the user asked me to delete a user

run suspended · waiting for a named person · key _gws-directory-agent_ cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

```
account {
  op: "keys.create", name: "gws-directory-agent",
  allowed_actions: ["gws_directory.*"], cap_calls: 2000,
  confirm_policy: "human_for_writes",
  approval_rules: [
    { match: "gws_directory.users.delete", approver: "lead@example.com" },
    { match: "gws_directory.groups.delete", approver: "lead@example.com" },
    { match: "gws_directory.roles.delete", approver: "lead@example.com" }
  ]
}
```

Illustrative. Scoped to Google Workspace Directory only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

## What Google Workspace Directory costs on actionlake.

Every Google Workspace Directory action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Google Workspace Directory 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.

- 1 upstream call per action all 128 Google Workspace Directory actions
- 128 actions page each page of a long list is one call
- 44 reads can be cached a cache hit costs nothing
- 100,000 calls a month, free paid plans from US$49 a month for 250,000

[See pricing](https://actionlake.com/pricing)

Action index

## Every Google Workspace Directory action.

128 actions by area: the id your agent calls, what it does, and its effect.

**Directory 31**

- `gws_directory.orgunits.create` Create an org unit write
- `gws_directory.orgunits.delete` Delete an org unit destructive
- `gws_directory.orgunits.get` Get one org unit read
- `gws_directory.orgunits.list` List org units read
- `gws_directory.orgunits.patch` Update an org unit write
- `gws_directory.orgunits.update` Replace an org unit write
- `gws_directory.schemas.create` Create a custom schema write
- `gws_directory.schemas.delete` Delete a custom schema destructive
- `gws_directory.schemas.get` Get one custom schema read
- `gws_directory.schemas.list` List custom schemas read
- `gws_directory.schemas.patch` Update a custom schema write
- `gws_directory.schemas.update` Replace a custom schema write
- `gws_directory.user_aliases.create` Create a user alias write
- `gws_directory.user_aliases.delete` Delete a user alias destructive
- `gws_directory.user_aliases.list` List user aliases read
- `gws_directory.user_aliases.watch` Watch user aliases for changes write
- `gws_directory.user_photos.delete` Delete a user photo destructive
- `gws_directory.user_photos.get` Get one user photo read
- `gws_directory.user_photos.patch` Update a user photo write
- `gws_directory.user_photos.update` Replace a user photo write
- `gws_directory.users.create` Create a user write
- `gws_directory.users.create_guest` Create a guest user write
- `gws_directory.users.delete` Delete a user destructive
- `gws_directory.users.get` Get one user read
- `gws_directory.users.list` List users read
- `gws_directory.users.make_admin` Grant or revoke super-admin destructive
- `gws_directory.users.patch` Update a user write
- `gws_directory.users.sign_out` Sign a user out everywhere destructive
- `gws_directory.users.undelete` Restore a deleted user write
- `gws_directory.users.update` Replace a user write
- `gws_directory.users.watch` Watch users for changes write

**Resources 19**

- `gws_directory.buildings.create` Create a building write
- `gws_directory.buildings.delete` Delete a building destructive
- `gws_directory.buildings.get` Get one building read
- `gws_directory.buildings.list` List buildings read
- `gws_directory.buildings.patch` Update a building write
- `gws_directory.buildings.update` Replace a building write
- `gws_directory.calendars.create` Create a calendar resource write
- `gws_directory.calendars.delete` Delete a calendar resource destructive
- `gws_directory.calendars.get` Get one calendar resource read
- `gws_directory.calendars.list` List calendar resources read
- `gws_directory.calendars.patch` Update a calendar resource write
- `gws_directory.calendars.update` Replace a calendar resource write
- `gws_directory.features.create` Create a resource feature write
- `gws_directory.features.delete` Delete a resource feature destructive
- `gws_directory.features.get` Get one resource feature read
- `gws_directory.features.list` List resource features read
- `gws_directory.features.patch` Update a resource feature write
- `gws_directory.features.rename` Rename a resource feature write
- `gws_directory.features.update` Replace a resource feature write

**Groups 16**

- `gws_directory.group_aliases.create` Create a group alias write
- `gws_directory.group_aliases.delete` Delete a group alias destructive
- `gws_directory.group_aliases.list` List group aliases read
- `gws_directory.groups.create` Create a group write
- `gws_directory.groups.delete` Delete a group destructive
- `gws_directory.groups.get` Get one group read
- `gws_directory.groups.list` List groups read
- `gws_directory.groups.patch` Update a group write
- `gws_directory.groups.update` Replace a group write
- `gws_directory.members.create` Create a group member write
- `gws_directory.members.delete` Delete a group member destructive
- `gws_directory.members.get` Get one group member read
- `gws_directory.members.has_member` Check group membership read
- `gws_directory.members.list` List group members read
- `gws_directory.members.patch` Update a group member write
- `gws_directory.members.update` Replace a group member write

**Printing 15**

- `gws_directory.print_servers.batch_create` Create many print servers at once write
- `gws_directory.print_servers.batch_delete` Delete many print servers at once destructive
- `gws_directory.print_servers.create` Create a print server write
- `gws_directory.print_servers.delete` Delete a print server destructive
- `gws_directory.print_servers.get` Get one print server read
- `gws_directory.print_servers.list` List print servers read
- `gws_directory.print_servers.patch` Update a print server write
- `gws_directory.printers.batch_create` Create many printers at once write
- `gws_directory.printers.batch_delete` Delete many printers at once destructive
- `gws_directory.printers.create` Create a printer write
- `gws_directory.printers.delete` Delete a printer destructive
- `gws_directory.printers.get` Get one printer read
- `gws_directory.printers.list` List printers read
- `gws_directory.printers.list_models` List supported printer models read
- `gws_directory.printers.patch` Update a printer write

**Devices 14**

- `gws_directory.chromeos_commands.get` Get one ChromeOS command read
- `gws_directory.chromeos_fleet.batch_change_status` Change the status of many ChromeOS devices write
- `gws_directory.chromeos_fleet.count` Count ChromeOS devices by auto-update expiry read
- `gws_directory.chromeos_fleet.issue_command` Issue a command to a ChromeOS device destructive
- `gws_directory.chromeosdevices.action` Run an action on a ChromeOS device write
- `gws_directory.chromeosdevices.get` Get one ChromeOS device read
- `gws_directory.chromeosdevices.list` List ChromeOS devices read
- `gws_directory.chromeosdevices.move_to_orgunit` Move ChromeOS devices to an org unit write
- `gws_directory.chromeosdevices.patch` Update a ChromeOS device write
- `gws_directory.chromeosdevices.update` Replace a ChromeOS device write
- `gws_directory.mobiledevices.action` Run an action on a mobile device write
- `gws_directory.mobiledevices.delete` Delete a mobile device destructive
- `gws_directory.mobiledevices.get` Get one mobile device read
- `gws_directory.mobiledevices.list` List mobile devices read

**Access 11**

- `gws_directory.privileges.list` List privileges read
- `gws_directory.role_assignments.create` Create a role assignment destructive
- `gws_directory.role_assignments.delete` Delete a role assignment destructive
- `gws_directory.role_assignments.get` Get one role assignment read
- `gws_directory.role_assignments.list` List role assignments read
- `gws_directory.roles.create` Create an admin role write
- `gws_directory.roles.delete` Delete an admin role destructive
- `gws_directory.roles.get` Get one admin role read
- `gws_directory.roles.list` List admin roles read
- `gws_directory.roles.patch` Update an admin role write
- `gws_directory.roles.update` Replace an admin role write

**Security 10**

- `gws_directory.asps.delete` Delete an application-specific password destructive
- `gws_directory.asps.get` Get one application-specific password read
- `gws_directory.asps.list` List application-specific passwords read
- `gws_directory.tokens.delete` Delete an OAuth token destructive
- `gws_directory.tokens.get` Get one OAuth token read
- `gws_directory.tokens.list` List OAuth tokens read
- `gws_directory.two_step_verification.turn_off` Turn off two-step verification write
- `gws_directory.verification_codes.generate` Generate verification codes write
- `gws_directory.verification_codes.invalidate` Invalidate verification codes destructive
- `gws_directory.verification_codes.list` List verification codes read

**Domains 8**

- `gws_directory.domain_aliases.create` Create a domain alias write
- `gws_directory.domain_aliases.delete` Delete a domain alias destructive
- `gws_directory.domain_aliases.get` Get one domain alias read
- `gws_directory.domain_aliases.list` List domain aliases read
- `gws_directory.domains.create` Create a domain write
- `gws_directory.domains.delete` Delete a domain destructive
- `gws_directory.domains.get` Get one domain read
- `gws_directory.domains.list` List domains read

**Tenant 3**

- `gws_directory.customers.get` Get one customer read
- `gws_directory.customers.patch` Update a customer write
- `gws_directory.customers.update` Replace a customer write

**Notifications 1**

- `gws_directory.channels.stop` Stop a notification channel destructive

Questions

## The Google Workspace Directory MCP server, answered.

**Is there a Google Workspace Directory MCP server for Claude?**

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 128 Google Workspace Directory actions across directory, resources, groups and printing, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Google Workspace Directory.

**What do I need to connect Google Workspace Directory?**

Your own Google Workspace Directory OAuth app, registered with Google Workspace Directory (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no Google Workspace Directory 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_directory" } lists exactly what to paste.

**Can an AI agent delete or change things in Google Workspace Directory?**

Only if its key allows it, and only with an explicit confirmation. 28 Google Workspace Directory actions are destructive, including delete a user, delete a group and delete an admin role. 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 Directory API limit?**

actionlake paces every call to the limits in the Google Workspace Directory service file: 2,400 calls a minute per connection. Repeated reads are answered from cache (44 Google Workspace Directory actions can be), which never reaches Google Workspace Directory.

**What does a Google Workspace Directory action cost?**

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (128 Google Workspace Directory actions page). Cache hits, searches, dry runs and calls Google Workspace Directory 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 Directory API does it cover?**

The Google Workspace Directory API 1 at admin.googleapis.com/admin/directory/v1. It is built from Google Workspace Directory's documentation as read on 15 September 2026. 128 actions in 10 areas, each one in the signed service file (version 2.0.0).

**Does actionlake keep my Google Workspace Directory data, and where?**

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, 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 Directory 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.

## More connectors like Google Workspace Directory

Shares the most action names with

- [Microsoft 365 Users 51](https://actionlake.com/connectors/microsoft-365-users)
- [PingOne Platform API 30](https://actionlake.com/connectors/pingone-platform-api)
- [Clerk 27](https://actionlake.com/connectors/clerk)
- [WorkOS 23](https://actionlake.com/connectors/workos)
- [OneLogin 20](https://actionlake.com/connectors/onelogin)
- [Doppler 18](https://actionlake.com/connectors/doppler)

Joins with, on shared entities

- [Sophos Central 5](https://actionlake.com/connectors/sophos-central)
- [Commvault Cloud 4](https://actionlake.com/connectors/commvault-cloud)
- [CIPP 4](https://actionlake.com/connectors/cipp)
- [Flagsmith 4](https://actionlake.com/connectors/flagsmith)
- [Grafana 4](https://actionlake.com/connectors/grafana)
- [Zabbix 4](https://actionlake.com/connectors/zabbix)

Browse

- [All Identity & security connectors](https://actionlake.com/connectors/category/identity-and-security)
- [All connectors](https://actionlake.com/connectors)
- [How actionlake compares](https://actionlake.com/compare)

actionlake is independent. It is not made or endorsed by Google Workspace Directory; the name is the vendor's own. Counts are from the Google Workspace Directory service file, version 2.0.0.

## Give your agent Google Workspace Directory today.

[Connect Google Workspace Directory free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

---

Source: https://actionlake.com/connectors/google-workspace-directory
More: https://actionlake.com/llms.txt
