Skip to main content
Glama
Google Chat MCP Server

Google Chat MCP Server

by hungvudang

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LOG_LEVELNoLog level: `trace`, `debug`, `info`, `warn`, `error` or `fatal`. Default `info`.info
GOOGLE_CHAT_WEBHOOKNoWebhook URL of the `default` space. Anyone with this URL can post to the space, so keep it private.
GOOGLE_CHAT_TIMEOUT_MSNoHow long to wait for Google Chat, in milliseconds. Default `10000`.10000
GOOGLE_CHAT_DEFAULT_SPACENoSpace to use when none is named. Defaults to `default`, or to the only space if there is just one.
GOOGLE_CHAT_WEBHOOK_<NAME>NoWebhook URL of another space. For example, `GOOGLE_CHAT_WEBHOOK_DEV_TEAM` adds a space called `dev-team`. Add one per additional space.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Posts to these Google Chat spaces: default. Use send for a conversational message and report for a structured update with details. Read google-chat://guide before posting. It explains how to write for the people in the space.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
sendA

Send a text message to a Google Chat space, optionally as a reply in a thread. Read google-chat://guide first.

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.

previewA

Show exactly how a message will look in Google Chat before sending it with send. Read google-chat://guide for tone and formatting.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
guide

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation4/5

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.

Naming Consistency5/5

All three tools use short, consistent imperative-style verb names: send, report, preview. There is no mixing of casing or naming conventions.

Tool Count5/5

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.

Completeness3/5

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

ActivityMaintained
ResponsivenessNo recent community issues