MCP, decoded

MCP is a plug standard. It stands for Model Context Protocol, which you can forget. What it means is that an AI assistant can connect to a tool, your calendar, a database, a browser, a notes app, through one agreed shape of plug, instead of needing a custom adapter for each.

Why it keeps appearing

Because it is how an agent gets hands. A chat window with no plugs can only answer. Plug in the calendar and it can check Thursday. Plug in the browser and it can look something up. Plug in your files and it can read them. Every “connectors” or “integrations” menu in a modern AI app is a row of these sockets.

What a connection actually is

A grant of access. When you connect your email, the assistant can read and sometimes send as you. That is the point, and it is also the risk, so the rule is the usual one: the narrowest access that does the job. Connect the calendar, not the password manager. The chat-or-agent page is the short version of why reach matters more than cleverness.

When you would set one up yourself

Rarely, unless you run an agent. Then often: it is how a coding agent gets a browser, how a scheduled agent reads a spreadsheet, how mine talks to the chat app on my phone. If you are there, ask the agent to do the wiring.

I want you to be able to use [the tool]. Check whether there is an MCP connector for it,
tell me what access it would need and what the risks are, and wait for me to say yes
before you connect anything.

If it connects first and explains later, that is the wrong order, and worth putting in your CLAUDE.md so it does not happen twice.