Google Chat Webhook MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_DIR | No | Log directory path (absolute or relative) | ./logs |
| LOG_LEVEL | No | Log level (DEBUG, INFO, WARN, ERROR) | INFO |
| LOG_ENABLE_CONSOLE | No | Enable console output (true or false) | true |
| LOG_RETENTION_DAYS | No | Days to keep logs (number in days) | 30 |
| GOOGLE_CHAT_WEBHOOK_URL | Yes | Google Chat Webhook URL (required by NCBI) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_google_chat_textB | Send a text message to configured Google Chat webhook |
| send_google_chat_cards_v2C | Send a Cards V2 message to configured Google Chat webhook |
| send_google_chat_markdownA | Convert Markdown to Cards V2 and send to configured Google Chat webhook. Falls back to text on failure. |
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 3 tools
Each tool has a clearly distinct purpose: send_google_chat_cards_v2 sends Cards V2 messages, send_google_chat_markdown converts Markdown to Cards V2 with fallback, and send_google_chat_text sends plain text messages. There is no ambiguity in their functions, as they target different message formats and conversion behaviors.
All tool names follow a consistent verb_noun pattern with 'send_google_chat_' as a prefix and specific suffixes (_cards_v2, _markdown, _text). This predictable naming scheme makes it easy to understand their roles and ensures no mixing of conventions.
With 3 tools, the count is appropriate for the server's purpose of sending messages to Google Chat webhooks, covering key message types. It is slightly lean but reasonable, as it includes essential formats (Cards V2, Markdown, text) without unnecessary bloat.
The tool set provides complete coverage for sending messages via Google Chat webhooks, including Cards V2, Markdown conversion with fallback, and plain text. There are no obvious gaps, as these tools cover the primary message formats and conversion needs for this domain.