gchat-claude-channel
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GCHAT_SPACE | Yes | The Google Chat space ID to watch (e.g., spaces/AAAAAAAAAAA) | |
| GCHAT_CLIENT_ID | No | OAuth 2.0 client ID (used with refresh token trio) | |
| GCHAT_STATE_DIR | No | Directory for state files such as heartbeat and inbox (default: current directory) | |
| GCHAT_CLIENT_SECRET | No | OAuth 2.0 client secret (used with refresh token trio) | |
| GCHAT_REFRESH_TOKEN | No | OAuth 2.0 refresh token (used with refresh token trio) | |
| GCHAT_TOKEN_COMMAND | No | Command that prints an access token (e.g., gcloud auth print-access-token). Alternative to OAuth refresh token trio. | |
| GCHAT_ALLOWED_SENDERS | Yes | Comma-separated list of Google user resource names allowed to send messages (e.g., users/1234567890). Must not be empty. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| experimental | {
"claude/channel": {}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| replyA | Send a message back to the Google Chat space. Text over 4000 chars is auto-split. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. All agent actions will use 'reply'.
With a single tool, there is no inconsistency to evaluate. The name 'reply' is clear and appropriate for its function.
A single tool for a chat channel server feels very limited. While it serves a narrow purpose, typical chat interactions often require reading or listing messages, making this count borderline insufficient.
The server covers only outbound replies. There are no tools for reading messages, listing spaces, or managing threads, which are essential for full chat interaction. This leaves significant gaps.