Google Chat MCP
English | Русский
Усильте агента
Собственная команда издателя. Не эндпоинт PlugMCP.
Host a copy with our keys and logs.
npx -y [email protected]У Claude Code нет ссылки для установки локальной команды. Скопируйте команду ниже и выполните её в терминале.
GOOGLE_CHAT_CLIENT_ID=<value> GOOGLE_CHAT_CLIENT_SECRET=<secret> GOOGLE_CHAT_REFRESH_TOKEN=<secret> GOOGLE_CHAT_ACCESS_TOKEN=<secret> GOOGLE_CHAT_OAUTH_PORT=<value> GOOGLE_CHAT_API_BASE=<value> GOOGLE_CHAT_TIMEOUT_MS=<value> GOOGLE_CHAT_MAX_RETRIES=<value> claude mcp add io.github.a1-x-tech-mcp-google-chat -- npx -y mcp-google-chat@1.1.2Выполните в терминале.
{ "mcpServers": { "io.github.a1-x-tech-mcp-google-chat": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "GOOGLE_CHAT_CLIENT_ID": "<value>", "GOOGLE_CHAT_CLIENT_SECRET": "<secret>", "GOOGLE_CHAT_REFRESH_TOKEN": "<secret>", "GOOGLE_CHAT_ACCESS_TOKEN": "<secret>", "GOOGLE_CHAT_OAUTH_PORT": "<value>", "GOOGLE_CHAT_API_BASE": "<value>", "GOOGLE_CHAT_TIMEOUT_MS": "<value>", "GOOGLE_CHAT_MAX_RETRIES": "<value>" } } }}claude_desktop_config.json
Удалённый URL или команда на вашем компьютере? Чем различаются два способа установки
Запустить на PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
ЗапускОт издателя
English | Русский
MCP server for the Google Chat API: spaces, messages, threads, reactions and memberships.
A1 Google Chat MCP lets an AI app work in Google Chat in plain language. Find the right space or direct message, catch up on a conversation, reply in a thread, react with an emoji and manage who is in a space.
It uses the Google Chat API with your Google account and acts as the signed-in user: messages send under your name, and only your own messages and reactions can be edited or deleted. It makes the limits of the Chat API explicit instead of implying that every chat task is possible.
127.0.0.1 with PKCE and keeps the tokens itself — no config files, no restart.Start with a read-only question:
Show today’s messages in the team space and summarize what was decided.
You: What was discussed in the release space today?
Assistant: Lists today’s messages with senders and threads. Nothing changes.
You: Reply in the deploy thread that the rollout is finished.
Assistant: Shows the target space, the thread and the drafted text, then asks for confirmation before sending.
You: Confirm.
Assistant: Sends the reply under your name in that thread. It does not touch any other message.
You need Node.js 20+ and a Google account with access to Google Chat. Credentials are not required at install time — the server connects from the conversation.
In the app: open Settings → MCP servers, select Add server, choose STDIO, enter the command npx -y mcp-google-chat@latest, then select Save. No environment variables are needed — connect from the chat afterwards.
From the command line:
codex mcp add google-chat \
-- npx -y mcp-google-chat@latest
codex mcp list
claude mcp add \
--transport stdio --scope user google-chat \
-- npx -y mcp-google-chat@latest
claude mcp list
The current official path is Settings → Extensions. For a custom desktop extension, open Advanced settings → Extension Developer → Install Extension…, select a .mcpb file and follow the prompts.
This repository currently publishes an npm stdio package and does not contain a .mcpb bundle. For Claude Desktop builds that still support local configuration, use the following JSON stdio configuration as a fallback:
{
"mcpServers": {
"google-chat": {
"command": "npx",
"args": ["-y", "mcp-google-chat@latest"]
}
}
}
In those builds, save it to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows.
Add this to ~/.cursor/mcp.json on macOS/Linux or %USERPROFILE%\.cursor\mcp.json on Windows:
{
"mcpServers": {
"google-chat": {
"type": "stdio",
"command": "npx",
"args": ["-y", "mcp-google-chat@latest"]
}
}
}
Run MCP: Open User Configuration and add:
{
"servers": {
"google-chat": {
"type": "stdio",
"command": "npx",
"args": ["-y", "mcp-google-chat@latest"]
}
}
}
Check it with MCP: List Servers.
GOOGLE_CHAT_ACCESS_TOKEN.The Chat API cannot search message text — the only message filters are creation time and thread. find_direct_message finds an existing DM but never creates one, and file bytes are not downloaded or uploaded through this server. Space creation and the other uncovered API methods go through raw_request.
The AI client controls confirmation prompts. The server marks reads, writes and destructive tools so the client can distinguish catching up from posting.
Google Chat requires OAuth 2.0; an API key is not enough. There are two ways in, and the first one needs no configuration files.
Say "connect Google Chat" and the assistant runs the flow with you:
setup_instructions prints the checklist: create or select a Google Cloud project, enable the Google Chat API, configure the consent screen and create a Desktop app OAuth client.set_client stores it owner-only. The secret never goes through the conversation.start_login returns a Google consent link. Open it on this machine and approve; the code comes back to a one-shot listener on 127.0.0.1 (PKCE), never through the chat.finish_login exchanges the code, saves the tokens to ~/.config/mcp-google-chat/credentials.json (mode 0600) and verifies them with a real Chat API call — so a Chat API that is still switched off is caught right there, not on your first real question.The tokens are re-read on every call, so the connection works immediately — no restart of the AI app. auth_status shows what is connected, logout revokes and deletes it. The login asks for chat.spaces.readonly, chat.messages, chat.messages.reactions and chat.memberships.readonly; the admin scope behind search_spaces is not requested — use the environment path if you need it.
Create or select a Google Cloud project and enable Google Chat API.
Configure the OAuth consent screen and create a Desktop app OAuth client.
Authorize the Google account you chat as. The OAuth 2.0 Playground can obtain the refresh token when Use your own OAuth credentials is enabled.
Request only the scopes your sessions need. For reading and sending, this is enough:
https://www.googleapis.com/auth/chat.spaces.readonly
https://www.googleapis.com/auth/chat.messages.readonly
https://www.googleapis.com/auth/chat.messages.create
The full per-task table — editing and deleting your own messages, reactions, memberships, admin search — is in docs/TOOLS.md.
Testing-mode OAuth refresh tokens can expire after seven days. Publish the OAuth app, or use an Internal app in a Workspace domain, when you need long-lived access. Treat the client secret and refresh token as passwords.
For a quick session, a short-lived token in GOOGLE_CHAT_ACCESS_TOKEN also works — for example from gcloud auth print-access-token with Chat scopes granted. The same variable is how a service-account Chat-app token reaches the server when you need app-only features.
Every variable is optional — with none of them the server connects from the chat.
* For the environment path, provide either the OAuth trio or an access token. When set, they win over a stored in-chat login and the server never refreshes or deletes them.
Started without any credentials, the server still completes the MCP handshake; the instructions and the first tool call then name both fixes — the in-chat login (no restart) and the environment variables (restart).
ASKADS_TELEMETRY=0 to opt out.429, the server uses backoff; reads also retry after network and 5xx errors, while writes are never replayed after an uncertain failure — a replayed send would be a duplicate message in a real room. send_message accepts a custom message id that makes a send addressable and deduplicable.list_messages can poll a space incrementally by creation time if your AI app supports scheduled tasks; space event subscriptions go through raw_request.Found a bug or need a scenario? Create an issue or write in Telegram.
MCP server for the Google Chat API: spaces, messages, threads, reactions and memberships.
{ "mcpServers": { "io.github.a1-x-tech-mcp-google-chat": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "GOOGLE_CHAT_CLIENT_ID": "<value>", "GOOGLE_CHAT_CLIENT_SECRET": "<secret>", "GOOGLE_CHAT_REFRESH_TOKEN": "<secret>", "GOOGLE_CHAT_ACCESS_TOKEN": "<secret>", "GOOGLE_CHAT_OAUTH_PORT": "<value>", "GOOGLE_CHAT_API_BASE": "<value>", "GOOGLE_CHAT_TIMEOUT_MS": "<value>", "GOOGLE_CHAT_MAX_RETRIES": "<value>" } } }}Инструменты
Списка инструментов пока нет. У удалённых серверов он появляется после первой проверки состояния.
FAQ
Скопируйте на этой странице конфигурацию stdio для Cursor, Claude Desktop, Claude Code или VS Code. Она использует установку издателя, а не прокси PlugMCP.
Издатель указывает следующие переменные окружения: GOOGLE_CHAT_CLIENT_ID, GOOGLE_CHAT_CLIENT_SECRET, GOOGLE_CHAT_REFRESH_TOKEN, GOOGLE_CHAT_ACCESS_TOKEN, GOOGLE_CHAT_OAUTH_PORT, GOOGLE_CHAT_API_BASE, GOOGLE_CHAT_TIMEOUT_MS, GOOGLE_CHAT_MAX_RETRIES.
Google Chat MCP работает локально через stdio.
Последняя проверка: 2026-11-11. MCP server for the Google Chat API: spaces, messages, threads, reactions and memberships.