google-chat-mcp
Provides tools for interacting with Google Chat, enabling listing spaces, reading and searching messages, retrieving threads and members, and optionally sending messages.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@google-chat-mcpsearch my chats for messages about the project launch"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
google-chat-mcp
MCP server for Google Chat. Lets Claude (Code / Desktop) or any MCP client list your spaces, read and search messages, pull threads and members, and — opt-in — send messages as you.
Read-only by default. Runs locally over stdio. Refresh token stored 0600 under ~/.google-chat-mcp/.
Tools
Tool | Input | Notes |
|
| Sorted by last activity. DMs have no name unless |
|
| Newest first. |
|
| Client-side scan; Chat API has no full-text search. Default window 14 days, ≤500 msgs/space. |
|
| All replies, oldest first. |
|
| Users + roles, names/emails via People API. |
|
| Only registered when |
Sender names come from the People API directory (directory.readonly). If that API is disabled or the user is external, you get users/<id> instead — everything else still works.
Related MCP server: google-mcp
Setup
Requires a Google Workspace account. Consumer @gmail.com accounts cannot call the Chat API (403).
1. Google Cloud project (one-time, ~10 min)
console.cloud.google.com → create/select a project.
APIs & Services → Library → enable Google Chat API and People API.
Google Chat API → Configuration tab → fill in App name, Avatar URL, Description; interactive features off; visibility to your domain. Save.
Gotcha: the Chat API rejects all OAuth calls with
403until this form is saved, even for read-only user auth.OAuth consent screen → Internal → add scopes:
https://www.googleapis.com/auth/chat.spaces.readonlyhttps://www.googleapis.com/auth/chat.messages.readonlyhttps://www.googleapis.com/auth/chat.memberships.readonlyhttps://www.googleapis.com/auth/directory.readonlyhttps://www.googleapis.com/auth/chat.messages.create(only if you wantsend_message)
Credentials → Create credentials → OAuth client ID → Desktop app → download JSON. Keep it out of any repo.
2. Login
export GOOGLE_CHAT_CLIENT_SECRET_PATH=/path/to/client_secret.json
npx google-chat-mcp login # browser opens → sign in with your Workspace account
npx google-chat-mcp whoami # sanity check3. Register with Claude Code
claude mcp add google-chat \
-e GOOGLE_CHAT_CLIENT_SECRET_PATH=/path/to/client_secret.json \
-- npx -y google-chat-mcpClaude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"google-chat": {
"command": "npx",
"args": ["-y", "google-chat-mcp"],
"env": { "GOOGLE_CHAT_CLIENT_SECRET_PATH": "/path/to/client_secret.json" }
}
}
}Environment
Var | Default | Purpose |
| — | Desktop OAuth client JSON. On macOS falls back to Keychain item |
|
| Refresh token cache. |
|
|
|
Quota notes
Chat API: ~60 requests/min/user. Spaces and member lists are cached 5 min in-process; resolved user names are cached on disk in ~/.google-chat-mcp/users.json. search_messages is the expensive one — scope it with spaces and since.
Development
pnpm install
pnpm dev login
pnpm typecheck && pnpm lint && pnpm buildNode ≥ 22. TypeScript strict, ESM, tsup build.
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Read email/chat conversations, messages, contacts and teams; draft, send and update threads.
Permissioned access to Gmail, Drive and Calendar via the user's own Google account
- UproarOAuthchat.uproar
Chat where AI agents are first-class members, with their own identity and permissions.
Read spaces, collections, pages and content; search docs and manage GitBook organization spaces.
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceConnects Claude to Google Chat for searching messages, spaces, and DMs, automatically resolving user IDs to real display names.MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Google Chat through MCP, allowing listing spaces and messages, searching messages, and sending messages. Supports local and remote transports.35 npmApache 2.0
- -licenseNot gradedqualityCmaintenanceEnables AI assistants to read and send messages in Google Chat spaces using service account authentication.-
- AlicenseAqualityBmaintenanceEnables AI assistants to work in Google Chat through natural language: find spaces and direct messages, read and send messages, manage threads, reactions, attachments, and memberships while acting as the signed-in user.1445 npmMIT