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.54 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
- AlicenseAqualityBmaintenanceEnables Claude Code to browse Google Chat spaces, read and search messages, view participants, and check unread items through read-only API access, without sending, editing, deleting, or marking anything as read.5MIT
- AlicenseNot gradedqualityFmaintenanceConnects Claude to Google Chat for searching messages, spaces, and DMs, automatically resolving user IDs to real display names.MIT
TDQS
Scored across 20 tools
Most tools are cleanly separated by resource and action, and the descriptions actively draw boundaries (e.g. search_spaces is admin-only vs list_spaces membership-only vs find_direct_message for existing DMs). A few near-neighbors remain — get_attachment overlaps with get_message's embedded attachment[] metadata, and list_spaces/search_spaces/find_direct_message all resolve space ids — but each is explained well enough to pick correctly.
Strongly consistent snake_case verb_noun pattern (list_spaces, get_message, send_message, update_message, delete_message, manage_members, raw_request). A handful of deviations exist: auth_status is a noun phrase, logout is a bare verb, and setup_instructions is noun-first, but the overall convention is predictable.
20 tools is on the heavier side but maps to a genuinely broad surface: six auth-lifecycle steps plus spaces, messages, members, reactions, attachments, and a raw escape hatch. Every tool has a concrete job; nothing looks like filler, though the auth flow alone consuming six tools inflates the count.
Core lifecycle is covered: space read/list, message CRUD, reactions, memberships, and message-level auth. Real gaps exist (no typed create_space, no DM creation via spaces.setup, no attachment upload/download, no update_space), but the raw_request tool is explicitly documented as the workaround for each, so agents are not dead-ended.