Google Chat Notification Bridge Service

An implementation of the Model Context Protocol (MCP) intermediary designed to interface with the Google Chat API solely via preconfigured webhooks. This utility furnishes a streamlined apparatus for dispatching plain text memoranda into designated Google Chat team spaces.

Core Capabilities

• Transmission of textual content to specified Google Chat team areas via HTTP webhooks.
• Robust and simplified integration relying entirely on webhook mechanisms.
• Elimination of any requirement for OAuth credential management or setup.
• Optimal compatibility and straightforward invocation from MCP-aware platforms.

Deployment Instructions

Acquisition via Smithery Platform

To provision gchat-mcp automatically for use with Claude Desktop through Smithery:

npx -y @smithery/cli install @rishipradeep-think41/gchat-mcp --client claude

Recommended Installation Path (Using Smithery)

Install the service instance using Smithery's command-line utility:

npx spinai-mcp install @KaranThink41/gchat_post_text_message --provider smithery

Setting Up Locally

1. Obtain the source code repository:

git clone https://github.com/KaranThink41/google_chat_mcp_server.git
cd google_chat_mcp_server

1. Install necessary software packages:

npm install

1. Compile the project assets:

npm run build

1. Initiate the server instance:

node build/index.js

Containerization with Docker

Execution of the service using a Docker container is also supported. Setup steps:

1. Generate the Docker image:

docker build -t google-chat-mcp-server .

1. Launch the container, injecting required configuration values as environment variables:

docker run -e GOOGLE_CHAT_SPACE_ID=your_space_id \ 
          -e GOOGLE_CHAT_API_KEY=your_api_key \ 
          -e GOOGLE_CHAT_TOKEN=your_token \ 
          google-chat-mcp-server

Operational Example

To dispatch a communication to a Google Chat location, structure your transmission as the following JSON structure:

{
  "method": "tools/call",
  "params": {
    "name": "post_text_message",
    "arguments": {
      "space_id": "your_space_id",
      "key": "your_api_key",
      "token": "your_token",
      "text": "Greetings! This is a trial transmission!"
    }
  }
}

Required Environment Variables

The service mandates the declaration of these environmental parameters for correct operation:

• GOOGLE_CHAT_SPACE_ID: Identifier for the destination Google Chat room.
• GOOGLE_CHAT_API_KEY: The requisite key from your Google Cloud project console.
• GOOGLE_CHAT_TOKEN: The security token authorizing interaction with the Chat service.

These settings can be established in your operating environment or passed during Docker execution (as illustrated above). For local execution without Docker, populate a .env file with:

GOOGLE_CHAT_SPACE_ID=your_space_id
GOOGLE_CHAT_API_KEY=your_api_key
GOOGLE_CHAT_TOKEN=your_token

Security Posture

• Incoming webhook URLs are processed directly from the incoming request body.
• Sensitive access credentials are not persisted within the application codebase.
• All inbound requests undergo mandatory validation prior to execution.

Collaboration Guidelines

1. Duplicate the official repository (Fork).
2. Establish a dedicated feature branch (git checkout -b feature/enhancement-name).
3. Record modifications (git commit -m 'Feature implementation completed').
4. Commit changes to your remote branch (git push origin feature/enhancement-name).
5. Submit a formal Pull Request.

Licensing Information

This software is distributed under the terms of the MIT License. Consult the LICENSE file for comprehensive particulars.