← All servers

google-workspace

connects

google-mcp.proscendia.com

Permissioned access to Gmail, Drive and Calendar via the user's own Google account

https://google-mcp.proscendia.com/mcpWebsiteOAuthlast checked 24 Aug 2026spoke MCP on 3 of 3 checks (30 days)initialize in 235 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme
OAuth
Issuer
https://google-mcp.proscendia.com/
Dynamic client registration
Advertised (RFC 7591)
Client ID Metadata Document
Supported

A client identifies itself by a URL to its own metadata, so no registration step is required.

PKCE
S256
Grant types
authorization_code, refresh_token
Scopes
https://www.googleapis.com/auth/calendar, https://www.googleapis.com/auth/calendar.events, https://www.googleapis.com/auth/calendar.readonly, https://www.googleapis.com/auth/chat.messages, https://www.googleapis.com/auth/chat.messages.readonly, https://www.googleapis.com/auth/chat.spaces, https://www.googleapis.com/auth/chat.spaces.readonly, https://www.googleapis.com/auth/contacts, https://www.googleapis.com/auth/contacts.readonly, https://www.googleapis.com/auth/cse, https://www.googleapis.com/auth/documents, https://www.googleapis.com/auth/documents.readonly, https://www.googleapis.com/auth/drive, https://www.googleapis.com/auth/drive.file, https://www.googleapis.com/auth/drive.readonly, https://www.googleapis.com/auth/forms.body, https://www.googleapis.com/auth/forms.body.readonly, https://www.googleapis.com/auth/forms.responses.readonly, https://www.googleapis.com/auth/gmail.compose, https://www.googleapis.com/auth/gmail.labels, https://www.googleapis.com/auth/gmail.modify, https://www.googleapis.com/auth/gmail.readonly, https://www.googleapis.com/auth/gmail.send, https://www.googleapis.com/auth/gmail.settings.basic, https://www.googleapis.com/auth/presentations, https://www.googleapis.com/auth/presentations.readonly, https://www.googleapis.com/auth/script.deployments, https://www.googleapis.com/auth/script.deployments.readonly, https://www.googleapis.com/auth/script.metrics, https://www.googleapis.com/auth/script.processes, https://www.googleapis.com/auth/script.projects, https://www.googleapis.com/auth/script.projects.readonly, https://www.googleapis.com/auth/spreadsheets, https://www.googleapis.com/auth/spreadsheets.readonly, https://www.googleapis.com/auth/tasks, https://www.googleapis.com/auth/tasks.readonly, https://www.googleapis.com/auth/userinfo.email, https://www.googleapis.com/auth/userinfo.profile, openid
Protected-resource metadata
Published (RFC 9728)
Anonymous access
Refused — credentials required

What the probe found

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

Contract history

No contract recorded yet — the server has not answered an anonymous connection.

Run this server? A verified owner can publish snapshots with their own credentials, and the contract history starts here, marked owner-reported.

mcpi-cli publish https://google-mcp.proscendia.com/mcp

Get alerted when this contract changes

Depend on this server? Leave an email. No contract is on record here yet, so alerts can only start once one is published — and alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

MCP status badge for google-workspace
[![MCP status](https://mcpi.app/servers/google-workspace/badge.svg)](https://mcpi.app/servers/google-workspace)

Own this server?

Sign in to claim this listing by proving control of the endpoint.