A1 Google Chat MCP
Related Servers
Alternatives to A1 Google Chat MCP
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityDmaintenanceEnables AI assistants to read and send messages in Google Chat spaces using service account authentication.-
- AlicenseNot gradedqualityCmaintenanceEnables reading and searching Google Chat spaces, messages, threads, and members, with optional message sending.127 npmMIT
- FlicenseAqualityCmaintenanceEnables LLM clients to send messages to Google Chat spaces, list spaces, and search message history.4-
- AlicenseNot gradedqualityAmaintenanceEnables reading, searching, and writing to Google Chat spaces, direct messages, and sidebar through MCP clients such as Claude Code and Claude Desktop.Apache 2.0
- AlicenseNot gradedqualityFmaintenanceConnects Claude to Google Chat for searching messages, spaces, and DMs, automatically resolving user IDs to real display names.MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to create and modify Google Apps Script projects, manage versions and deployments, run functions, and inspect execution history through natural language.1333 npmMIT
TDQS
Scored across 14 tools
Each tool maps to a distinct Google Chat resource and action: spaces discovery/reading/search, DM lookup, message CRUD, reactions, members, attachments, and a raw escape hatch. Even the space-finding tools are clearly separated by membership scope versus admin-wide search, so an agent can reliably choose the right one.
All tool names use a consistent snake_case verb_noun pattern: list_* for collections, get_* for singletons, send/update/delete for message lifecycle, and manage_* for sub-resources. raw_request is the only deviation, but it is an intentional, clearly named escape hatch rather than a naming inconsistency.
14 tools is well within the well-scoped range and each one earns its place by covering a distinct part of the Chat API. The count feels proportionate to the domain: spaces, messages, members, reactions, attachments, and an escape hatch for advanced operations.
The typed surface covers the core workflows: list/read spaces, send/edit/delete messages, manage members and reactions, and inspect attachments. Minor gaps remain around attachment upload/download and some space/admin operations, which are either left to raw_request or explicitly outside the server's scope.