Skip to content
Back to search

google-chat-mcp

MCP server that sends messages to Google Chat spaces through incoming webhooks

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked yesterday
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/hungvudang--google-chat-mcp/badge.svg)](/listings/hungvudang--google-chat-mcp)

HTML

<a href="/listings/hungvudang--google-chat-mcp"><img src="/api/listings/hungvudang--google-chat-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

1. 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.

2. 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 to `env`, for example `GOOGLE_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

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 73 lines
  1. # google-chat-mcp
  2. Post to Google Chat from any MCP client through incoming webhooks.
  3. Requires Node.js 22.18 or later.
  4. ## Setup
  5. 1. 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.
  6. 2. Add the server to your MCP client's config:
  7. ```json
  8. {
  9. "mcpServers": {
  10. "google-chat": {
  11. "command": "npx",
  12. "args": ["-y", "@hungvudang/google-chat-mcp"],
  13. "env": {
  14. "GOOGLE_CHAT_WEBHOOK": "https://chat.googleapis.com/v1/spaces/..."
  15. }
  16. }
  17. }
  18. }
  19. ```
  20. To post to several spaces, add one `GOOGLE_CHAT_WEBHOOK_<NAME>` per space to `env`, for example `GOOGLE_CHAT_WEBHOOK_ALERTS`.
  21. Some clients add servers from the command line instead. With Claude Code, for example:
  22. ```bash
  23. claude mcp add google-chat \
  24. -e GOOGLE_CHAT_WEBHOOK=https://chat.googleapis.com/v1/spaces/... \
  25. -- npx -y @hungvudang/google-chat-mcp
  26. ```
  27. ## Configuration
  28. | Variable | Description |
  29. |---|---|
  30. | `GOOGLE_CHAT_WEBHOOK` | Webhook of the `default` space |
  31. | `GOOGLE_CHAT_WEBHOOK_<NAME>` | Webhook of another space. `GOOGLE_CHAT_WEBHOOK_DEV_TEAM` adds a space called `dev-team` |
  32. | `GOOGLE_CHAT_DEFAULT_SPACE` | Space to use when none is named. Defaults to `default`, or to the only space if there is just one |
  33. | `GOOGLE_CHAT_TIMEOUT_MS` | How long to wait for Google Chat. Default `10000` |
  34. | `LOG_LEVEL` | `trace`, `debug`, `info`, `warn`, `error` or `fatal`. Default `info` |
  35. At least one webhook is required.
  36. ## Usage
  37. Ask your assistant to post something, for example *"tell the alerts space that the deploy is done"*.
  38. | Tool | What it does |
  39. |---|---|
  40. | `send` | Sends a message to a space, optionally as a reply in a thread |
  41. | `report` | Sends a card with a title, text, labelled details and link buttons |
  42. | `preview` | Shows how a message will look, without sending it |
  43. 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.
  44. ## Development
  45. ```bash
  46. npm install
  47. npm test
  48. npm run build
  49. cp env/.env.local .env # then fill in a webhook
  50. node --env-file=.env build/index.js
  51. ```
  52. ## License
  53. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.