Skip to main content
Glama
ice3x2

Google Chat Webhook MCP Server

by ice3x2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Google Chat Webhook MCP Server

No user-submitted related servers found.

    Related Servers

    • notify_me_mcp

      thesammykins
      A
      license
      B
      quality
      D
      maintenance
      Enables sending rich notifications to Discord and/or Slack webhooks with automatic service detection, retry logic, and support for embeds, blocks, and attachments. Provides secure webhook management with comprehensive input validation and rate limiting.
      3
      TypeScript
      MIT

    • feishu-bot-mcp

      leonleonlei
      A
      license
      A
      quality
      C
      maintenance
      Enables sending messages to Feishu group chats via custom bot webhook, supporting text, rich text, interactive cards, Markdown-converted cards, and chat sharing without requiring an enterprise app.
      6
      MIT

    • Discord Webhook MCP

      LLMTooling
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to send messages and rich embeds to Discord via webhooks, supporting plain text messages, formatted embeds with images and fields, and customizable webhook appearance for AI-powered Discord notifications and integrations.
      6 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources