Problem Statement
What's Missing
Claude's Google Workspace connectors currently support Gmail, Calendar, and Drive — but not Google Chat. For organizations that use Google Chat as their primary messaging platform, this is a significant gap. There's no native connector in the directory, no workaround within Claude, and the only path today is building and self-hosting a custom remote MCP server, which is a heavy lift for non-developer teams.
Why It Matters
Google Chat is a core component of Google Workspace and is widely used by small and mid-size teams for day-to-day coordination, decision-making, and project communication. The same way Claude can currently search Gmail threads or Calendar events to build context, being able to search and reference Google Chat conversations would make Claude a far more effective teammate — especially for operations-heavy organizations that live in Chat, not Slack.
Proposed Solution
A Google Chat connector with at minimum:
List accessible Google Chat spaces
Search messages across spaces by keyword and date range
Read message threads from a specific space
Read-only access would be a strong starting point. Write capabilities (sending messages, creating spaces) would be a welcome addition later.
Alternatives Considered
Current Alternatives
There are open-source Google Chat MCP servers on GitHub (e.g., chy168/google-chat-mcp-server), but they run as local servers and require self-hosting, Google Cloud OAuth configuration, and Python 3.13+ — not viable for most teams using Claude for non-technical workflows.
Area
MCP Connector (adding/managing servers)
Priority
High - Major improvement needed
Additional Context
Environment
Claude Team plan
Google Workspace (Google Chat as primary messaging)
Existing connectors in use: Gmail, Google Calendar, Google Drive
Problem Statement
What's Missing
Claude's Google Workspace connectors currently support Gmail, Calendar, and Drive — but not Google Chat. For organizations that use Google Chat as their primary messaging platform, this is a significant gap. There's no native connector in the directory, no workaround within Claude, and the only path today is building and self-hosting a custom remote MCP server, which is a heavy lift for non-developer teams.
Why It Matters
Google Chat is a core component of Google Workspace and is widely used by small and mid-size teams for day-to-day coordination, decision-making, and project communication. The same way Claude can currently search Gmail threads or Calendar events to build context, being able to search and reference Google Chat conversations would make Claude a far more effective teammate — especially for operations-heavy organizations that live in Chat, not Slack.
Proposed Solution
A Google Chat connector with at minimum:
List accessible Google Chat spaces
Search messages across spaces by keyword and date range
Read message threads from a specific space
Read-only access would be a strong starting point. Write capabilities (sending messages, creating spaces) would be a welcome addition later.
Alternatives Considered
Current Alternatives
There are open-source Google Chat MCP servers on GitHub (e.g., chy168/google-chat-mcp-server), but they run as local servers and require self-hosting, Google Cloud OAuth configuration, and Python 3.13+ — not viable for most teams using Claude for non-technical workflows.
Area
MCP Connector (adding/managing servers)
Priority
High - Major improvement needed
Additional Context
Environment
Claude Team plan
Google Workspace (Google Chat as primary messaging)
Existing connectors in use: Gmail, Google Calendar, Google Drive