OpenApps

google-chat MCP server — tools & history

google-chat MCP server: observed open status, tool schemas, linked apps and version history.

google-chat

Endpoint: https://chatmcp.googleapis.com/mcp/v1

Observed status: open. Checked: 2026-10-13T05:07:53+00:00.

Linked apps

  • google-chat

    Search conversations, read and send Google Chat messages, and manage read state through Google's remote Chat MCP server.

Observed tools

  • list_messages — Retrieves messages from a specified Google Chat conversation (Space, direct message (DM) or group DM) in Markdown format. Allows filtering by thread, time range, and number of messages. Additionally, the next page of messages can be retrieved to allow for more context. Private messages (messages only visible to a single user) are filtered out.
  • search_conversations — Searches for Google Chat conversations (named spaces, direct messages (DMs), or group chats) by display name or participants to find conversation IDs. This tool searches conversation metadata, NOT message contents. To search within message history or find messages by keyword/sender/timestamp, use `search_messages`. If only `participants` are provided, this tool finds 1:1 direct messages (if one participant is provided) or group chats (if multiple participants are provided) that include the specified participants and the calling user. If only a `query` is provided, this tool searches for conversations where the query is a case-insensitive substring of the conversation's display name. If both `participants` and `query` are provided, this tool finds conversations by participants and then filters them by display name. If neither `participants` nor `query` are provided, this tool lists all conversations the calling user is a member of. This tool only lists conversations the calling user is a member of. Returns a list of conversation objects containing conversation IDs (format: `spaces/{space}`), display names, and conversation types. IMPORTANT: An empty `conversations` list does not mean there are no more results overall. If `next_page_token` is present, more pages can be fetched. If you get an empty list but a `next_page_token`, ask the user if you should continue the searching.
  • search_messages — Searches for Google Chat messages using keywords and filters returning them in Markdown format. Works across all spaces the user has access to, or can be scoped to a specific conversation. Follow this guidance when deciding to use `search_messages` vs other search or read tools: - Use `search_messages` when looking for specific message content, keywords, mentions, links, senders or unread messages potentially across multiple spaces or without a known conversation ID. - Use `list_messages` when you know the specific space or thread ID and want to read messages sequentially in chronological order. - Use `search_conversations` to find space metadata such as conversation IDs by space display name or participants (it searches metadata only, not message contents). If `searchParameters` is provided without specific filters, recent messages across conversations accessible to the user are returned.
  • send_message — Sends a Google Chat message to a conversation with Markdown formatting. This tool uses a conversation ID, an optional thread ID, and a message text as inputs. Conversation IDs can be found using the `search_conversations` tool. It returns the created message.

Data as of 2026-10-13T05:07:53+00:00.

OpenApps records store listings and observed changes. Store ranks are not download counts; launch dates may be derived or use the first observation. Coverage gaps are shown in the interactive catalog.

REST API specification · Guide for AI clients · Manage API keys and MCP connections