Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GCHAT_COOKIESNoPath to the saved cookies file. Default: $GCHAT_CONFIG_DIR/cookies.json$GCHAT_CONFIG_DIR/cookies.json
GCHAT_PROFILENoPath to the browser profile used for sign-in. Default: $GCHAT_CONFIG_DIR/browser-profile$GCHAT_CONFIG_DIR/browser-profile
GCHAT_MCP_WRITENoSet to 1 to turn on the MCP server's write tools (send, reply, react, edit or delete your own messages). Off by default.off
GCHAT_CONFIG_DIRNoConfiguration directory for googlechat-mcp. Default: ~/.config/googlechat-mcp~/.config/googlechat-mcp

Instructions

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

Read-only: tools that post or change anything are off. The user can turn them on by setting GCHAT_MCP_WRITE=1 for this server.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_spacesC

List spaces, group chats and DMs, most recently active first.

list_unreadA

List the page_size most recently active chats with messages you haven't read.

A chat counts as unread when it has messages newer than your last_read_time or new replies in a thread you follow. Google gives no count of unread messages. Use read_messages and compare create_time with last_read_time to see what is new. Reading here does not mark anything read.

list_sectionsA

List your sidebar sections in sidebar order, each with its chats.

name (any case) or a section id limits it to that section.

read_messagesA

Read the latest threads of a space or DM: each thread's first message plus its newest replies replies, with Drive files, attachments and links.

space_id and is_dm come from list_spaces; in every tool, is_dm may be left out and is then looked up. page_size is the number of threads. Use read_thread for every message of one thread.

read_threadB

Read every message of one thread (or only its newest limit), oldest first.

search_messagesA

Search messages server-side across all chats, like Chat's search box.

space_id (+ is_dm) limits it to one chat. since/until are ISO dates or datetimes (e.g. "2026-11-01"; no timezone means UTC). order: "newest" or "relevance". Each hit includes its space_id and thread_id.

list_space_filesC

List files, Drive items and links shared in the latest page_size threads.

list_membersB

List members of a space or DM.

get_user_statusA

Do-not-disturb state and custom status of users (ids from list_members).

Users Google returns no status for (e.g. bots) are listed under no_status.

sign_inA

Sign in to Google Chat or refresh an expired session. Tries a silent refresh from the saved browser profile first; if that fails, opens a Chrome window for the user to sign in (waits up to 10 minutes). Call this when other tools report the user is not signed in or the session expired.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 10 tools

Disambiguation4/5

Most tools target a distinct query shape: list_spaces (all spaces), list_unread (unread filter), list_sections (sidebar grouping), and search_messages (server-side search) are separable by their descriptions. The main overlap is read_messages vs read_thread and list_spaces vs list_sections, but the docs explicitly clarify thread-level vs message-level reading and section-grouped vs flat listing.

Naming Consistency4/5

Nearly all names follow a verb_noun pattern (list_spaces, read_messages, search_messages, list_space_files, list_members, get_user_status). Minor deviations: list_unread omits the noun, and sign_in uses a verb+particle rather than verb_noun, but the set is still highly predictable.

Tool Count5/5

10 tools is well-scoped for a chat client, covering listing, reading, searching, file/member lookup, and auth. Each tool earns its place and there is no filler.

Completeness2/5

The surface is entirely read-only: there is no send_message, reply, create space, or mark-as-read operation, which are core lifecycle actions for a Google Chat client. An agent asked to actually participate in chat will hit a dead end despite rich reading coverage.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues