Level 2 · Connect — MCP
Hand it the keys
Claude reaches your real tools itself — a few tools, one action at a time, inside fences you draw.
01 What Connect is
Stop being the copy-paste bridge
At Chat, you read the calendar, copied the bit that mattered and pasted it in. A connector removes that hop.
One scoped link to one tool
Calendar, Gmail, Drive — or a custom MCP server.
It fetches the real data
Answers come from your actual week, not general knowledge.
It proposes; you commit
It drafts or suggests the action. You confirm it.
-
YouAsk in plain words
- “What’s on Tuesday?”
- asks
-
ClaudePicks the right tool
- calls
-
ConnectorHolds the keys you grantedread-only
- reads
-
Your calendarAnswers with real eventswrite: off
MCP (Model Context Protocol) is the open standard connectors speak.
02 Where it lives
Every key lives in Settings › Connectors
One screen to add a tool, read what it can do — and take it away again.
- 1
A connected tool
Standing access — it stays connected across chats.
- 2
Claude’s per-tool permission
Allow, ask or off for each tool — here the write tool is off.
- 3
Connect the next one
A sign-in on the provider’s consent screen — often all-or-nothing.
- 4
Add a custom connector
Paste an MCP server URL your IT team or vendor gave you.
Connectors
Let Claude use your apps and data — you choose what it can see and do.
-
1Google CalendarEvents, free/busy and invitesConnected2
What Claude can do1 of 2 on
- See your events and free/busyRead
- Create and edit eventsWrite
-
GmailSearch and read email, create drafts3Connect
-
Google DriveFind and read Docs, Sheets and filesConnect
-
Team wikiCustomhttps://mcp.example.dev/mcpConnected
Simplified mock-up · names and permission controls vary by plan and account
03 Try it
Grant the verb in your brief
The provider’s consent screen sets the scope — often all-or-nothing. Take the narrowest on offer; decline the rest.
Decide the verb first
Read-only job? Take the read-only option, if offered. Nothing wider.
Read ≠ write
A read grant can’t move a meeting, however you phrase it.
Then fence it in Claude
Set write tools to ask or off; revoke when the run is done.
04 The new risk
The risk lives in the writes
A wrong answer used to cost a worse paragraph. Now it can cost a draft to the wrong client.
Reads
Look, don’t touch
Searches your inbox, lists your week, opens a file
Reads the wrong record — and sounds sure
Ask for sources; open the record yourself
Nothing changed — remove the connector in Settings › Connectors to stop access
Writes
Change a live system
Drafts a reply, books an event, creates a file
Acts on a real system that others see
Tell it propose, don’t execute — then confirm
Delete the stray draft or event yourself — others may already have seen it
05 The verify reflex
Check the tool, not the model
The model can’t grade its own homework. “Are you sure?” just gets a confident yes.
Read before you trust
Open the real thread, file or event behind each claim.
Ask for the source
Every claim should name the event, file or sender.
Re-read after you act
“It ran” isn’t “it’s right” — check what landed.
Confirming the Phase 1 boundary before we start on Monday. Need your sign-off by Friday.
Genuine — a real scope question waiting on you. Act on it.
Invoice #4471 attached. Amount due: $12,400. (“Scope” appears only in the SOW footer.)
Mislabeled — it’s an invoice. Claude matched the word “scope” in a footer. Asking it “are you sure?” wouldn’t have caught this. Opening it did.
Claude flagged both as “scope decisions.” Open each — the model can’t grade its own homework.
06 Do it now
Four small steps, in real Claude
-
Step 1 of 4
Connect one tool
One connector is enough to feel the difference.
You should see: A “connected” tick next to the tool.
In the Claude app: Settings › Connectors → connect your Calendar (or Gmail). Take the narrowest option on offer, then set write tools to ask or off. -
Step 2 of 4
Ask about your real week
Now it answers from your world, not general knowledge.
You should see: Your actual meetings, with prep suggestions.
-
Step 3 of 4
Ask something honest
Connected Claude can judge, not just fetch.
You should see: An opinion grounded in your calendar.
-
Step 4 of 4
Make the artifact
From fetch → to finished briefing.
You should see: A briefing you’d actually read on Monday.
paste into ClaudeWrite my Monday briefing: top 3 priorities from my calendar, anything I seem to owe people, and one thing I should decline.
One step = one paste into Claude (the mobile app is perfect). Each step you mark done climbs a floor; progress saves on this device.
07 Decide
Is a connector the right level for this?
You want to handle something using your real calendar, mail or files. Which fits?
Pick the closest match — you’ll get a verdict.
08 Capstone
The whole level in one prompt
- Connect your calendar, mail or Drive at the narrowest scope on offer (read-only, if offered).
- Paste the prompt in and check every claim names its source.
- Open the most load-bearing record yourself — then review your scopes.
I'm practicing connecting you to my real tools at READ-ONLY scope. Be my tutor and hold me to the discipline. My objective: tell me what this week actually looks like and what I need to prep — especially Tuesday — read from my real calendar, inbox, and Drive. Don't guess. Rules for this run: 1. READ-ONLY. Do not draft, label, create, or change anything. If something needs an action, propose it and stop for me. 2. For every claim, cite the specific event / file name / sender it came from, so I can open the real record myself. Don't infer beyond what's in the tools. 3. List my meetings with times; for each, flag anything I still need to prep and say which file or email tells you that; surface any unanswered emails tied to those meetings. Then, before I act: pick the single most load-bearing item and tell me exactly which record to open to verify it, and what would tell me you got the WRONG record (wrong version, same-titled file, a thread whose subject misleads). Don't tell me you're sure — point me at the source. Finally, remind me to review my connector scopes and per-tool permissions, and revoke anything I won't need again.
Wrap-up · check yourself
You’ve got Connect
Remember
You’re ready when you scope tight, gate every write and verify the real record — and keep wishing Claude could run the whole job for you. That wish is Level 3.