Connectors · Email & messaging

Google Chat MCP server for AI agents.

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

Connect Google Chat 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

53actionsin one signed file
23readlook, never change
23writecreate and update
7wait for a yesdestructive, confirmed first

Set up

Connect Google Chat 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 Chat.
OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Chat, 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 Chat needs an OAuth app of your own, registered in its developer portal. actionlake has no Google Chat 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 Google Chat API and…
- client_secretGoogle OAuth client secret
```
account { op: "connections.requirements", service: "google_chat" }
# 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: "google_chat.spaces.list" }# spaces: list · read · 1 upstream callcheck { action: "google_chat.messages.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Google Chat at a glance

Sign-in: OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Chat, 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: 10 calls a second, per connection
API covered: Google Chat API v1 (Discovery revision 20261016)chat.googleapis.com
Built from: Google Chat's documentation, read 22 October 2026chat.googleapis.com developers.google.com
Service file: Version 1.0.0, signed (Ed25519)
Cached reads: 23 of 23 reads, for up to 2 minutes; a write clears what it affects
Shared entities: 2, so ask can line Google Chat 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 Chat.

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

23readlook, never change
23writecreate and update
7destructivewait for a confirmation

Spaces
10
5 read · 4 write · 1 destructive
Spaces: list · Spaces: create · Spaces: get · Spaces: patch
Messages
8
3 read · 4 write · 1 destructive
Messages: list · Messages: create · Messages: get · Messages: patch
Availability
5
1 read · 4 write · 0 destructive
Availability: get · Availability: mark as active · Availability: mark as away · Availability: mark as do not disturb
Members
5
2 read · 2 write · 1 destructive
Members: list · Members: patch · Members: get · Members: create
Sections
5
1 read · 3 write · 1 destructive
Sections: create · Sections: list · Sections: position · Sections: delete
Custom emojis
4
2 read · 1 write · 1 destructive
Custom emojis: create · Custom emojis: list · Custom emojis: get · Custom emojis: delete
Message pins
3
1 read · 1 write · 1 destructive
Message pins: create · Message pins: list · Message pins: delete
Reactions
3
1 read · 1 write · 1 destructive
Reactions: create · Reactions: list · Reactions: delete

6 more areas · 10 actions

Section items 2
Space events 2
Space notification settings 2
Space read state 2
Attachments 1
Thread read state 1

Top actions

The Google Chat API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 15 of Google Chat's 15 action names are shared with at least one other connector, so an agent learns them once.

Action	What it does	Effect	Same name in
`google_chat.messages.list`Messages: list	Lists messages in a space that the caller is a member of, including messages from blocked members and spaces.	read	`comm.message.list`42 connectors
`google_chat.spaces.list`Spaces: list	Lists spaces the caller is a member of.	read	`comm.channel.list`27 connectors
`google_chat.messages.create`Messages: create	Creates a message in a Google Chat space.	write	`comm.message.create`25 connectors
`google_chat.spaces.create`Spaces: create	Creates a space.	write	`comm.channel.create`16 connectors
`google_chat.messages.delete`Messages: delete	Deletes a message.	destructive	`comm.message.delete`27 connectors
`google_chat.members.list`Members: list	Lists memberships in a space.	read	`comm.channel_member.list`12 connectors
`google_chat.members.patch`Members: patch	Updates a membership.	write	`comm.channel_member.update`4 connectors
`google_chat.spaces.setup`Spaces: setup	Creates a space and adds specified users to it.	write	this connector
`google_chat.members.create`Members: create	Creates a membership for the calling Chat app, a user, or a Google Group.	write	this connector
`google_chat.reactions.list`Reactions: list	Lists reactions to a message.	read	this connector
`google_chat.reactions.create`Reactions: create	Creates a reaction and adds it to a message.	write	this connector
`google_chat.spaces.find_group_chats`Spaces: find group chats	Returns all spaces with `spaceType == GROUP_CHAT`, whose human memberships contain exactly the calling user, and the users specified in…	read	this connector

Try it

Prompts to paste into Claude.

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

Readread
Spaces: list in Google Chat and tell me what stands out.
callsgoogle_chat.spaces.list
Writewrite
Messages: create in Google Chat. Show me exactly what you will send before you save it.
callsgoogle_chat.messages.create

Governance for Google Chat

Destructive actions wait for a yes.

7 Google Chat actions are destructive. These are all of them:

Messages: deletegoogle_chat.messages.delete
Spaces: deletegoogle_chat.spaces.delete
Members: deletegoogle_chat.members.delete
Reactions: deletegoogle_chat.reactions.delete
Sections: deletegoogle_chat.sections.delete
Message pins: deletegoogle_chat.message_pins.delete
Custom emojis: deletegoogle_chat.custom_emojis.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.

dogoogle_chat.messages.deleteconfirm_policy: human

Messages: delete?

intent: the user asked me to messages: delete

run suspended · waiting for a named person · key google-chat-agent cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

account {  op: "keys.create", name: "google-chat-agent",  allowed_actions: ["google_chat.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "google_chat.messages.delete", approver: "[email protected]" },    { match: "google_chat.spaces.delete", approver: "[email protected]" },    { match: "google_chat.members.delete", approver: "[email protected]" }  ]}

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

Cost

What Google Chat costs on actionlake.

Every Google Chat action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Google Chat 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 53 Google Chat actions
11actions pageeach page of a long list is one call
23reads 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 Chat action.

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

Spaces10

google_chat.spaces.complete_importSpaces: complete importwrite
google_chat.spaces.createSpaces: createwrite
google_chat.spaces.deleteSpaces: deletedestructive
google_chat.spaces.find_direct_messageSpaces: find direct messageread
google_chat.spaces.find_group_chatsSpaces: find group chatsread
google_chat.spaces.getSpaces: getread
google_chat.spaces.listSpaces: listread
google_chat.spaces.patchSpaces: patchwrite
google_chat.spaces.searchSpaces: searchread
google_chat.spaces.setupSpaces: setupwrite

Messages8

google_chat.messages.createMessages: createwrite
google_chat.messages.deleteMessages: deletedestructive
google_chat.messages.getMessages: getread
google_chat.messages.listMessages: listread
google_chat.messages.patchMessages: patchwrite
google_chat.messages.replace_cardsMessages: replace cardswrite
google_chat.messages.searchMessages: searchread
google_chat.messages.updateMessages: updatewrite

Availability5

google_chat.availability.getAvailability: getread
google_chat.availability.mark_as_activeAvailability: mark as activewrite
google_chat.availability.mark_as_awayAvailability: mark as awaywrite
google_chat.availability.mark_as_do_not_disturbAvailability: mark as do not disturbwrite
google_chat.availability.patchAvailability: patchwrite

Members5

google_chat.members.createMembers: createwrite
google_chat.members.deleteMembers: deletedestructive
google_chat.members.getMembers: getread
google_chat.members.listMembers: listread
google_chat.members.patchMembers: patchwrite

Sections5

google_chat.sections.createSections: createwrite
google_chat.sections.deleteSections: deletedestructive
google_chat.sections.listSections: listread
google_chat.sections.patchSections: patchwrite
google_chat.sections.positionSections: positionwrite

Custom emojis4

google_chat.custom_emojis.createCustom emojis: createwrite
google_chat.custom_emojis.deleteCustom emojis: deletedestructive
google_chat.custom_emojis.getCustom emojis: getread
google_chat.custom_emojis.listCustom emojis: listread

Message pins3

google_chat.message_pins.createMessage pins: createwrite
google_chat.message_pins.deleteMessage pins: deletedestructive
google_chat.message_pins.listMessage pins: listread

Reactions3

google_chat.reactions.createReactions: createwrite
google_chat.reactions.deleteReactions: deletedestructive
google_chat.reactions.listReactions: listread

Section items2

google_chat.section_items.listSection items: listread
google_chat.section_items.moveSection items: movewrite

Space events2

google_chat.space_events.getSpace events: getread
google_chat.space_events.listSpace events: listread

Space notification settings2

google_chat.space_notification_settings.getSpace notification settings: getread
google_chat.space_notification_settings.patchSpace notification settings: patchwrite

Space read state2

google_chat.space_read_state.getSpace read state: getread
google_chat.space_read_state.updateSpace read state: updatewrite

Attachments1

google_chat.attachments.getAttachments: getread

Thread read state1

google_chat.thread_read_state.getThread read state: getread

Questions

The Google Chat MCP server, answered.

Is there a Google Chat MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 53 Google Chat actions across spaces, messages, availability and members, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Google Chat.

What do I need to connect Google Chat?

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

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

Only if its key allows it, and only with an explicit confirmation. 7 Google Chat actions are destructive, including messages: delete, spaces: delete and members: 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 Chat API limit?

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

What does a Google Chat action cost?

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

The Google Chat API v1 (Discovery revision 20261016) at chat.googleapis.com. It is built from Google Chat's documentation as read on 22 October 2026. 53 actions in 14 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Google Chat data, and where?

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

Connect Google Chat free See pricing

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

Google Chat MCP server for AI agents.

Connect Google Chat in three steps.

Add actionlake to Claude.

Connect Google Chat.

Make the first call. Check before a write.

What an AI agent can do in Google Chat.

Spaces

Messages

Availability

Members

Sections

Custom emojis

Message pins

Reactions