MCP: connect it to your own data

Lesson 1's fourth fact was that the model sees only the window, and the only way in was to paste or attach. That's still true. What's changed is that the assistant can now be given tools that fetch things into the window for it: your calendar for next week, the last five emails from a client, a file from a shared drive, a record from the CRM. The standard most of these tools use is called MCP, the Model Context Protocol. You don't need to know how it works. You need to know what it changes and where the risks are.

What a connector actually does

When you connect, say, your calendar, nothing is copied into the model. The assistant gains the ability to ask the calendar a question ("what's on Tuesday?") when a task needs it, and the answer lands in the window like anything else. The same applies to writing: an email connector might let it draft a message, or draft and send, depending on what you allowed.

The result is that lesson 5's first question, "does it need my data, live, every time?", often stops requiring a specialised product. "Prepare me for tomorrow's meetings" becomes a thing your general assistant can do, because it can read the calendar, find the attendees' last emails, and pull the relevant file. It's the same model as before. It just has doors.

What it changes in practice

A few tasks that go from clumsy to natural once connected:

• Meeting prep. "For each meeting tomorrow, give me the last thing we exchanged with the attendees and any open items." Previously ten minutes of searching, now one request.
• Inbox triage. "Which emails from this week need a reply from me, and draft the three shortest." Drafts land in your drafts folder; you send.
• Finding things. "Find the proposal we sent to that client in the spring." Across drive and email, by description.
• Reports from systems. "Pull this month's closed deals from the CRM and write the summary in my format." The format is the skill from lesson 7; the data comes through the door.
• Keeping records. "Add a note to the account saying we agreed a two-week extension." Write access, so think before enabling.

Notice the pattern: the workflows from lesson 6 and the skills from lesson 7 are exactly the same. The connector just removes the pasting.

The three permissions

Before you switch on any connector, three questions. They take a minute and they're the whole safety story.

1. Read, or read and write? Reading your calendar is low-risk. Sending email, editing records, deleting files is a different category. Start read-only. Add write access to one specific thing only when you've seen the read side behave for a couple of weeks. "Draft but don't send" is the setting to look for in email connectors, and it's the right one for almost everyone.

2. Which data, exactly? "All of Drive" and "this one folder" are different decisions. Narrow it. A connector that can see the finance folder can put the finance folder into the window, and anything in the window can end up in an answer.

3. Whose rules apply? If this is a work account, your company has rules about where data may go, and the connector sends data to the assistant's provider. Many companies have approved specific assistants and connectors and banned others. Ask before connecting a work system; "I didn't know" is not a good position. For personal accounts, read what the provider does with the data. It's usually in a settings page, in plain language, and it's worth two minutes.

A new kind of mistake

Connected assistants make a mistake the unconnected ones can't: acting on the wrong thing. Emailing the wrong Dave. Updating the wrong record. Reading a file with instructions in it (a web page, a document someone sent you) and treating those instructions as yours. The good assistants are built to resist that last one, and they ask before doing anything irreversible. But the general rule holds: the more the assistant can do, the more your check step matters. For anything that writes, read before you confirm. Every time.

How to connect one

In the assistant's settings there's a section called connectors, integrations, apps or extensions, depending on the product. Pick one, sign in to the service, choose the permission. The whole thing takes two minutes. Start with the calendar: lowest risk, immediately useful, and you'll see within a day whether you like working this way.

If your company runs the assistant, the available connectors are chosen by the admin, which is a feature. Someone has already answered question three for you.

The habit

Connect only what a real task needs. Read before write. Narrow before broad. Ask about work accounts. And when it drafts something to send, read it as if you'd written it, because as far as the recipient is concerned, you did.