Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Google Chat to Claude Code

Let Claude post messages and reply in threads inside Google Chat. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Google Chat to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Google Chat, you add a Google Chat MCP server: a small hosted service that exposes Google Chat's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Google Chat account. No API keys pasted into config files.

claude mcp add --transport http google-chat https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Google Chat once connected?

Full read-write Google Chat access lets Claude post a message to a space, reply inside the right thread, react, and share a summary back where the discussion is happening. The handoff that used to mean copy-pasting Claude's output into Chat instead lands in the space, on the thread, after you approve it.

  • Post a message to a specific space or direct message
  • Reply inside an existing thread, keeping the conversation together
  • Summarize a long thread and post the recap back to the space
  • Add an emoji reaction to a message
  • Share a status update or notice across the spaces you choose
  • Draft an announcement for a space and send it once you approve

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Google Chat access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Google Chat API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Google Chat changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Google Chat connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Google Chat connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Google Chat account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Google Chat's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Google Chat?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Google Chat account it signs in with. Revoking access is one click in Google Chat.

More on the Google Chat connector

Google Chat connector for claude.aiTelegram + Claude CodeWhatsApp Business + Claude CodeWebex + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us