Multi-Chat MCP Server (Google Chat Included)

Created By
siva010928a year ago
Google Chat MCP server that lets AI assistants like Claude and Cursor participate directly in team conversations - search messages, help teammates, share files, and coordinate across chat platforms.
Overview

What is Multi-Chat MCP Server?

Multi-Chat MCP Server is an open-source Python framework that allows AI assistants like Claude and Cursor to participate directly in team conversations across multiple chat platforms, including Google Chat, Slack, and Microsoft Teams.

How to use Multi-Chat MCP Server?

To use the Multi-Chat MCP Server, clone the repository from GitHub, set up Google Cloud API credentials, and run the server with your preferred AI assistant. The server can be configured to connect to multiple chat platforms simultaneously.

Key features of Multi-Chat MCP Server?

  • Seamless integration of AI assistants into team chat environments.
  • Ability to run multiple chat providers simultaneously.
  • Contextual awareness for AI to search team history and assist in real-time.
  • Modular architecture for easy extension to support additional chat platforms.

Use cases of Multi-Chat MCP Server?

  1. AI assistants can share error logs and solutions across chat platforms.
  2. Developers can receive real-time assistance from AI while collaborating in team chats.
  3. AI can summarize team activities and catch up on missed conversations.

FAQ from Multi-Chat MCP Server?

  • Can I use this server with any chat platform?

The server is designed to support multiple platforms, including Google Chat, Slack, and Teams, with the ability to extend support for more.

  • Is it secure to use this server?

Yes, it is designed for local organizational use to maintain data privacy and security compliance.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
siva010928
Star
5
Language
Python
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago