Connectors · Workspace

Google Vault MCP server for AI agents.

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

Connect Google Vault free See 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

33actionsin one signed file
11readlook, never change
13writecreate and update
9wait for a yesdestructive, confirmed first

Set up

Connect Google Vault 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 Vault.
OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Vault, 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 Vault needs an OAuth app of your own, registered in its developer portal. actionlake has no Google Vault app to lend you.
- access_tokenAccess token from one sign-in with your own OAuth app
- refresh_tokenRefresh token from the same sign-in; the access token is renewed from it
- client_idGoogle OAuth client id (Google Cloud console > APIs & Services > Credentials; enable the Vault API)
- client_secretGoogle OAuth client secret
```
account { op: "connections.requirements", service: "gws_vault" }
# free: exactly what to paste, and what is found for you
```

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_vault.matters.list" }# matters: list · read · 1 upstream callcheck { action: "gws_vault.holds.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Google Vault at a glance

Sign-in: OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Vault, 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 Vault API v1 (matters, holds, saved queries, exports, operations) API vault v1 (Discovery revision 20261015)vault.googleapis.com
Built from: Google Vault's documentation, read 23 October 2026vault.googleapis.com developers.google.com
Service file: Version 1.0.0, signed (Ed25519)
Cached reads: 11 of 11 reads, for up to 5 minutes; a write clears what it affects
Shared entities: 1, so ask can line Google Vault 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 Vault.

33 actions in 1 area. Every one carries its effect, so a key can allow the reads and hold the rest.

11readlook, never change
13writecreate and update
9destructivewait for a confirmation

Ediscovery
33
11 read · 13 write · 9 destructive
Hold accounts: list · Exports: create · Exports: list · Hold accounts: create

Top actions

The Google Vault API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems.

Action	What it does	Effect	Same name in
`gws_vault.hold_accounts.list`Hold accounts: list	Lists the accounts covered by a hold.	read	this connector
`gws_vault.holds.list`Holds: list	Lists the holds in a matter.	read	this connector
`gws_vault.exports.list`Exports: list	Lists details about the exports in the specified matter.	read	this connector
`gws_vault.holds.create`Holds: create	Creates a hold in the specified matter.	write	this connector
`gws_vault.matters.list`Matters: list	Lists matters the requestor has access to.	read	this connector
`gws_vault.matters.count`Matters: count	Counts the accounts processed by the specified query.	write	this connector
`gws_vault.exports.create`Exports: create	Creates an export.	write	this connector
`gws_vault.hold_accounts.create`Hold accounts: create	Adds an account to a hold.	write	this connector
`gws_vault.holds.delete`Holds: delete	Removes the specified hold and releases the accounts or organizational unit covered by the hold.	destructive	this connector
`gws_vault.operations.list`Operations: list	Lists operations that match the specified filter in the request.	read	this connector
`gws_vault.saved_queries.list`Saved queries: list	Lists the saved queries in a matter.	read	this connector
`gws_vault.saved_queries.create`Saved queries: create	Creates a saved query.	write	this connector

Try it

Prompts to paste into Claude.

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

Readread
Who has access in Google Vault? List every user and their role.
callsgws_vault.hold_accounts.list
Writewrite
Holds: create in Google Vault. Show me exactly what you will send before you save it.
callsgws_vault.holds.create

Governance for Google Vault

Destructive actions wait for a yes.

9 Google Vault actions are destructive. These are all of them:

Holds: deletegws_vault.holds.delete
Exports: deletegws_vault.exports.delete
Matters: deletegws_vault.matters.delete
Hold accounts: deletegws_vault.hold_accounts.delete
Holds: remove held accountsgws_vault.holds.remove_held_accounts
Matters: remove permissionsgws_vault.matters.remove_permissions
Operations: deletegws_vault.operations.delete
Saved queries: deletegws_vault.saved_queries.delete
Operations: cancelgws_vault.operations.cancel

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.

dogws_vault.holds.deleteconfirm_policy: human

Holds: delete?

intent: the user asked me to holds: delete

run suspended · waiting for a named person · key gws-vault-agent cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

account {  op: "keys.create", name: "gws-vault-agent",  allowed_actions: ["gws_vault.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "gws_vault.holds.delete", approver: "[email protected]" },    { match: "gws_vault.exports.delete", approver: "[email protected]" },    { match: "gws_vault.matters.delete", approver: "[email protected]" }  ]}

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

Cost

What Google Vault costs on actionlake.

Every Google Vault action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Google Vault 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 33 Google Vault actions
5actions pageeach page of a long list is one call
11reads can be cacheda cache hit costs nothing
100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Google Vault action.

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

Ediscovery33

gws_vault.exports.createExports: createwrite
gws_vault.exports.deleteExports: deletedestructive
gws_vault.exports.getExports: getread
gws_vault.exports.listExports: listread
gws_vault.hold_accounts.createHold accounts: createwrite
gws_vault.hold_accounts.deleteHold accounts: deletedestructive
gws_vault.hold_accounts.listHold accounts: listread
gws_vault.holds.add_held_accountsHolds: add held accountswrite
gws_vault.holds.createHolds: createwrite
gws_vault.holds.deleteHolds: deletedestructive
gws_vault.holds.getHolds: getread
gws_vault.holds.listHolds: listread
gws_vault.holds.remove_held_accountsHolds: remove held accountsdestructive
gws_vault.holds.updateHolds: updatewrite
gws_vault.matters.add_permissionsMatters: add permissionswrite
gws_vault.matters.closeMatters: closewrite
gws_vault.matters.countMatters: countwrite
gws_vault.matters.createMatters: createwrite
gws_vault.matters.deleteMatters: deletedestructive
gws_vault.matters.getMatters: getread
gws_vault.matters.listMatters: listread
gws_vault.matters.remove_permissionsMatters: remove permissionsdestructive
gws_vault.matters.reopenMatters: reopenwrite
gws_vault.matters.undeleteMatters: undeletewrite
gws_vault.matters.updateMatters: updatewrite
gws_vault.operations.cancelOperations: canceldestructive
gws_vault.operations.deleteOperations: deletedestructive
gws_vault.operations.getOperations: getread
gws_vault.operations.listOperations: listread
gws_vault.saved_queries.createSaved queries: createwrite
gws_vault.saved_queries.deleteSaved queries: deletedestructive
gws_vault.saved_queries.getSaved queries: getread
gws_vault.saved_queries.listSaved queries: listread

Questions

The Google Vault MCP server, answered.

Is there a Google Vault MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 33 Google Vault actions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Google Vault.

What do I need to connect Google Vault?

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

Can an AI agent delete or change things in Google Vault?

Only if its key allows it, and only with an explicit confirmation. 9 Google Vault actions are destructive, including holds: delete, exports: delete and matters: 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 Vault API limit?

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

What does a Google Vault action cost?

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

The Google Vault API v1 (matters, holds, saved queries, exports, operations) API vault v1 (Discovery revision 20261015) at vault.googleapis.com. It is built from Google Vault's documentation as read on 23 October 2026. 33 actions in 1 area, each one in the signed service file (version 1.0.0).

Does actionlake keep my Google Vault 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 Vault 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 Vault today.