What is an MCP, really? A plain-English guide

If you've been anywhere near AI news in the last six months, you've seen three letters everywhere: MCP. People drop it into tweets like you should already know. Let's fix that.

The short version

MCP stands for Model Context Protocol. It's a standard way for AI assistants (like Claude or ChatGPT) to plug into tools, services, and data sources. Think of it like USB-C for AI — one standard, many devices.

Why you should care (even as a non-developer)

If you use Cursor, Claude Code, Windsurf, or any modern AI assistant, MCPs are how they get superpowers:

• Read and write to your Notion
• Control your browser
• Query your database
• Send messages in Slack
• Search your emails

Each of those is "an MCP." Instead of copy-pasting context into a chat, the AI reaches out and gets what it needs.

A concrete example

Say you're writing a blog post and want the AI to check your past posts for a similar topic. Without MCP: you copy-paste every post into the chat. With the notion-mcp: the AI searches your Notion directly.

Task	Without MCP	With MCP
Check past posts	Copy-paste manually	AI searches automatically
Update a Linear ticket	Open Linear, edit, save	AI does it inline
Query a database	Export CSV, paste	AI queries directly

Do you need one?

Probably yes, eventually — but don't force it. Start with the tool you already use, see if there's an MCP that makes your life easier, install it, try it for a week.

The ones worth trying first:

1. Filesystem MCP — lets AI read/write local files
2. GitHub MCP — lets AI work with your repos
3. Notion MCP — if that's where your notes live

The catch

MCPs require a small amount of setup (connecting the tool, granting permission). Each tool has its own setup flow, and that's where most non-technical users get stuck. We have a guide for setting up Claude Code MCPs — start there.

---

TL;DR: MCP is the plug that lets AI assistants use your actual tools and data. If you use any AI coding tool, you'll eventually want one.