Claude MCP for Non-Developers — Connect Claude to Gmail, Calendar & Drive

Before I set this up, a typical morning looked like this.

Open Gmail. Read through unread emails. Open a new tab for Google Calendar. Check what meetings I had. Open Drive to find the document for the first one. Go back to Gmail to re-read the thread with the person I was meeting. Open Claude in another tab. Paste everything in manually. Ask my question.

Four tabs. Fifteen minutes. Every single morning.

Here is what my morning looks like now.

I open Claude. I type one message: "What are my most urgent emails today, what meetings do I have this afternoon, and can you find the brief for my 2pm call in Drive?"

Claude responds with all three. No switching. No pasting. No tabs.

The difference is MCP — Model Context Protocol. It connects Claude directly to Gmail, Google Calendar, and Google Drive. And the setup, once you know the steps, takes about 20 minutes.

This post walks through every step. The full video is at the bottom if you want to follow along on screen.

MCP stands for Model Context Protocol. Ignore the name.

Here is what it actually means for your business:

Without MCP, Claude only knows what you tell it. You paste an email in, Claude responds. You copy a calendar event in, Claude works with it. Every piece of information goes through you manually.

With MCP, Claude is connected. It reaches into your Gmail directly. It reads your calendar live. It searches your Drive without you uploading anything. You ask a question and Claude pulls the answer from the source.

The practical difference looks like this:

Three connections built this video: Gmail, Google Calendar, Google Drive. No code. No terminal. No developer.

Two things:

Claude Pro — $20 per month. MCP connectors require Pro or above.

A Google account — which you already have.

That is it. The only slightly technical step is a one-time Google Cloud Console setup that takes about 8 minutes. I walk through every click below. You never touch it again after the first time.

This is the step that stops most people. It looks technical from the outside. It is not. Here is every click:

Go to console.cloud.google.com. Sign in with your Google account.

Create a new project. Click the project dropdown at the top of the page. Click New Project. Name it anything — I called mine "Claude MCP." Click Create. Wait about 10 seconds for it to generate.

Enable the three APIs. Click the hamburger menu on the left. Go to APIs and Services, then Library.

Search for Gmail API. Click it. Click Enable. Go back to Library. Search for Google Calendar API. Enable. Go back to Library. Search for Google Drive API. Enable.

Three searches. Three enables. Done.

Create the OAuth credentials. Still in APIs and Services, click Credentials. Click Create Credentials. Select OAuth Client ID.

When prompted for Application Type, select Web Application. Give it a name — "Claude MCP" works.

Under Authorized Redirect URIs, click Add URI and paste exactly this:

Click Create. Google generates a Client ID and a Client Secret. Copy both into a Notepad document. You will use them in the next step.

That is the entire Google Cloud setup. Close the tab. You are done here.

Open Claude.ai. Click your profile icon in the top right. Go to Settings, then Connectors. Click Add Custom Connector.

Fill in two fields:

Server name: Gmail

Remote MCP server URL:

Click Advanced Settings. Paste your OAuth Client ID. Paste your OAuth Client Secret. Click Save.

Claude will redirect you to Google to authorize access. Click through. Allow access to Gmail. Done.

Test it immediately. Open a new Claude conversation and type:

Claude will pull your actual inbox. No paste. No upload. If you see real emails in the response, the connection is working.

Back to Settings → Connectors → Add Custom Connector.

Server name: Google Calendar

Remote MCP server URL:

Same OAuth Client ID and Client Secret from your Notepad. The same credentials work for all three Google connections. Authorize with Google. Done.

Test it:

Claude pulls your real calendar. Then try this follow-up in the same conversation:

That second prompt is where MCP changes everything. Claude is now reading your inbox and your calendar in the same conversation and connecting them. That is not possible with copy-paste. That is only possible because both tools are connected at the same time.

One more time. Settings → Connectors → Add Custom Connector.

Server name: Google Drive

Remote MCP server URL:

Same credentials. Authorize. Done.

Test it:

Claude finds the file, reads it, and summarizes it. You did not upload anything.

Now run the full combined test — this is the moment:

One message. Three tools. All connected.

Once all three connectors are live, here are the two workflows I use every single day. Both are copy-paste ready.

Workflow 1 — Morning Briefing From Live Data

This replaces 15 minutes of tab-switching every morning. Claude pulls live data from all three sources and writes the briefing.

Combine this with V14: If you built the Scheduled Task from last week, run this prompt as a scheduled task. Claude pulls live Gmail and Calendar data automatically every morning before you wake up. No prompt required. That is the V14 and V15 stack running together.

Workflow 2 — Meeting Prep in One Prompt

This used to take me 20 minutes before every client call. Finding the right email thread. Locating the shared brief. Reading back through notes. Writing a summary.

Now it takes one prompt and about 45 seconds.

Claude can draft emails on your behalf. But all emails must be sent manually through your own Gmail account. Claude writes the draft. You review it, edit it if needed, and hit send yourself.

This is not a limitation — it is a feature. You stay in control of every outgoing message. Claude does the thinking and the writing. You make the final call on what goes out.

The same logic applies to calendar invites and Drive file changes. Claude can create, draft, and suggest. Final actions go through you.

If you have followed the channel over the last three weeks, you now have all three pieces of the productivity stack:

V1 — Claude Cowork Basics Claude works with your local files in conversation.

V13 — Scheduled Tasks Claude works on your files automatically on a timer.

V14 — MCP Connections (this post) Claude connects to your real business tools — email, calendar, files.

V14 and V15 combined: Scheduled Tasks running the morning briefing prompt with live Gmail and Calendar data. Claude reviews your inbox and your schedule automatically every morning. No prompt from you. Output waiting in your folder when you wake up.

That is the complete stack. Three videos. One system.

Every step in this post is on screen in the video — live clicks through Google Cloud Console, all three connections being tested, and both workflows running with real data so you can see exactly what Claude produces.

📺 Watch here: https://youtu.be/ZM3mQ7_ZFb4

Includes both workflow prompts from this post plus all four Scheduled Task prompts from V13 — copy-paste ready.

📥 Free download: https://replacewithclaude.beehiiv.com/

Every workflow I build — MCP prompts, Scheduled Task templates, automation builds — is posted in the community. Founding member pricing is still open.

🏘️ Join here: skool.com/signup?ref=bd14267a4a8540868d97a596bc032542

Joe | replacewithclaude Stop hiring. Start replacing.

No affiliate links in this post — Claude Pro and Google Cloud Console are the only tools required. Google Cloud Console is free.