Google Chat MCP Interface Engine

A Model Context Protocol (MCP) server implementation engineered for interfacing with the Google Chat service endpoints via pre-configured webhooks. This service furnishes a streamlined utility for dispatching textual content to designated Google Chat enclosures.

Key Capabilities

• Transmit textual payloads to Google Chat spaces leveraging webhooks.
• Offers straightforward and robust webhook-based connection protocols.
• Eliminates the prerequisite for OAuth configuration.
• Seamlessly interoperable with other MCP-conforming systems.

Deployment Methods

Automated Installation via Smithery

To onboard the gchat-mcp package automatically for Claude Desktop environments utilizing Smithery:

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

Recommended Installation via Smithery CLI

Provision the server using Smithery's command-line interface:

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

On-Premises Development Setup

1. Clone the source code repository: bash git clone https://github.com/KaranThink41/google_chat_mcp_server.git cd google_chat_mcp_server

2. Resolve project dependencies: bash npm install

3. Compile the source artifacts: bash npm run build

4. Execute the running process: bash node build/index.js

Containerized Execution (Docker)

You may operate this service within a Docker container. Setup procedure:

1. Construct the Docker image: bash docker build -t google-chat-mcp-server .

2. Launch the container instance, ensuring necessary environmental parameters are supplied: 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 dispatch a communication to Google Chat, submit the subsequent JSON structure for invocation:

{ "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!" } } }

Required Configuration Parameters

The server necessitates the declaration of the following environmental variables for operational success:

• GOOGLE_CHAT_SPACE_ID: The unique identifier for the target Google Chat venue.
• GOOGLE_CHAT_API_KEY: The requisite API key credential from your Google Cloud project.
• GOOGLE_CHAT_TOKEN: The authentication token required for the Google Chat interaction.

These parameters can be established within your runtime environment or specified during Docker execution (as detailed above).

For local execution without containerization, instantiate a .env file containing:

GOOGLE_CHAT_SPACE_ID=your_space_id GOOGLE_CHAT_API_KEY=your_api_key GOOGLE_CHAT_TOKEN=your_token

Security Posture

• Webhook endpoints are relayed strictly within the request payload.
• Sensitive access credentials are not persisted within the application source code.
• All incoming interaction requests undergo rigorous validation prior to execution.

Collaboration Guide

1. Establish a fork of the repository.
2. Branch out for new features (git checkout -b feature/amazing-feature).
3. Commit alterations (git commit -m 'Add some amazing feature').
4. Push the changes to your branch (git push origin feature/amazing-feature).
5. Initiate a Pull Request.

Licensing

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