The single fastest way to understand why MCP matters is to connect one server and watch your assistant do something it couldn't do a minute earlier — reach into a real folder on your computer and work with your actual files.

No code. About ten minutes. Here's exactly how, using the filesystem server in Claude Desktop, because it's the most tangible first win and the safest one to reason about.

Before you start

You need Claude Desktop installed. That's it. Everything below is editing one small text file and following careful steps — if you can do that, you're ready. We'll point the assistant at a single folder you choose, so nothing else on your computer is in play.

Step 1 — Open the configuration file

Claude Desktop keeps its MCP setup in a small configuration file, reached through the app's settings. Inside, MCP servers live under one section called mcpServers. Each server you add is a single entry: a name you choose, plus instructions for how to start it.

Step 2 — Add the filesystem server

Add this single entry under mcpServers. The only part you change is the last line — point it at a real folder you're comfortable letting the assistant work in (ideally a dedicated test folder at first, not your whole drive):

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/path/to/your/folder"
      ]
    }
  }
}

Read in plain English, this just says: start this filesystem server program, and give it access to this one folder. The name "filesystem" is only a label for you. Nothing here is as intimidating as it looks.

Step 3 — Restart fully

Save the file, then completely quit and reopen Claude Desktop. This restart is the single most-forgotten step, and skipping it creates the false impression that the setup failed. Don't just close the window — fully quit and relaunch so it reloads the config.

Step 4 — Verify

Ask the assistant something explicit, like: "use the filesystem tools to list what's in my folder," or "create a short text file called notes.txt in my folder." Watch it actually do it. That moment — a chat assistant reaching into your real filesystem — is MCP working. You're done.

If it doesn't work, it's almost always one of these

• Nothing showed up? You probably didn't fully restart. Quit and reopen the app completely.
• The server failed to start? Check the folder path for typos, and make sure it actually exists.
• The assistant ignores it? Be explicit — name the tool, as in "use the filesystem tools to…". Once it uses it once, it reaches for it naturally after.

The one habit that makes it click

The setup is the easy part. The habit that turns this into real productivity is learning to direct instead of paste. Once the folder is connected, you stop shuttling text in and out of chat and start describing what you want done — "read the notes in this folder and summarize every decision," or "draft a new document from the existing ones here." The assistant does the reaching and reading; you do the directing and the judgment. That shift, from feeding to directing, is the whole point.

One safety note

Start the filesystem server pointed at a single dedicated folder, not your entire drive. You can always widen access later — it's far easier to grant more than to undo a mistake. And when you start connecting servers that touch important accounts, take a moment to trust the publisher first.

Free starter: I put this setup plus the next steps onto a 5-page cheat sheet — the servers worth connecting, a quick safety check, and a one-page reference. Grab it free: MCP Quick-Start Cheat Sheet

Go deeper: For every host (Claude Code and Cursor too), choosing servers safely, real workflows, and a 7-day plan, there's the full guide: MCP Made Simple

What's the first folder you'd connect — notes, a project, your whole documents folder? Tell me what you'd reach for first.