Google Chat MCP Service Adapter

A Model Context Protocol (MCP) compliant service adapter engineered for interfacing with the Google Chat API through outbound webhook conduits. This component is specialized in dispatching plain text announcements into specified Chat rooms.

Core Capabilities

• Transmit unformatted textual content to Google Chat rooms utilizing webhooks.
• Streamlined, secure integration pathway based entirely on webhooks.
• Eliminates the prerequisite for explicit OAuth credential configuration.
• Optimized for seamless operation within MCP-aware environments.

Deployment Procedures

Utilizing Smithery (Preferred Method)

Invoke Smithery's command-line interface for server installation:

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

On-Premises Development Setup

1. Obtain the source code repository:

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

1. Fetch necessary package dependencies:

npm install

1. Compile the application assets:

npm run build

1. Initiate the service runtime:

node build/index.js

Containerized Execution (Docker)

Execution via Docker containers can be managed as follows:

1. Construct the Docker image:

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

1. Launch the container instance, supplying required configuration parameters:

docker run -e GOOGLE_CHAT_SPACE_ID=your_space_identifier 
          -e GOOGLE_CHAT_API_KEY=your_access_key 
          -e GOOGLE_CHAT_TOKEN=your_session_key 
          google-chat-mcp-server

Execution Exemplar

To dispatch a message to a Google Chat destination, structure your invocation request as follows:

{
  "method": "tools/call",
  "params": {
    "name": "post_text_message",
    "arguments": {
      "space_id": "your_space_identifier",
      "key": "your_access_key",
      "token": "your_session_key",
      "text": "Greetings! This is a transmitted communication test!"
    }
  }
}

Necessary Configuration Parameters

The server necessitates the following environment variables for operational continuity:

• GOOGLE_CHAT_SPACE_ID: Identifies the target Google Chat communication area.
• GOOGLE_CHAT_API_KEY: The credential key sourced from the Google Cloud project.
• GOOGLE_CHAT_TOKEN: The essential authorization credential for the Chat service.

If not utilizing Docker, establish a .env file containing:

GOOGLE_CHAT_SPACE_ID=your_space_identifier
GOOGLE_CHAT_API_KEY=your_access_key
GOOGLE_CHAT_TOKEN=your_session_key

Security Posture

• Webhook endpoints are received directly within the transmission payload.
• No sensitive access credentials are persistently retained within the application source code.
• Comprehensive input validation precedes all outbound service interactions.

Collaboration Guidelines

1. Fork the primary repository structure.
2. Establish a dedicated feature branch (e.g., git checkout -b feature/enhanced-functionality).
3. Commit modifications (git commit -m 'Implement feature enhancement X').
4. Submit changes to the remote branch (git push origin feature/enhanced-functionality).
5. Initiate a formal Pull Request.

Project Licensing

This software is governed under the terms of the MIT License; refer to the [LICENSE] file for comprehensive particulars.