[ MCP SERVER SUMMARY ]
Google Chat MCP server summary
Google Chat MCP (Developer Preview) connects AI assistants to Chat spaces and messages with OAuth-backed permissions. Bifrost applies the same governance model you use for Gmail and Drive — one /mcp endpoint, scoped tools, full audit logs.
| Property | Details |
|---|---|
| Company | |
| Connection type | HTTP |
| Authentication | OAuth 2.0 (Google Cloud client) |
| Package or endpoint | https://chatmcp.googleapis.com/mcp/v1 |
| Capabilities | Chat spaces and messages, Collaboration workflows, Workspace messaging tools |
| Official documentation | Google Chat MCP documentation |
Before you start
- Google Cloud project with Chat MCP enabled
- OAuth client credentials
What you can do with Google Chat
- Summarize Chat spaces for executives through a governed gateway
- Restrict send-message tools to approved automation keys
- Correlate Chat tool calls with other Workspace MCP activity
[ HOW TO CONNECT ]
Connect Google Chat to Bifrost in three steps
Install Bifrost
Start the gateway locally or deploy in your VPC.
npx -y @maximhq/bifrost
Add Google Chat in MCP Gateway
Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and choose HTTP. Or register via the API below.
• Endpoint: https://chatmcp.googleapis.com/mcp/v1 (Google Cloud MCP supported products).
• Follow Google Workspace MCP setup for Chat API + Chat MCP API enablement.
Point clients at Bifrost /mcp
Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to Google Chat.
{
"mcpServers": {
"bifrost": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer vk_your_virtual_key"
}
}
}
}[ EXAMPLE CONFIG ]
Register Google Chat via API
Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "google-chat",
"connection_type": "http",
"connection_string": "https://chatmcp.googleapis.com/mcp/v1",
"auth_type": "oauth",
"tools_to_execute": [
"*"
]
}'[ WHY BIFROST ]
Run Google Chat through one governed gateway
Access control
Virtual keys, RBAC, and tool allowlists per team or agent.
Cost governance
Attribute MCP tool spend alongside LLM usage in one view.
Observability
Log every tool call with latency, server, and virtual key metadata.
Credential isolation
Upstream secrets stay in the gateway — not on every laptop.
[ FAQ ]
Common questions
What does the Google Chat MCP server do?
Google Chat exposes chat spaces and messages, collaboration workflows, workspace messaging tools to MCP-compatible AI clients. Bifrost connects to it as an upstream MCP client and exposes approved tools through one governed /mcp endpoint.
How does Google Chat authenticate when used with Bifrost?
Google Chat uses OAuth 2.0 (Google Cloud client). Store credentials in Bifrost's environment or credential configuration so they stay at the gateway instead of being copied into every AI client.
Can Claude Desktop, Cursor, or Claude Code use Google Chat through Bifrost?
Yes. After registering Google Chat in Bifrost, point any HTTP MCP-compatible client at the Bifrost /mcp endpoint and authenticate with a virtual key. The client sees only the tools allowed for that key.
[ RELATED SERVERS ]
More MCP integrations
Gmail
Connect AI assistants to Gmail to search messages, draft and send email, and automate inbox workflows through Google Workspace MCP.
Google Calendar
Let AI assistants access Google Calendar events and automate scheduling workflows through Google Workspace MCP.
Google Drive
Connect AI assistants to files and folders in Google Drive through Google Workspace MCP.