Google Workspace MCP Server
Official remote MCP servers from Google for Gmail, Drive, Calendar, Chat, and People API, letting AI agents read and act on Workspace data.
Google Workspace MCP is a set of provider-hosted Model Context Protocol servers that expose Gmail, Google Drive, Google Calendar, Google Chat, and the People API to AI agents. Each Workspace product has its own remote endpoint under *.googleapis.com/mcp/v1, and clients authenticate using standard OAuth 2.0 with user-granted scopes. The servers inherit the user's existing permissions and Workspace data governance controls, so AI agents only see what the authenticated user is allowed to see.
The servers expose roughly 30 tools across the five services, covering common read and write actions: searching threads and creating drafts in Gmail, reading and creating files in Drive, listing and scheduling events in Calendar, sending messages in Chat, and looking up contacts and directory people. This makes the servers useful for end-user productivity agents as well as backend automations built on Gemini CLI, Claude, or other MCP clients.
The servers are currently available through Google's Public Developer Preview Program. Because they are hosted by Google directly, there is no code to clone or self-host: configuration is limited to creating an OAuth client in Google Cloud and pointing your MCP client at the relevant URL.
Tools
| Tool | Description |
|---|---|
create_draft |
Create a draft email in Gmail. |
list_drafts |
List Gmail draft messages for the authenticated user. |
get_thread |
Retrieve a specific Gmail thread and its messages. |
search_threads |
Search Gmail threads using Gmail query syntax. |
list_labels |
List all Gmail labels available to the user. |
create_label |
Create a new custom Gmail label. |
label_message |
Apply one or more labels to a Gmail message. |
unlabel_message |
Remove one or more labels from a Gmail message. |
label_thread |
Apply one or more labels to a Gmail thread. |
unlabel_thread |
Remove one or more labels from a Gmail thread. |
search_files |
Search files in Google Drive. |
list_recent_files |
List recently accessed Drive files. |
get_file_metadata |
Get metadata for a specific Drive file. |
get_file_permissions |
Get sharing permissions for a Drive file. |
read_file_content |
Read the content of a Drive file. |
download_file_content |
Download binary content of a Drive file. |
create_file |
Create a new file in Google Drive. |
list_calendars |
List the user's Google Calendars. |
list_events |
List events on a calendar within a time range. |
get_event |
Retrieve a specific calendar event. |
create_event |
Create a new calendar event. |
update_event |
Update an existing calendar event. |
delete_event |
Delete a calendar event. |
respond_to_event |
Respond to a calendar invitation (accept, decline, tentative). |
suggest_time |
Suggest meeting times that work for a set of attendees. |
get_user_profile |
Get the authenticated user's profile via the People API. |
search_contacts |
Search the user's personal contacts. |
search_directory_people |
Search people in the Workspace directory. |
search_conversations |
Find Google Chat spaces or direct message conversations. |
list_messages |
List messages in a Google Chat conversation. |
search_messages |
Search across Google Chat messages. |
send_message |
Send a message to a Google Chat space or direct message. |
Prerequisites
- A Google Cloud project with billing enabled
- Enrollment in the Google Workspace Developer Preview Program
- The Gmail, Drive, Calendar, Chat, and/or People API enabled in your project
- The corresponding MCP API enabled (e.g. Gmail MCP API)
- An OAuth 2.0 client ID and secret created in Google Cloud Console
- An OAuth consent screen configured with the scopes you intend to request
Server endpoints
- Gmail:
https://gmailmcp.googleapis.com/mcp/v1 - Drive:
https://drivemcp.googleapis.com/mcp/v1 - Calendar:
https://calendarmcp.googleapis.com/mcp/v1 - Chat:
https://chatmcp.googleapis.com/mcp/v1 - People:
https://people.googleapis.com/mcp/v1
Example client configuration (Gemini CLI)
{
"mcpServers": {
"gmail": {
"httpUrl": "https://gmailmcp.googleapis.com/mcp/v1",
"oauth": {
"enabled": true,
"clientId": "OAUTH_CLIENT_ID",
"clientSecret": "OAUTH_CLIENT_SECRET",
"scopes": [
"https://www.googleapis.com/auth/gmail.readonly",
"https://www.googleapis.com/auth/gmail.compose"
]
}
},
"drive": {
"httpUrl": "https://drivemcp.googleapis.com/mcp/v1",
"oauth": {
"enabled": true,
"clientId": "OAUTH_CLIENT_ID",
"clientSecret": "OAUTH_CLIENT_SECRET",
"scopes": ["https://www.googleapis.com/auth/drive"]
}
},
"calendar": {
"httpUrl": "https://calendarmcp.googleapis.com/mcp/v1",
"oauth": {
"enabled": true,
"clientId": "OAUTH_CLIENT_ID",
"clientSecret": "OAUTH_CLIENT_SECRET",
"scopes": ["https://www.googleapis.com/auth/calendar"]
}
}
}
}
Refer to each service's MCP guide for the exact recommended scopes:
- Triage an inbox: search Gmail threads for unread customer issues, label them by priority, and draft responses for review.
- Daily standup helper: pull today's calendar events with
list_events, summarize attendees, and send a recap to a Google Chat space withsend_message. - Meeting scheduling: use
suggest_timeandcreate_eventto schedule meetings across multiple attendees without manual back and forth. - Knowledge retrieval: search Drive for relevant docs, read their contents, and use them as grounding context for a Gemini or Claude agent.
- People lookup: resolve email addresses or names against the Workspace directory with
search_directory_peoplebefore sending messages or invites.
- "Search my Gmail for threads from acme.com in the last 14 days and label any unanswered ones as 'Follow up'."
- "Find a 30 minute slot tomorrow that works for me, alex@example.com, and priya@example.com, then create a meeting called 'Q3 planning'."
- "List my recent Drive files and summarize anything titled with 'roadmap'."
- "Search the Workspace directory for people on the data platform team and DM each of them in Google Chat with a link to the on-call rotation."
- "Look at today's calendar events and post a morning summary into the #team space."
- Official and hosted by Google, so no self-hosting, packaging, or token storage of your own.
- Broad coverage across the five most-used Workspace surfaces (Gmail, Drive, Calendar, Chat, People).
- Inherits the user's existing Workspace permissions and data governance controls via standard OAuth 2.0 scopes.
- Works with any MCP client that supports remote HTTP transport plus OAuth (Gemini CLI, Claude, IDEs).
- Part of the Public Developer Preview Program, so behavior and tool surface may change before general availability.
- Requires setting up a Google Cloud project, enabling multiple APIs, and configuring an OAuth consent screen before you can use it.
- Tool coverage is intentionally narrow per service (for example, no
send_messagein Gmail and limited Drive write operations); some workflows still need the underlying REST APIs.
- taylorwilsdon/google_workspace_mcp: community-maintained self-hosted MCP server covering Gmail, Drive, Calendar, Docs, Sheets, and more.
- Zapier MCP: exposes Google Workspace actions via Zapier's universal MCP layer.
- Composio MCP: hosted MCP layer with prebuilt Google Workspace tool packs.