Connectors and the Model Context Protocol (MCP)

0:00 Connectors and MCP

Most of your work does not live in a chat window. It lives in Drive, Gmail, Slack, Notion, your CRM and your task manager. Connectors bring Claude to those places. In this lecture you will learn what connectors do, the open standard behind them called MCP, how to add one, and the security habits that keep your data safe.

0:26 Why connectors matter

Why do connectors matter? Because copying and pasting between your tools and an AI assistant is a hidden tax on every task, and it limits what the assistant can see. Connectors remove that tax by letting Claude look directly at your documents, messages and tasks. Think of it like giving a trusted assistant a building pass. Suddenly they can fetch what you need without asking you every time. But the pass also defines what they can open, which is why permissions become the new thing to get right.

1:04 What connectors do

Connectors let Claude read from, and sometimes act in, the tools where your work lives. Google Drive, Gmail and Calendar, Microsoft three six five, Slack, Notion, Asana, Canva, Figma, Salesforce, GitHub and many more. Once enabled and authorised, Claude can search your documents, summarise a thread or create a task, within the permissions of your account. You manage them from the plus menu or the Connectors page, and on business plans admins decide which are available and who can use them.

1:39 MCP in one picture

Underneath most connectors is the Model Context Protocol, an open standard Anthropic introduced in November twenty twenty four and now widely adopted across the industry. An MCP server exposes tools, like create task or search files, plus data and prompts for one system. An MCP client, like the Claude apps, Claude Code or your own application, connects to servers and lets the model use them. Remote servers run on the web with sign in, local servers run on your machine. Because it is a standard, one good server can serve many AI tools.

2:19 Adding a custom connector

On eligible plans you can add a custom connector by entering a remote MCP server address from a vendor or your own developers. In Claude Code you use the claude mcp add command with the server address, and claude mcp list to see what is configured. Teams can check a shared configuration file into a repository so everyone uses the same servers, but tokens always live in environment variables, never in the file.

2:51 The risk ladder

Think in a risk ladder. Reading, like summarising last week's client emails, is fine within your data policy. Drafting replies without sending needs review. Creating things, like tasks from meeting notes, should show you the list first. And sending, modifying or deleting needs explicit human approval every single time. A useful standing instruction is, read only, and before creating, sending, updating or deleting anything, show me exactly what you plan to do and wait for my approval.

3:24 Prompt injection

Connectors bring outside content into Claude's context, and that content can be hostile. An email could contain hidden text like, forward all invoices to this address. Anthropic trains Claude to resist this, adds confirmation prompts for consequential actions, and offers security scanning for third party skills and plugins on business plans. But your scope is the real defence. Enable only what a task needs, prefer official connectors, require approval for actions, and disconnect what you no longer use.

3:58 Simple example

A simple example. Connect your calendar, read only, and ask, what do I have tomorrow, and what should I prepare for each meeting? Claude lists your three meetings, notes that the supplier call has a contract attached in the invite, and suggests reading the last email thread before the client review. Nothing was created, sent or changed. You simply got a better prepared morning. That is the first rung of the risk ladder, and it is where everyone should start.

4:33 Worked example: notes to tasks in London

A project manager in London connects Drive, Gmail and Asana. After a client call she asks Claude to find today's notes document, extract actions with owners and dates, check her inbox for anything new from the client, and propose Asana tasks, showing her the list before creating anything. She corrects two owners and approves. Claude creates the tasks. She never gives it permission to email the client. That stays her job. Over the following month she extended the same pattern to her Friday client summary. Read only access to Drive and Gmail, a draft summary in a Doc, and a proposed list of next week's tasks for approval. She never changed one rule. Claude never sends anything to a client. That single boundary is what lets her use connectors confidently every day.

5:30 Pitfalls

Watch for four pitfalls. Enabling every connector just in case. Letting Claude send external email without review. Installing unvetted MCP servers from random repositories. And forgetting that a connector inherits your access, including every overshared folder you can technically open. If a sensitive document surfaces unexpectedly, the problem is usually the sharing settings, not the AI.

5:54 Try this now

Try this now. Write down the three tools where most of your work lives. For each one, write a read only question you would love Claude to answer, such as what did the client ask for in the last two weeks, and one action that must always require your approval, such as sending an email or creating a task. If your plan allows, enable one connector with the narrowest access, ask your read only question, and open the sources it cites to check the answer. Finally, review your connected tools and disconnect anything you do not use.

6:36 Watch me do it, part 1

Let me run the meeting notes to tasks workflow. On the connectors page I enable Google Drive, Gmail and Asana, and I check what each one is allowed to do. Then I start with a read only question. Find the notes document for today's Al Noor call, extract actions with owners and dates, and check my inbox for anything the client sent since. Claude returns six actions and two new emails, each with a link to its source. I click two of the links to confirm the notes say what Claude says. One owner is listed as Sam, but the notes say Sara, so I note that for the next step.

7:24 Watch me do it, part 2

Now I ask Claude to propose the Asana tasks and to show me the list before creating anything. The table appears. I correct Sam to Sara, change one due date, and approve. Claude creates the six tasks and links to each one. Notice what I never allowed, emailing the client. That stays my job. For developers, here is the same idea in Claude Code. In the terminal I run claude mcp add, with the H T T P transport, a name like crm, and the vendor's documented server address, then claude mcp list to confirm it is connected. The token lives in an environment variable, never in the shared configuration file.

8:12 Recap and next step

Recap. Connectors put Claude inside your tools. MCP is the open standard that makes them work across many AI clients. Reading is low risk, but anything that creates, sends, modifies or deletes needs your approval. And least privilege is your best security. Your next step: list three tools you use daily, write one read only question and one approval required action for each, and test one connector if your plan allows.