Playbook · AI Fluency

Your first MCP
connection in Claude.

MCP is the universal adapter for your work — the kind you pack for an overseas trip. One plug. Calendar, mail, drive — all draw power from a single chat. This is the 30-minute walkthrough, built around the Friday wrap-up: the small ritual that lets the weekend be a weekend.

01 —

The story.

The opening

// A familiar plateau

You use Claude for drafting and thinking. But it stops at the chat window.

Every time you want it to act on something — pull from your calendar, look at your sent mail, check a document — you copy-paste it in. Every. Single. Time.

The copy-paste tax is bigger than it looks. It's the reason most knowledge workers plateau at "I use AI for emails" and never get further. It's also the reason the weekly rituals that actually help — wrap-ups, retros, planning notes — get skipped on busy weeks. They take too long when they need to be cheap.

Most people start fixing this by reading the MCP docs. That's the wrong way to start. The docs explain what MCP is. They don't tell you what changes the first time you use it.

What changes is this: Claude stops being a chat. It becomes a tool that can reach into the systems you already use and do work that, until now, only you could do.

02 —

What MCP actually is.

Two ways to use Claude. The difference between them is the entire point of this playbook.

// Without MCP

A chat, behind glass.

You and Claude. You copy from your calendar. Paste into chat. Copy from your sent mail. Paste into chat. Copy what Claude wrote. Paste back into Gmail. The work gets done. The tax adds up to twenty minutes a day, every day.

// With MCP

The universal adapter.

MCP — Model Context Protocol — lets Claude reach into the systems you already use. You connect a tool once. After that, when a task needs your calendar or your mail or your drive, Claude goes and looks. No copy-paste. The chat becomes a desk with the right drawers open.

// A useful comparison

MCP is to Claude what the universal travel adapter is to your devices. One plug. Multiple sockets. You stop carrying five chargers and start treating the wall as something that just works. The shift in what the trip feels like is bigger than the device count would suggest.

03 —

Don't pick a tool. Pick a ritual.

The contrarian frame

// Where most people stall

Most AI productivity advice is about getting more done. This isn't that.

People who start with "let me connect Gmail and see what it can do" stall. The connector sits there, unused. The people who get value from MCP fast are the ones who say: every Friday afternoon I write a wrap-up and it takes 30 minutes. I want that to take five. They reverse-engineer the connections from the task.

The point of automating a weekly wrap-up isn't to free up time for more work. It's to make the wrap-up cheap enough that you'll actually do it every Friday. The ritual is what changes. You close the week properly. The weekend is the weekend. Monday morning, you pick up where you left off without 20 minutes of what was I doing again.

Start with the ritual. The tooling follows.

04 —

The worked example: the Friday wrap-up.

~20–30 min by hand

Most knowledge workers have some version of a Friday wrap-up. To a manager. To a team. To a client. To themselves — even if it's just a quick note in a journal, or a mental checklist on the commute home. When it's done well, it does three things.

01

Captures

What got done

A clear-eyed list of what you actually achieved this week. Not the meetings you sat in. The outcomes you moved.

02

Previews

What's coming

A short look at next week — the commitments, the deadlines, the prep you'll need. So Monday morning isn't a cold start.

03

Flags

What's missing

The bit that lets you walk away. If nothing's missing, the weekend is free. If something is — you caught it now, not at 9pm on Sunday.

// Why it takes 20–30 minutes by hand

Five different tabs. Five different lookups. All before the writing starts.

You scroll your calendar for what you actually did this week. Skim your sent mail for what you committed to or delivered. Open the project doc to remember where things landed. Write the summary. Spot what's missing before you close the laptop.

None of those steps are hard. They're just slow when you do them by hand, every Friday, forever. This is the exact workflow MCP shortcuts. Three connections. One prompt.

05 —

The setup, end-to-end.

~30 min · one time

→

Setup · Once · 30 min

Three connectors. One prompt.

~30 min

No code. No file editing. Six moves, in order. Times include the coffee. The auth flows are clicks, not configuration — if you can sign in to Google or Microsoft, you can finish this in one sitting.

Connect · one-time

Open Claude. Plug in.

The connector flow lives in Settings. You'll do it three times in a row.

1

Open Claude.ai and sign in.

~5 min · includes coffee

A free account works for this walkthrough. Once you're in, click your profile and open Settings → Connectors. This is where MCP lives in the Claude product. You'll see a list of services Claude can connect to.

2

Connect Google Calendar.

Settings → Connectors → Google Calendar → Connect

~3 min

Click Connect. Google's auth screen opens. Sign in with the Google account you actually use for work. Approve the access. You're back in Claude. The connector now shows Connected.

3

Connect Gmail and Drive the same way.

~5 min

Same flow. Same Google account. Three connectors, all green, all done. If you're on Microsoft 365 — Outlook, OneDrive, Teams — the same pattern works. The connectors are named differently and the auth screen is Microsoft's. Everything else is identical. Resist the urge to connect more. Three is the right number on day one. You're learning the pattern, not building a system.

Run · the prompt

One paste. Three lookups.

Claude uses connectors automatically when the task needs them — you don't toggle them in the chat box.

4

Start a new chat.

~1 min

Open a fresh conversation. The fact that you have connectors enabled isn't visible in the chat box. Claude will use them when the task needs them. Trust the design.

5

Run the prompt.

~5 min

Paste the prompt below. Edit the bracketed bits for your situation. Claude will go and look — calendar, then mail, then drive — one connector at a time. It surfaces what it found. Then it drafts.

// Paste this · adapt the bracketed parts

It's Friday afternoon. Help me write my weekly wrap-up so I can close out the week properly. Use my calendar to remind me what meetings I had this week. Skim my sent mail from the last five working days for what I committed to or delivered. If you find a document in my Drive called [your project name], use it for context. Give me three short sections: - What I got done this week - What's coming up next week - Anything that looks like it might be missing or unresolved Plain prose, no preamble, in my voice. Australian English.

// If you also need to send it on

Follow up with: "Now turn this into an email to [recipient]. Same content. Slightly more formal." Two prompts, both versions, no double work. The note for you stays the note for you. The email gets shaped for the audience.

6

Read, fix, close.

~10 min

The first draft will be 80% there. The last 20% is your voice, your nuance, the things only you know. Read the "what's missing" section twice. That's the one doing the real work. If it flags something — a deliverable you forgot, a reply you owe, a doc you said you'd send — handle it now. Five minutes on a Friday afternoon is much cheaper than the thought arriving on Sunday night. When the section is empty or all minor, close the laptop. The week is properly closed.

06 —

What to expect the first time.

Four honest things

No first run is perfect. Four things worth knowing before you press send — so the surprises feel useful instead of disappointing.

// Expectation 01

It won't be perfect.

The draft might miss context. It might mis-attribute a meeting. The fix is the same fix you'd give a junior colleague — tell it what to change. Claude remembers within the conversation. You're refining, not starting over.

// Expectation 02

It will surprise you in one direction.

Either it pulls something you forgot you did, or it misses something obvious. Both are useful. The forgotten thing makes the wrap-up better. The miss tells you what to add to next week's prompt.

// Expectation 03

The second time is the ritual.

Save the prompt — in a note, a doc, or a Claude project. Friday week two, paste it again. Edit for five minutes. By week four, it's the thing you do before you close your laptop. The weekend starts cleaner. Monday morning, you re-read last Friday's note and you're back in the work in under a minute.

// Expectation 04

The third connector will be obvious.

Once you've felt MCP work once, you'll notice the next workflow it could fix. Probably your Monday planning. Possibly your meeting prep. The pattern compounds. But — see the gotchas — don't connect everything on day one.

07 —

Three gotchas.

Worth knowing upfront

Three things that bite first-time MCP users. None are dealbreakers. All are easier when you spot them on day one rather than week three.

// Gotcha 01

Permissions matter.

MCP can only see what your account can see. If a doc is shared with you, it works. If it isn't, it doesn't. The fix isn't technical — it's sharing the doc, or asking someone to share it. Spend a minute checking access before you blame the connector.

// Gotcha 02

Privacy is a real question.

The data Claude reads through MCP is governed by Anthropic's privacy terms. Read them. Know what you're comfortable with. For personal-productivity workflows in a personal account, most people are fine. For client data, regulated data, or anything you wouldn't paste into a chat window — check your employer's AI policy first.

// Gotcha 03

Don't connect everything on day one.

The temptation after the first win is to connect ten services. Don't. Each new connector is another permission scope, another surface to think about. Add the next one when the next task needs it. A working three-connector setup beats a sprawling ten-connector pile every time.

08 —

Where to go next.

Three more rituals

Same three connectors. Same pattern. Different prompts. Each one swaps a recurring high-effort task for a five-minute ritual. Run them in any order — but Monday planning is the one most people add second.

// Next 01

Monday planning.

The mirror image of the Friday wrap-up. Tells you where the week is dense before it hits. Catches the over-commitments while you can still do something about them.

Read my calendar for the week ahead. Read my last five sent emails. Tell me where the week is dense, where I've over-committed, and what looks like it's missing prep.

// Next 02

Meeting prep.

Ten minutes before any meeting. Pulls the email thread, the doc, and what you discussed last time into a one-page brief. You walk in knowing what's on their mind, not yours.

My next meeting is at 2pm with [name]. Find the most recent email thread, find the relevant Drive doc, and write me a one-page brief: what we last discussed, what they're likely to raise, what I need to land.

// Next 03

Inbox triage.

Twenty unread emails become four piles. The "today" pile arrives with draft replies in your voice. You stop sorting and start choosing. Best run on Monday morning, or after a long meeting block.

Look at my unread mail from the last 48 hours. Group it into: needs a reply today, needs a reply this week, FYI only, can be archived. For the today ones, draft replies in my voice.

// What this opens up

Three clicks. One ritual. The pattern compounds.

Not because connecting Google Calendar is technically demanding — it isn't, the auth flow takes seconds — but because the muscle of let Claude reach into the system is new. Once you've felt one workflow shortcut from 30 minutes to 5, the next ones are obvious. Most knowledge workers who try this end up with three to five rituals inside a month: weekly wrap-ups, Monday planning, meeting prep, inbox triage.

The biggest unlock isn't five minutes saved on a Friday afternoon. It's the rituals you stop skipping — the wrap-ups, retros, planning notes that used to get cut on busy weeks because they took too long when they needed to be cheap. That adds up. So does the weekend.