Google Chat

Google Chat

This connector reads and writes Google Chat as the signed-in user through the Google Chat API v1 (https://chat.googleapis.com/v1): spaces, group chats and direct messages, their members, messages and threads, reactions, attachments and the space event log. It posts and edits messages in the user's name, exactly as if they typed them. Google Chat API user access needs a Google Workspace account (Business, Enterprise, Education); personal Gmail accounts cannot use it.

Setup (one-time, about 15 minutes)

1. Open https://console.cloud.google.com, pick or create a project, then APIs & Services → Library → enable Google Chat API.
2. Configure the Chat app (required by Google for user-authorized Chat API calls): open APIs & Services → Enabled APIs → Google Chat API → Configuration (https://console.cloud.google.com/apis/api/chat.googleapis.com/hangouts-chat). Fill in App name (e.g. AnythingMCP), Avatar URL (any HTTPS link to a square PNG or JPEG) and Description, leave Interactive features turned off, and click Save. Without it, posting messages fails with "Google Chat app not found".
3. APIs & Services → OAuth consent screen: choose Internal (Google Workspace). External apps with the publishing status Testing lose their refresh token after 7 days.
4. APIs & Services → Credentials → Create credentials → OAuth client ID → application type Web application → add the authorized redirect URI <your AnythingMCP URL>/api/mcp-oauth/callback (on AnythingMCP Cloud: https://cloud.anythingmcp.com/api/mcp-oauth/callback).
5. Paste the client ID and secret into GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET and install the connector.
6. On the connector page, click Authorize with Provider and sign in with the Google Workspace account the AI should act as. The refresh token is stored encrypted and access tokens are renewed automatically.

One Google client for all Google connectors: the same Cloud project and OAuth client can serve every Google connector (Gmail, Calendar, Drive, Sheets, Docs, Chat...). Enable each API in that project and reuse GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET; each connector asks only for its own scopes.

Scopes: chat.spaces.readonly (see spaces), chat.messages (read, post, edit and delete the user's messages and reactions) and chat.memberships.readonly (see members). The connector cannot create spaces or add and remove people. For a read-only setup, change chat.messages to https://www.googleapis.com/auth/chat.messages.readonly in the connector's OAuth settings, authorize again, and disable google_chat_create_message, google_chat_reply_in_thread, google_chat_update_message and google_chat_add_reaction.

Switched off at install: google_chat_delete_message and google_chat_delete_reaction; a deleted message cannot be restored, so an admin switches them on when the team needs them.

Names and ids: Chat names resources by path: a space is spaces/AAAAMpdlehY, a message spaces/AAAAMpdlehY/messages/ZJ7sqN6qlYk.ZJ7sqN6qlYk, a thread spaces/AAAAMpdlehY/threads/FHT5Rc21TfA, a person users/123456789. Tools take the parts separately: space_id is what follows spaces/ (AAAAMpdlehY), message_id what follows /messages/. thread_name and user take the full name. People are users/{id}; in filters and google_chat_find_direct_message an email works as well (users/[email protected]). Senders and members usually come back without a display name: match people by id or email.

Finding a conversation

• google_chat_list_spaces: everything the user belongs to, filter by spaceType (SPACE, GROUP_CHAT, DIRECT_MESSAGE). Direct messages have no displayName.
• google_chat_search_spaces: named spaces by name, e.g. display_name:"Marketing" AND space_type = "SPACE".
• google_chat_find_direct_message: the direct message with one person, e.g. users/[email protected] (404 when none exists yet; this connector cannot open a new one).
• google_chat_get_space: details of one space; google_chat_list_members: who is in it.

Reading messages

• google_chat_list_messages: a space's messages, oldest first (order_by create_time desc for the latest). Narrow by time with create_time > "2026-10-01T00:00:00Z" and to one thread with thread.name = spaces/.../threads/.... Default page size 25.
• google_chat_search_messages: keywords across all spaces and direct messages, newest first, with conditions such as sender.name = "users/[email protected]", space.name = "spaces/AAAAMpdlehY", createTime >= "2026-10-01T00:00:00Z", annotations.user_mentions.user.name:me (messages mentioning the user), attachment:*, has_link(), is_unread(). It skips messages from Chat apps and muted spaces.
• google_chat_get_message: one message. google_chat_list_reactions: who reacted with what.
• google_chat_list_space_events: the change log of a space for the last 28 days, e.g. event_types:"google.workspace.chat.message.v1.created". Types: google.workspace.chat.message.v1.created|updated|deleted, google.workspace.chat.reaction.v1.created|deleted, google.workspace.chat.membership.v1.created|updated|deleted, google.workspace.chat.space.v1.updated (one per event_types: condition, joined with OR).
• Attachments: a message's attachment[] lists files. google_chat_get_attachment reads one's metadata; google_chat_download_attachment downloads an uploaded file with its attachmentDataRef.resourceName. Google Drive files (source DRIVE_FILE) are read with the Google Drive connector via driveDataRef.driveFileId. Times are RFC 3339 in UTC (2026-10-29T14:05:31.123Z). Card content is left out of answers.

Writing

• google_chat_create_message posts as the user; in threaded spaces it starts a new thread. google_chat_reply_in_thread answers in the thread named by a message's thread.name. Pass request_id when you might retry, so nothing is posted twice.
• google_chat_update_message replaces the text of the user's own message. google_chat_add_reaction reacts with a unicode emoji.
• Text formatting: *bold*, _italic_, ~strike~, `code`, <https://example.com|label>; mention with <users/123456789> or <users/all>. A message is at most 32,000 bytes. Always confirm with the user before posting in their name.

Pagination: answers carry nextPageToken while more results exist; call the same tool again with the same arguments and page_token set to it.

Limits: Google Chat allows about 3,000 reads per minute per project and, per space, about 1 message a second; a throttled call answers 429 RESOURCE_EXHAUSTED. Wait and retry.

Common errors

• 401: the authorization expired or was revoked; click Authorize with Provider again.
• 403 PERMISSION_DENIED: the Chat API is not enabled, a scope is missing, the account is not a Google Workspace account, or the user may not do this in that space (e.g. edit someone else's message).
• 404 NOT_FOUND: wrong space or message id, the user is not a member, or (posting) the Chat app from setup step 2 is not configured.
• 400 INVALID_ARGUMENT: a filter Google does not accept; check quotes, operators and field names in the tool descriptions.

Out of scope here: creating spaces, adding or removing members, uploading files, cards and app-only features (Chat apps posting as a bot), pinned messages and read state.