Google Chat MCP Server
Allows posting messages to Google Chat spaces through incoming webhooks. Supports sending messages, replying in threads, sending card-style reports with titles, details, and link buttons, previewing message formatting, and targeting multiple configured spaces.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Google Chat MCP Server tell the alerts space that the deploy is done"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
google-chat-mcp
Post to Google Chat from any MCP client through incoming webhooks.
Requires Node.js 22.18 or later.
Setup
In Google Chat, open the space and go to Apps & integrations > Webhooks > Add webhook. Copy the URL. Anyone with this URL can post to the space, so keep it private.
Add the server to your MCP client's config:
{ "mcpServers": { "google-chat": { "command": "npx", "args": ["-y", "@hungvudang/google-chat-mcp"], "env": { "GOOGLE_CHAT_WEBHOOK": "https://chat.googleapis.com/v1/spaces/..." } } } }To post to several spaces, add one
GOOGLE_CHAT_WEBHOOK_<NAME>per space toenv, for exampleGOOGLE_CHAT_WEBHOOK_ALERTS.Some clients add servers from the command line instead. With Claude Code, for example:
claude mcp add google-chat \ -e GOOGLE_CHAT_WEBHOOK=https://chat.googleapis.com/v1/spaces/... \ -- npx -y @hungvudang/google-chat-mcp
Related MCP server: Google Chat MCP Server
Configuration
Variable | Description |
| Webhook of the |
| Webhook of another space. |
| Space to use when none is named. Defaults to |
| How long to wait for Google Chat. Default |
|
|
At least one webhook is required.
Usage
Ask your assistant to post something, for example "tell the alerts space that the deploy is done".
Tool | What it does |
| Sends a message to a space, optionally as a reply in a thread |
| Sends a card with a title, text, labelled details and link buttons |
| Shows how a message will look, without sending it |
The assistant writes in Markdown and the server converts it to Google Chat formatting. The server also gives the assistant a short writing guide so messages read like a teammate wrote them.
Development
npm install
npm test
npm run build
cp env/.env.local .env # then fill in a webhook
node --env-file=.env build/index.jsLicense
MIT
Available Tools
3 toolspreviewPreview a messageARead-only
Show exactly how a message will look in Google Chat before sending it with send. Read google-chat://guide for tone and formatting.
Inputs: text (required), format. Returns: text
reportSend a reportA
Send a structured report to a Google Chat space: a title, optional plain text, labelled details and link buttons. Read google-chat://guide first.
Inputs: title (required), text, links, space, +3 more. Returns: name, thread
sendSend a messageA
Send a text message to a Google Chat space, optionally as a reply in a thread. Read google-chat://guide first.
Inputs: text (required), space, format, threadKey. Returns: name, thread
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
send and report both deliver content to a space, but report is clearly specialized for structured output and preview is explicitly non-sending. An agent can distinguish them, though send/report selection may require knowing whether structured report format is desired.
All three tools use short, consistent imperative-style verb names: send, report, preview. There is no mixing of casing or naming conventions.
Three tools are well-scoped for a focused outbound-messaging server: one general send, one structured report, and one preview aid. Each has a clear role and the set does not feel bloated.
The surface covers sending and previewing messages but lacks obvious Google Chat operations such as listing spaces, reading messages, or updating/deleting sent messages. These gaps may force agents to rely on external context to identify spaces and verify results.
Maintenance
Related MCP Connectors
Hosted MCP messaging across owners, tools, and machines, with readable transcripts.
Build your own tools from chat: design, test and host them on a shareable MCP server URL.
Let Claude or ChatGPT search, read and send your WhatsApp messages over MCP. OAuth sign-in.
Appreciate teammates, celebrate milestones, and run workspace ops from MCP clients via OAuth.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables posting text messages to Google Chat spaces through webhook-based integration, providing simple and secure message delivery without OAuth setup requirements.MIT
- AlicenseNot gradedqualityDmaintenanceEnables posting text messages to Google Chat spaces using webhooks, providing simple integration without OAuth setup required.1MIT
- AlicenseAqualityDmaintenanceSends messages to Google Chat via webhooks with automatic Markdown to Cards V2 conversion, supporting headers, lists, code blocks, tables, and images with validation and fallback handling.319 npm1MIT
- AlicenseAqualityAmaintenanceEnables interaction with Google Chat via MCP using the internal Dynamite API, allowing listing spaces, reading and sending messages, and managing DMs. No Google Cloud Console setup required.13MIT