google-chat-mcp

An MCP (Model Context Protocol) server that connects Claude to your Google Chat workspace — search spaces, DMs, and full message history. All sender and member names are automatically resolved to real display names via the Google People/Directory API.

Each user authenticates with their own Google account. No shared credentials files, no admin access required.

What you can do with it

• Search your full message history across all spaces and DMs

• Ask Claude questions like "what did the team decide about X?", "find the doc Sarah shared in the eng channel", "what were we discussing last week about the API?"

• Browse spaces, read recent messages, see who's in a given space — with real names, not user IDs

• Ask "who have I spoken to in the last 3 days?" and get a named list

• Works with Cursor, Claude Code, Claude Desktop, and Cowork

Related MCP server: google-workspace-mcp-with-script

Setup

Quick install (one command)

git clone https://github.com/ROKT/google-chat-mcp-yash.git && cd google-chat-mcp-yash && pipx install -e . && google-chat-mcp setup --client-id YOUR_CLIENT_ID --client-secret YOUR_CLIENT_SECRET

Replace YOUR_CLIENT_ID and YOUR_CLIENT_SECRET with the values from 1Password or a teammate.

Don't have pipx? Run brew install pipx first.

What setup does

1. Saves your credentials locally to ~/.config/google-chat-mcp/env.json

2. Automatically configures ~/.cursor/mcp.json

3. Opens a browser for Google OAuth — sign in with your Rokt account

That's it. Reload Cursor (Cmd+Shift+P → Developer: Reload Window) and start chatting.

Interactive setup (if you prefer)

google-chat-mcp setup
# Prompts for Client ID and Client Secret interactively

Usage

Once connected, just ask Claude naturally:

Available MCP tools

Read

Write

All tools return real display names for senders and members — no raw user IDs.

Other MCP clients

The setup command auto-configures Cursor. For other clients, add manually:

Claude Code

Add to ~/.claude/settings.json:

{
  "mcpServers": {
    "google-chat": {
      "command": "google-chat-mcp",
      "args": ["serve"]
    }
  }
}

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

{
  "mcpServers": {
    "google-chat": {
      "command": "google-chat-mcp",
      "args": ["serve"]
    }
  }
}

For Claude Code and Claude Desktop, the serve command automatically loads saved credentials from ~/.config/google-chat-mcp/env.json — no env block needed.

Cowork

Copy skill/SKILL.md to your Cowork skills folder.

Commands

google-chat-mcp setup    # One-time setup (saves creds, configures Cursor, authenticates)
google-chat-mcp auth     # Re-authenticate with Google
google-chat-mcp serve    # Start MCP server (called automatically by MCP clients)
google-chat-mcp logout   # Revoke cached token

OAuth Scopes

Troubleshooting

No credentials found — Run google-chat-mcp setup to save your credentials.

Connection closed in Cursor — Run which google-chat-mcp and check the path matches what's in ~/.cursor/mcp.json. Re-run google-chat-mcp setup to fix.

Error 403 — Your Google Workspace may restrict Chat or People API access. Ask your admin.

Token expired — Run google-chat-mcp auth to refresh.

Force re-authentication — google-chat-mcp logout && google-chat-mcp auth

Privacy & security

• All authentication is handled by Google OAuth 2.0 — your password is never stored

• Read and write scopes are requested — Claude can search messages and send on your behalf (always with your confirmation)

• Your token is stored locally at ~/.config/google-chat-mcp/token.json

• OAuth client credentials are stored locally at ~/.config/google-chat-mcp/env.json

• Nothing is sent to any third-party server — the MCP server runs entirely on your machine

License

MIT