# Google Chat MCP (npm · @renzo.johnson/google-chat-mcp)

Google Chat MCP server: read spaces and messages, send, edit and delete messages, create spaces.

- Trust score: 68/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@renzo.johnson/google-chat-mcp`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-renzojohnson-google-chat-mcp/renzo-johnson-google-chat-mcp.md), [page](https://verifymcp.io/servers/com-renzojohnson-google-chat-mcp/renzo-johnson-google-chat-mcp)

## Channel facts

- Registry: `npm`
- Package: `@renzo.johnson/google-chat-mcp`
- Version: `26.11.14`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 416 tokens (~59/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Google Chat MCP server?

Google Chat MCP runs locally as an npm package, launched with npx -y @renzo.johnson/google-chat-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-renzojohnson-google-chat-mcp -- npx -y @renzo.johnson/google-chat-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-renzojohnson-google-chat-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@renzo.johnson/google-chat-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-renzojohnson-google-chat-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@renzo.johnson/google-chat-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-renzojohnson-google-chat-mcp -- npx -y @renzo.johnson/google-chat-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-renzojohnson-google-chat-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@renzo.johnson/google-chat-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-renzojohnson-google-chat-mcp --command npx --arg -y --arg @renzo.johnson/google-chat-mcp
```

### Hermes

```yaml
mcp_servers:
  com-renzojohnson-google-chat-mcp:
    command: "npx"
    args: ["-y", "@renzo.johnson/google-chat-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-renzojohnson-google-chat-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@renzo.johnson/google-chat-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-renzojohnson-google-chat-mcp -t stdio -c npx -a -y @renzo.johnson/google-chat-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-renzojohnson-google-chat-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@renzo.johnson/google-chat-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 64)

First indexed and scored.

## MCP tools (7)

### `ping` (~14 tokens)

Checks server connectivity and auth status

### `chat_list_spaces` (~69 tokens)

Lists the Chat spaces, group chats and direct messages you belong to.

Input parameters:

- `filter` (string): Filter, e.g. spaceType = "SPACE"
- `page_size` (number): Max spaces (default 100, max 1000)
- `page_token` (string): Pagination token

### `chat_get_space` (~32 tokens)

Gets details of one space.

Input parameters:

- `space` (string, required): Space name, e.g. spaces/AAAAxxxx

### `chat_list_messages` (~112 tokens)

Lists messages in a space, oldest first unless order is "desc".

Input parameters:

- `filter` (string): Filter, e.g. createTime > "2026-11-01T00:00:00Z"
- `order` (string): Order by create time (default asc)
- `page_size` (number): Max messages (default 50, max 1000)
- `page_token` (string): Pagination token
- `space` (string, required): Space name, e.g. spaces/AAAAxxxx

### `chat_get_message` (~34 tokens)

Gets one message by name.

Input parameters:

- `message` (string, required): Message name, e.g. spaces/AAAA/messages/BBBB

### `chat_list_members` (~62 tokens)

Lists the members of a space.

Input parameters:

- `page_size` (number): Max members (default 100, max 1000)
- `page_token` (string): Pagination token
- `space` (string, required): Space name, e.g. spaces/AAAAxxxx

### `chat_admin` (~93 tokens)

Google Chat actions as the signed-in user. Actions: send_message(space, text, thread_key?), update_message(message, text), create_space(display_name, description?). Destructive (confirm:true): delete_message(message). space is spaces/<id>; message is spaces/<id>/messages/<id>.

Input parameters:

- `action` (string, required): Admin action
- `params` (object): Action parameters; destructive actions also need confirm: true

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-renzojohnson-google-chat-mcp/renzo-johnson-google-chat-mcp#diagnostics

## Score history

- 2026-11-21: 68
- 2026-11-20: 67
- 2026-11-19: 67
- 2026-11-18: 66
- 2026-11-17: 66
- 2026-11-16: 65
- 2026-11-15: 65
- 2026-11-14: 64
- 2026-11-13: 64

## Common questions

### What is the Google Chat MCP server?

Google Chat MCP is listed in the public MCP registry as com.renzojohnson/google-chat-mcp. Google Chat MCP server: read spaces and messages, send, edit and delete messages, create spaces. This page covers its npm package (@renzo.johnson/google-chat-mcp).

### Is the Google Chat MCP server safe to use?

Google Chat MCP scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Google Chat MCP server expose?

Google Chat MCP exposes 7 tools: ping, chat_list_spaces, chat_get_space, chat_list_messages, chat_get_message, and 2 more. Their descriptions and schemas cost roughly 416 tokens of context every time the server is loaded.

### Is the Google Chat MCP server still maintained?

Google Chat MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Google Chat MCP server under?

Google Chat MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Google Chat MCP server?

VerifyMCP ran 15 checks on Google Chat MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Google Chat MCP: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@renzo.johnson/google-chat-mcp
- Socket report: https://socket.dev/npm/package/@renzo.johnson/google-chat-mcp
- Website: https://renzojohnson.com/contributions/google-chat-mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-renzojohnson-google-chat-mcp/renzo-johnson-google-chat-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-renzojohnson-google-chat-mcp/renzo-johnson-google-chat-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-renzojohnson-google-chat-mcp/renzo-johnson-google-chat-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-renzojohnson-google-chat-mcp/renzo-johnson-google-chat-mcp
