Log inSubmit server
Google Chat MCP logo

Google Chat MCP

Connects AI clients to Google Chat for reading conversations, posting threaded messages, managing reactions and memberships, and inspecting attachmen…

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Google Chat MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "google-chat-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-chat@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 20 tools correctly (8d ago).

Overview

Google Chat MCP connects AI applications to the Google Chat API through an authenticated MCP interface. It can discover spaces and direct messages, read conversations, send or update messages, manage reactions and memberships, and inspect attachment metadata. OAuth setup starts from the conversation and uses a local PKCE redirect, making it suitable for agents that need to review or act on Google Chat as the signed-in user.

Use cases

  • Summarize decisions from a Google Chat space
  • Reply to a deployment thread
  • Find an existing direct message
  • Review reactions and attachment metadata
  • Manage members in a Chat space

Key features

  • OAuth connection with PKCE and local redirect
  • Space and direct-message discovery
  • Threaded message reading and sending
  • Message, reaction, and membership management
  • Attachment metadata inspection
  • Raw Google Chat API requests

Tools20

What Google Chat MCP lets your agent do. Expand a tool for its parameters.

Verified live~5.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

13/13 checks healthy over the last 66d

What it can do

From the 20 tools this server returned when we ran it; 20 declare their own safety hints.

Can delete or modify data · 6Handles credentials · 8Makes network requests · 20Read-only tools · 14
Network at startup4 connections
Files written at startup1
Install scriptsprepare
npm provenanceNot published
Package age66 days
Maintainers1

Observed 2026-11-04 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · mcp-google-chat@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1kPackage downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed20Callable tools this server registers over MCP.

How Google Chat MCP works

What Google Chat MCP does

Google Chat MCP gives an AI client tools for working with Google Chat spaces, direct messages, messages, threads, reactions, memberships, and attachment metadata. It includes 20 tools for discovering conversations, catching up on messages, posting replies, maintaining messages, checking reactions, and managing who belongs to a space.

The server acts through the Google Chat API using the signed-in Google account. Messages are posted under that user's identity. Editing and deletion are limited to the user's own messages and reactions, while membership changes require the user to be a space manager.

How it works

The server uses OAuth credentials and keeps its tokens itself. A user can start the connection by asking the AI client to connect Google Chat; the flow guides OAuth client setup, receives Google's redirect on 127.0.0.1, and uses PKCE. No configuration file or restart is required for this connection flow.

Google Chat resource names matter when acting on messages, threads, members, reactions, and attachments. A typical workflow is to list spaces or messages first, then use the exact resource name returned by the API. Replies can target a thread name or thread key. Sending normally falls back to a new thread when the target cannot be threaded, with an option to fail instead.

Read operations do not change Chat data. Sending, editing, deleting, reacting, and changing membership do. The server marks read, write, and destructive tools so the client can apply its own confirmation prompts. A failed write is not retried after an ambiguous result, preventing an uncertain send from being replayed as a duplicate.

Setup and configuration

Node.js 20 or newer and a Google account with access to Google Chat are required. The package can be added as an stdio MCP server with:

Terminal
npx -y mcp-google-chat@latest

Codex, Claude Code, Claude Desktop, Cursor, and VS Code each have documented stdio configurations for the package. After adding it to the client, initiate the OAuth flow from the conversation rather than supplying credentials during installation.

The server uses the scopes granted by the OAuth token. Read-only scopes are sufficient for browsing spaces and messages. A separate service-account access token can be supplied through GOOGLE_CHAT_ACCESS_TOKEN when using the Google Chat app configuration path.

Tools and capabilities

  • Discover spaces and existing direct messages.
  • List messages and inspect conversation threads.
  • Send messages with thread control.
  • Update or delete the signed-in user's messages.
  • Add or remove the signed-in user's reactions and inspect other reactions.
  • Read attachment names, types, and related metadata.
  • List members, identify space managers, and add, re-role, or remove members.
  • Make an API call through raw_request for methods without a dedicated tool.

Limitations and notes

Google Chat text search is not available through the Chat API. Message retrieval can be filtered by creation time and thread, but not by message content. Finding a direct message locates an existing conversation and does not create one.

Attachment files are not uploaded or downloaded; the server exposes attachment metadata only. Space creation and other API methods without dedicated tools require raw_request.

The standard flow acts as the signed-in user. Acting as a Google Chat app, including cards, app direct messages, the dedicated attachment endpoint, or forced deletes, requires separate Google Cloud configuration and the service-account token path. Membership operations also depend on manager permissions.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Google Chat MCP

Google Chat MCP is an MCP server that connects AI applications to the Google Chat API. Its tools discover spaces and direct messages, read and send threaded messages, manage reactions and memberships, and inspect attachment metadata. It authenticates with your Google account and performs writes as the signed-in user.

Install it as an stdio server with `npx -y mcp-google-chat@latest`, then add that command to your MCP client. Codex, Claude Code, Claude Desktop, Cursor, and VS Code configurations are supported. Start the OAuth connection from the conversation after installation.

Yes, Google Chat MCP works with Cursor through a stdio entry in `~/.cursor/mcp.json` on macOS or Linux, or the corresponding user path on Windows. Configure the command as `npx` with `-y mcp-google-chat@latest` as its package argument.

No, it cannot search message text through the Chat API. It can retrieve messages using creation-time and thread filters, after which the AI client can review or summarize the returned conversation.

No, it handles attachment metadata rather than file contents. It can show attachment names and types, but file bytes are not uploaded or downloaded through the server.

Related MCP servers

All in Communication All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGoogle Chat MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/google-chat-mcp?style=directory)](https://allmcps.com/mcp/google-chat-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/google-chat-mcp"><img src="https://allmcps.com/api/badge/google-chat-mcp?style=directory" alt="Google Chat MCP on AllMCPs" /></a>