A1-x-Tech/mcp-google-chat

**English** | Русский
**A1 Google Chat MCP** lets an AI app work in Google Chat in plain language. Find the right space or direct message, catch up on a conversation, reply in a thread, react with an emoji and manage who is in a space.
It uses the Google Chat API with your Google account and acts as the signed-in user: messages send under your name, and only your own messages and reactions can be edited or deleted. It makes the limits of the Chat API explicit instead of implying that every chat task is possible.
- **20 tools.** Connect from the chat, discover spaces and direct messages, read and send messages with thread control, manage emoji reactions, read attachment metadata and manage membership.
- **Connects from the conversation.** Say "connect Google Chat": the server walks you through the OAuth client, catches Google's redirect on 127.0.0.1 with PKCE and keeps the tokens itself — no config files, no restart.
- **You act as yourself.** Sends appear under your name; edits and deletes stop at your own messages and reactions.
- **A send is never replayed.** After an ambiguous failure the server does not retry a write — a replayed send would be a duplicate message in a real room.
- **Minimal Google scopes.** The server sends whatever token you minted; grant scopes per task — read-only ones are enough for browsing spaces and messages.
Start with a read-only question:
> Show today’s messages in the team space and summarize what was decided.
Connect the server · Explore use cases · Open technical documentation
---
See it work in a minute
> **You:** What was discussed in the release space today?
>
> **Assistant:** Lists today’s messages with senders and threads. Nothing changes.
>
> **You:** Reply in the deploy thread that the rollout is finished.
>
> **Assistant:** Shows the target space, the thread and the drafted text, then asks for confirmation before sending.
>
> **You:** Confirm.
>
> **Assistant:** Sends the reply under your name in that thread. It does not touch any other message.
Contents
- Quick start
- What you can ask it to do
- How the server acts in Chat
- What can change
- Getting access
- Configuration
- Data, limits and background work
- Technical documentation
- Support
Quick start
You need Node.js 20+ and a Google account with access to Google Chat. Credentials are not required at install time — the server connects from the conversation.
1. Add the server to your AI app.
2. Say "connect Google Chat": the assistant walks you through creating the OAuth client and approving access without editing config files or restarting.
3. Ask the read-only question above.
Codex
**In the app:** open **Settings → MCP servers**, select **Add server**, choose **STDIO**, enter the command npx -y mcp-google-chat@latest, then select **Save**. No environment variables are needed — connect from the chat afterwards.
**From the command line:**
Codex MCP documentation
Claude Code
Claude Code MCP documentation
Claude Desktop
The current official path is **Settings → Extensions**. For a custom desktop extension, open **Advanced settings → Extension Developer → Install Extension…**, select a .mcpb file and follow the prompts.
This repository currently publishes an npm stdio package and does not contain a .mcpb bundle. For Claude Desktop builds that still support local configuration, use the following JSON stdio configuration as a fallback:
In those builds, save it to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows.
Claude Desktop MCP documentation
Cursor
Add this to ~/.cursor/mcp.json on macOS/Linux or %USERPROFILE%\.cursor\mcp.json on Windows:
Cursor MCP documentation
VS Code
Run **MCP: Open User Configuration** and add:
Check it with **MCP: List Servers**.
VS Code MCP documentation
What you can ask it to do