Give Claude Code access to your Gmail, Google Drive and Google Calendar

Do not do this unless you understand how prompt injection works, and the lethal trifecta. Most people should just use the more limited features available in the Claude Web app, and patiently await an official integration for Claude Code. Note also that your organisation's IT security team may prohibit this.

During setup, you'll need to create a project in Google Cloud Console, enable the relevant APIs, setup oAuth, and add yourself as a test user. If you don't already know how to do these things, that means you should stop reading this blog post.

When you get serious about Claude Skills, you'll want to create calendar events, send emails, pull documents from Google Drive, and so on.

To get set up, first install my secure MCP install skill. Then ask Claude:

Please install this MCP server using your secure-mcp-install skill.

https://github.com/c0webster/hardened-google-workspace-mcp

The server name should be "google-workspace".

Appendix 1. Migrating from the original Workspace MCP

Earlier versions of this post recommended the non-hardened MCP server.

Most people should switch. To do that, just ask Claude:

Currently we are using Google Workspace MCP. I'd like to replace it with this hardened fork: https://github.com/c0webster/hardened-google-workspace-mcp

Please make a plan for doing this. Make sure to keep the credentials I already copied from Google Cloud Console, and use them in the forked version. The MCP server name should be "google-workspace".