Connectors & MCPs, without the jargon
This is the one bit of vocabulary worth knowing. It sounds technical. It isn’t. You’ll never touch code.
What is a “connector”?
A connector is a one-time permission. It lets Claude use a tool you already have — your Gmail, your calendar, your Google Drive — on your behalf. You click a button once, sign in the way you always do, and from then on Claude can read that inbox or check that calendar for you. That’s it. No setup, no code, no new account for most of them.
Think of it like giving a trusted assistant a key to one specific drawer — not the whole building, just the drawer you pointed at.
And “MCP”?
MCP is just the plumbing standard that makes connectors work — the “USB port” tools plug into so Claude can talk to them. You don’t configure it or think about it. When you see “MCP,” read it as “a tool Claude can connect to.” Nothing more.
The three kinds of tools
Gmail, Google Calendar, Google Drive. Native — just sign in once. Nothing to buy.
A tool you don’t have yet. Create a free account at the tool’s site, then connect it in Cowork with one click.
A tool without a direct connector. Zapier acts as the glue — one connector that reaches thousands of apps.
How do I know which I need?
You don’t have to work it out — your report tells you. Its setup checklist lists every tool your first system needs, in order, each tagged “already connected,” “create a free account,” or “connect in one click,” with the exact link. You just follow it.
Is any of this risky?
Every automation we recommend drafts and holds for your approval by default — Claude prepares the work, you’re the one who clicks send. Nothing goes out, spends money, or touches a customer without your yes. You can disconnect any tool at any time.