Google Chat MCP Dispatcher Service

A Model Context Protocol (MCP) server implementation designed for transmitting data to Google Chat via established webhook endpoints. This utility offers a streamlined mechanism for broadcasting textual content into designated Google Chat conversation areas.

Core Capabilities

Transmit character-based messages to Google Chat channels utilizing webhooks.
Integration approach emphasizing simplicity and security via webhook communication.
Eliminates the overhead associated with OAuth credential management.
Seamless interoperability with tooling adhering to MCP standards.

Deployment Procedures

Via Smithery (Recommended Pathway)

Install the necessary server package using the Smithery command-line interface:

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

Local Environment Setup

Obtain the source code repository: bash git clone https://github.com/KaranThink41/google_chat_mcp_server.git cd google_chat_mcp_server
Fetch required dependencies: bash npm install
Compile the project artifacts: bash npm run build
Initiate the service instance: bash node build/index.js

Containerization Strategy (Docker)

You may elect to run this service within a Docker container. Setup involves these steps:

Construct the Docker apparatus image: bash docker build -t google-chat-mcp-server .
Execute the container, supplying requisite environmental parameters: bash 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 inject a notification into a Google Chat venue, execute a JSON invocation structured as follows:

{ "method": "tools/call", "params": { "name": "post_text_message", "arguments": { "space_id": "your_space_id", "key": "your_api_key", "token": "your_token", "text": "Hello, this is a test message!" } } }

Configuration Requirements

The service mandates the definition of the following environment variables for correct operation:

GOOGLE_CHAT_SPACE_ID: The unique identifier for the target Google Chat room.
GOOGLE_CHAT_API_KEY: The credential key provisioned from your Google Cloud project.
GOOGLE_CHAT_TOKEN: The authentication token necessary for Chat API interaction.

These settings can be established in your operating environment or supplied during Docker execution (as illustrated above).

For execution outside a containerized environment, populate a .env file with these contents:

GOOGLE_CHAT_SPACE_ID=your_space_id GOOGLE_CHAT_API_KEY=your_api_key GOOGLE_CHAT_TOKEN=your_token

Security Posture

Webhook destination addresses are conveyed strictly within the request payload.
No sensitive access credentials are persisted within the application source code.
All incoming service requests undergo rigorous pre-execution validation checks.

Collaborative Development Guidelines

Initiate a fork of the original repository.
Establish a dedicated feature branch (e.g., git checkout -b feature/enhanced-functionality).
Commit your modifications (git commit -m 'Implement substantial enhancement').
Push the changes to your remote branch (git push origin feature/enhanced-functionality).
Submit a formal Pull Request.