This lesson is being recorded

Every video of this course is being uploaded to my YouTube channel. Subscribe so you do not miss it.

Bruno AshfordBruno Ashford @brunoashfordSubscribe

Module 6 · Lesson 6.2 · 12 min

Email, Calendar and Docs

Connect Gmail or Microsoft 365 and Google Drive so Claude can read, summarise and draft, with sending kept under your control.

Module 6
Connecting Your Tools

Give your AI department safe access to where your business lives

Bruno Ashford
Bruno Ashford · Module 601 / 13
The problem
If you copy data into the chat and paste answers back out, you are the slowest part of your own AI.
Bruno Ashford
Bruno Ashford · Module 602 / 13
6.1 Plain English

MCP is a standard plug

Each tool publishes a panel of buttons. Claude can only press those.

  • Server: the tool's panel of actions
  • Tools: read, search, draft, update, send
  • You decide which buttons need approval
  • Nothing happens outside the panel
Bruno Ashford · Module 603 / 13
Two routes in

How a connection arrives

  1. 1claude.ai connectorsAdd in account settings, appear in Claude Code
  2. 2claude mcp addTerminal command with the vendor's URL
  3. 3/mcpCheck status, sign in, see tools
Bruno Ashford · Module 604 / 13
Scope

Who gets the connection

ScopeWhoUse it for
localYou, this projectDefault, testing, client data
projectTeam via .mcp.jsonApproved shared tools
userYou, all projectsPersonal utilities
Bruno Ashford · Module 605 / 13
6.2 Email, calendar, docs

Read, draft, then you send

The rule for the whole module.

  • Stage 1: read-only triage
  • Stage 2: drafts in your email client
  • Sending stays human
  • Deny rule on send tools
Bruno Ashford · Module 606 / 13
6.3 CRM and spreadsheets

Preview, approve, write

Every change appears as a table before it is saved.

  • Health report first, read-only
  • Record, field, old, new, reason
  • Approve by row number
  • Log every change
Bruno Ashford · Module 607 / 13
Roofing CRM cleanup (illustrative case)

What a read-only report found

1,140open deals before
612inactive 60+ days
318open deals after
Bruno Ashford · Module 608 / 13
6.4 Web research

Research you can repeat monthly

Public web for facts, your browser for signed-in work.

  • Link on every fact
  • claude --chrome for signed-in sites
  • Save to dated files
  • Spot-check three sources
Bruno Ashford · Module 609 / 13
6.5 The uncomfortable part
Connecting a tool hands a stranger's software a key to part of your business. Check the key first.
Bruno Ashford
Bruno Ashford · Module 610 / 13
Risk check

Five questions before any connector

  1. 1Who built it?Vendor, known project or anonymous
  2. 2What data?Clients, money, health, legal
  3. 3Can it write?Send, change, delete
  4. 4Where are secrets?Env variables, never shared files
  5. 5How do we exit?Remove and revoke
Bruno Ashford · Module 611 / 13
Project

Two systems, one workflow

CRM leads become email drafts. Nothing sends itself.

  • Score both connectors
  • Connect at local scope
  • Block send and delete
  • Measure minutes before and after
Bruno Ashford · Module 612 / 13
Recap
Connect what earns its place, read before you write, and keep the send button in human hands.
Bruno Ashford
Bruno Ashford · Module 613 / 13
01 / 13

Use ← → to move. The marker highlights text and the pencil draws on the slide; navigation locks while you annotate. Undo removes the last mark, Esc exits.

1Add the connectors in your Claude account

In claude.ai, open the connectors settings and add Gmail, Google Calendar and Google Drive, or the Microsoft 365 connector if your company runs on Outlook and SharePoint. Sign in with your work account and review the permissions screen before you accept. Connectors your organisation admin has not approved may be unavailable on Team or Enterprise plans, which is a good thing.

2Confirm they appear in Claude Code

Start Claude Code while logged in with the same account and open the /mcp panel. The claude.ai connectors appear alongside any servers you added in the terminal. If one shows as needing authentication, select it and follow the sign-in flow.

Terminal
/mcp
3Run a read-only inbox triage

Your first task only reads. Ask for a triage of the last 48 hours sorted by what needs you, what can be delegated and what can be ignored. Check it against your inbox manually the first three times.

Prompt for Claude
Read my unread emails from the last 48 hours. Do not send, archive, label or delete anything. Give me a table with: sender, subject, what they want, urgency (high, medium, low), and who should handle it (me, my team, nobody). Then list the three messages I must answer today.
4Move to drafts, never sends

Once the triage is reliable, let Claude create drafts for routine replies. Drafts sit in your email client waiting for you. You review, edit and send in seconds instead of writing from scratch.

Prompt for Claude
For each message you marked 'me' and routine, create a draft reply in my email, in my voice from CLAUDE.md. Keep each under 120 words. Do not send anything. When you finish, list the drafts you created so I can review them.
5Block sending with a permission rule

Belt and braces: in your project settings, add a deny rule for any tool that sends email, so even a confusing instruction cannot send on your behalf. MCP tools are named in the pattern mcp__server__tool, and you can see the exact names in the /mcp panel. You will learn the full permissions system in Module 11.

6Connect documents for context, not just storage

With Drive connected, Claude can find the last proposal you sent a client, read a signed contract, or pull numbers from a shared sheet. Ask it to cite the file name and link for every fact it uses, so you can verify in one click.

Most owners I meet spend the first hour of the day inside their inbox, triaging messages that a trained assistant could sort in ten minutes. The truth that hurts: you are the highest paid person in the company and you are doing the lowest leverage task in it.

In this lesson you connect the three systems that eat the most owner time: email, calendar and documents. The rule for the whole module starts here. Claude reads and drafts. You send.

Key points

  • Connect email, calendar and documents through your Claude account connectors.
  • Stage 1 is read-only triage; stage 2 is drafts; sending stays human.
  • A deny rule on send tools protects you from any ambiguous instruction.
  • Ask for file names and links so every fact can be verified.

Avoid

  • Letting the agent send emails in week one because the drafts looked good.
  • Connecting a personal Gmail and a work Gmail and forgetting which one the agent is reading.
  • Asking for 'clean up my inbox' without saying what may be archived or deleted.
Real-world example: an accounting practice

A four-person accounting practice in Manchester connected Microsoft 365. During tax season, the senior partner asked Claude every morning for a triage of client emails plus a list of documents still missing per client, checked against the shared folder. Claude drafted polite chaser emails for each missing document, all left as drafts. The partner reviewed and sent them in about 15 minutes, a job that previously took most of the morning.

Bruno Ashford Subscribe