Google Chat

nuccio4stars

MCP Server for trustly use Claude connected to Google Chat

1# Google Chat

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: Apache-2.0
Last checked: 2026-10-28

Stars: 4
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Google Chat?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Google Chat need an API key?

No required environment variable is listed on this record.

What transport does Google Chat use?

Google Chat runs locally over stdio.

When was Google Chat last checked?

Last checked 2026-10-28. MCP Server for trustly use Claude connected to Google Chat

From the publisher

Documentation

MCP Server for Google Chat with ACL

An MCP server that connects Claude Desktop to Google Chat. It is designed to run locally on each user's machine: Claude Desktop spawns the server automatically and communicates with it over stdio, so no separate process or network endpoint is needed.

Key features

Per-space allowlist: only the spaces you list are reachable, each with read access, write access or both (independent of each other).
No direct messages: sending to DMs and group chats is blocked.
Separate tools for interactive and automated sends: send_message posts only to regular spaces and is meant to require your approval in the client; send_message_unattended posts only to spaces marked :unattended, for scheduled tasks. When the client supports it, send_message also asks you to confirm the exact text and target space.
Your own identity: each user authenticates with their own Google account, so messages come from the real person, not a shared bot.

See docs/configuration.md for everything that can be configured, and its security implications.

Available tools

Tool	Permission	Description
`list_spaces`	—	List configured spaces with their r/w flags
`get_space`	read	Get details of a space
`list_messages`	read	List messages in a space (optional filter)
`send_message`	write	Send a message to a space without `:unattended` (see Sending messages)
`send_message_unattended`	write	Send a message to a `:unattended` space, without confirmation (for scheduled tasks)
`list_members`	read	List members of a space
`chat_auth_status`	—	OAuth token status and expiry warning (works without a valid token)

Setup

1. OAuth credentials on Google Cloud Console

Open console.cloud.google.com and select (or create) a project
Go to APIs & Services → Library, search for Google Chat API and enable it
Go to APIs & Services → OAuth consent screen:
- Choose Internal if you use a Google Workspace organisation (no verification required), otherwise External
- Add the following scopes:
  - https://www.googleapis.com/auth/chat.spaces.readonly
  - https://www.googleapis.com/auth/chat.messages
  - https://www.googleapis.com/auth/chat.memberships.readonly
Go to APIs & Services → Credentials → Create Credentials → OAuth client ID:
- Application type: Desktop app
- Give it a name (e.g. "Claude MCP")
Click Download JSON and save the file as:
```
~/.config/google-chat-mcp/client_secrets.json
```
The structure of the file matches client_secrets.example.json in this repo.

On Windows with WSL, this path is inside the WSL filesystem (see below).

2. Installing WSL on Windows

Skip this section on Mac or Linux.

Open PowerShell as Administrator and run:
```
wsl --install
```
This installs WSL 2 with Ubuntu. A system restart is required.
After restarting, Ubuntu launches automatically. Create your user when prompted.

Inside the Ubuntu terminal, install uv:

curl -LsSf https://astral.sh/uv/install.sh | sh
source ~/.bashrc

Create the config folder and copy the client_secrets.json downloaded earlier:

mkdir -p ~/.config/google-chat-mcp
# Copy the file from Windows (replace "YourUser" with your Windows username):
cp /mnt/c/Users/YourUser/Downloads/client_secrets*.json ~/.config/google-chat-mcp/client_secrets.json

First run: OAuth authentication

Run this command once, in a terminal on your machine, to authorise access to your Google account — it is a separate CLI step, not something Claude runs for you, and it must be done before Claude Desktop is configured to start the server:

uvx "git+https://github.com/nuccio/google-chat-mcp" auth

A browser window will open. Sign in with your Google account and grant access. The token is saved to ~/.config/google-chat-mcp/token.json and refreshed automatically on subsequent runs. Its structure matches token.example.json in this repo.

Finding space IDs

To configure which spaces are accessible, you need their resource name (e.g. spaces/AAABBBCCC). There are two ways to find it.

Option A — CLI (after completing the auth step)

uvx "git+https://github.com/nuccio/google-chat-mcp" spaces

This prints a table of all spaces your account can access:

spaces/AAABBBCCC  Team General    [SPACE]
spaces/DDDEEEFFF  Announcements   [SPACE]
spaces/GGGHHH111  Alice Johnson   [DIRECT_MESSAGE]

The first column is the value to use with --space.

Option B — Google Chat URL

Open chat.google.com in your browser, navigate to the space, and look at the URL:

https://chat.google.com/room/AAABBBCCC/...
                              ^^^^^^^^^^^

The resource name is spaces/ followed by that segment.

Claude Desktop configuration

See docs/claude-desktop.md for where to put the configuration (macOS/Linux and Windows with WSL), and docs/configuration.md for what each option means.

Local development

git clone https://github.com/nuccio/google-chat-mcp
cd google-chat-mcp
uv pip install -e ".[dev]"

For running tests, including integration tests against real Google Chat spaces, see tests/README.md. To try latest in Claude Desktop before promoting it to stable, see docs/manual-testing.md.

Release and branch policy

Two tags separate the version people use every day from the one being tried:

Tag	Points to	How it moves
`latest`	the most recent commit on `main` whose automated tests passed	automatically, when the tests on `main` pass
`stable`	the last version tried in a real client and known to work	by hand, after trying `latest`

Clients configured with stable are not affected by bugs that the automated tests did not catch: a change reaches them only after someone has tried it in a real client. Some problems only show up there — for example, whether the client supports a given MCP feature.

Flow of a change:

The change is developed on its own branch, usually one per issue, and proposed with a pull request.
The automated tests run on every pull request (the Tests workflow, .github/workflows/tests.yml, on Python 3.11–3.13) and must pass before merging. Integration tests need a real OAuth token and are run by hand (see tests/README.md).
The pull request is merged into main with rebase: merge commits are disabled on this repository, and rebase keeps each commit of the branch on main. The tests run again on main, and if they pass latest moves to the new commit.
latest is tried in Claude Desktop, following docs/manual-testing.md.
If it works, latest is promoted to stable. If a bug turns up, stable stays where it is, and the fix goes through the same flow.

Promoting to stable: on GitHub, Actions → Release tags → Run workflow. Leave "Commit" empty to promote the commit latest points to, or enter the SHA of an earlier commit on main (e.g. to roll stable back). Commits that are not on main are refused. The workflow is in .github/workflows/release-tags.yml.

A green Tests run is required before merging only if it is set as a required status check in the branch protection of main (Settings → Branches); otherwise the rule relies on whoever merges.

For how to install a given version in Claude Desktop, see Choosing the version.

Google Chat

nuccio4stars

MCP Server for trustly use Claude connected to Google Chat

Communication

Install Run on PlugMCP

GitHub

Run on PlugMCP

1# Google Chat

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: Apache-2.0
Last checked: 2026-10-28

Stars: 4
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Google Chat?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Google Chat need an API key?

No required environment variable is listed on this record.

What transport does Google Chat use?

Google Chat runs locally over stdio.

When was Google Chat last checked?

Last checked 2026-10-28. MCP Server for trustly use Claude connected to Google Chat

From the publisher

Documentation

MCP Server for Google Chat with ACL

Key features

Per-space allowlist: only the spaces you list are reachable, each with read access, write access or both (independent of each other).
No direct messages: sending to DMs and group chats is blocked.
Separate tools for interactive and automated sends: send_message posts only to regular spaces and is meant to require your approval in the client; send_message_unattended posts only to spaces marked :unattended, for scheduled tasks. When the client supports it, send_message also asks you to confirm the exact text and target space.
Your own identity: each user authenticates with their own Google account, so messages come from the real person, not a shared bot.

See docs/configuration.md for everything that can be configured, and its security implications.

Available tools

Tool	Permission	Description
`list_spaces`	—	List configured spaces with their r/w flags
`get_space`	read	Get details of a space
`list_messages`	read	List messages in a space (optional filter)
`send_message`	write	Send a message to a space without `:unattended` (see Sending messages)
`send_message_unattended`	write	Send a message to a `:unattended` space, without confirmation (for scheduled tasks)
`list_members`	read	List members of a space
`chat_auth_status`	—	OAuth token status and expiry warning (works without a valid token)

Setup

1. OAuth credentials on Google Cloud Console

Open console.cloud.google.com and select (or create) a project
Go to APIs & Services → Library, search for Google Chat API and enable it
Go to APIs & Services → OAuth consent screen:
- Choose Internal if you use a Google Workspace organisation (no verification required), otherwise External
- Add the following scopes:
  - https://www.googleapis.com/auth/chat.spaces.readonly
  - https://www.googleapis.com/auth/chat.messages
  - https://www.googleapis.com/auth/chat.memberships.readonly
Go to APIs & Services → Credentials → Create Credentials → OAuth client ID:
- Application type: Desktop app
- Give it a name (e.g. "Claude MCP")
Click Download JSON and save the file as:
```
~/.config/google-chat-mcp/client_secrets.json
```
The structure of the file matches client_secrets.example.json in this repo.

On Windows with WSL, this path is inside the WSL filesystem (see below).

2. Installing WSL on Windows

Skip this section on Mac or Linux.

Open PowerShell as Administrator and run:
```
wsl --install
```
This installs WSL 2 with Ubuntu. A system restart is required.
After restarting, Ubuntu launches automatically. Create your user when prompted.

Inside the Ubuntu terminal, install uv:

curl -LsSf https://astral.sh/uv/install.sh | sh
source ~/.bashrc

Create the config folder and copy the client_secrets.json downloaded earlier:

mkdir -p ~/.config/google-chat-mcp
# Copy the file from Windows (replace "YourUser" with your Windows username):
cp /mnt/c/Users/YourUser/Downloads/client_secrets*.json ~/.config/google-chat-mcp/client_secrets.json

First run: OAuth authentication

uvx "git+https://github.com/nuccio/google-chat-mcp" auth

Finding space IDs

To configure which spaces are accessible, you need their resource name (e.g. spaces/AAABBBCCC). There are two ways to find it.

Option A — CLI (after completing the auth step)

uvx "git+https://github.com/nuccio/google-chat-mcp" spaces

This prints a table of all spaces your account can access:

spaces/AAABBBCCC  Team General    [SPACE]
spaces/DDDEEEFFF  Announcements   [SPACE]
spaces/GGGHHH111  Alice Johnson   [DIRECT_MESSAGE]

The first column is the value to use with --space.

Option B — Google Chat URL

Open chat.google.com in your browser, navigate to the space, and look at the URL:

https://chat.google.com/room/AAABBBCCC/...
                              ^^^^^^^^^^^

The resource name is spaces/ followed by that segment.

Claude Desktop configuration

See docs/claude-desktop.md for where to put the configuration (macOS/Linux and Windows with WSL), and docs/configuration.md for what each option means.

Local development

git clone https://github.com/nuccio/google-chat-mcp
cd google-chat-mcp
uv pip install -e ".[dev]"

For running tests, including integration tests against real Google Chat spaces, see tests/README.md. To try latest in Claude Desktop before promoting it to stable, see docs/manual-testing.md.

Release and branch policy

Two tags separate the version people use every day from the one being tried:

Tag	Points to	How it moves
`latest`	the most recent commit on `main` whose automated tests passed	automatically, when the tests on `main` pass
`stable`	the last version tried in a real client and known to work	by hand, after trying `latest`

Flow of a change:

The change is developed on its own branch, usually one per issue, and proposed with a pull request.
The automated tests run on every pull request (the Tests workflow, .github/workflows/tests.yml, on Python 3.11–3.13) and must pass before merging. Integration tests need a real OAuth token and are run by hand (see tests/README.md).
The pull request is merged into main with rebase: merge commits are disabled on this repository, and rebase keeps each commit of the branch on main. The tests run again on main, and if they pass latest moves to the new commit.
latest is tried in Claude Desktop, following docs/manual-testing.md.
If it works, latest is promoted to stable. If a bug turns up, stable stays where it is, and the fix goes through the same flow.

A green Tests run is required before merging only if it is set as a required status check in the branch protection of main (Settings → Branches); otherwise the rule relies on whoever merges.

For how to install a given version in Claude Desktop, see Choosing the version.