Lesson 6 of 8
Connectors & MCP
6 min read
Claude can talk about your calendar, your docs, your team chat — but wouldn't it be better if it could actually reach them? What if there were one standard socket every app could plug into?
One port, many tools
On its own, Claude only knows what's in the conversation. Connectors let it reach outside itself — your files, your calendar, your team's tools — by plugging into real services. They ride on [MCP](glossary://mcp), one shared standard, so any service connects the same way instead of a custom hookup for each. One port, many tools.
MCP is a universal port. Because every tool connects the same way, adding one is a plug-in, not a build.
Connect what it needs
With a connector plugged in, Claude stops just describing your tools and starts using them — pulling the doc, checking the calendar, posting the message. You decide which connectors to add and what each is allowed to do, so it only reaches the tools you've handed it.
A connector turns Claude from a talker into a doer — it can act inside the services you connect, not just talk about them.
A connector can act on your behalf, so only add ones you trust and read the permissions. "Read my files" and "send messages as me" are very different powers to hand over.
The shape of it
- —Connectors plug Claude into real tools and services so it can act.
- —They use MCP — one standard — so any service connects the same way.
- —You choose which connectors to add and what each may do.
You want Claude to actually post an update to your team channel — not just draft it. What makes that possible?
Continue in the app
Take the whole Get the most out of Claude course — tracked
Get your personalized path, progress and streaks in the app — this lesson and every next one, in order.