MCP Without Code: Connect Your AI Assistant to a Folder, Step by Step

Most MCP tutorials start with "build a server in Python." If you just want your AI assistant to read the files you're working on, that's the wrong starting point. You don't need to build anything. You need to connect one server that already exists, check that it works, and know how to undo it.

MCP (the Model Context Protocol) is the open standard that lets an AI app talk to outside tools and data. The official site describes it as "a USB-C port for AI applications": one standard plug instead of a custom integration for every tool.

This walkthrough connects one server end to end: the official Filesystem server in Claude Desktop, following the steps in the MCP documentation. At the end there's a short note on doing the same in Cursor and on remote "connectors" that need no install at all.

What you'll have at the end

Claude Desktop will be able to read, create, move and search files, but only inside the folders you name. Per the docs, Claude asks for your approval before each file operation, so you stay in the loop.

Code needed: none. You will edit one small text file.

Step 0: Two things to install

Claude Desktop. Download it from claude.ai/download. The docs list macOS, Windows and Linux. If you already have it, use the Claude menu and pick "Check for Updates..." first.

Node.js. The Filesystem server, like many MCP servers, runs on Node.js. Open a terminal (Terminal on macOS, Command Prompt on Windows) and type:

node --version

If you see a version number, you're set. If you get "command not found", install the LTS version from nodejs.org. The docs recommend LTS for stability.

That's the only terminal command you need, unless something goes wrong later.

Step 1: Open the config file

MCP servers for Claude Desktop live in one JSON file. You don't have to find it by hand:

1. Click the Claude menu in your system menu bar (not the settings inside the chat window) and choose Settings...
2. Open the Developer tab in the left sidebar.
3. Click Edit Config.

This creates the file if it doesn't exist yet and opens it. For reference, it lives here:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/Claude/claude_desktop_config.json

Step 2: Add the server, with one narrow folder

The docs' example gives the server access to Desktop and Downloads. For a first try I'd go narrower: make a new, empty folder (say mcp-test on your Desktop), put a couple of throwaway files in it, and give the server only that folder. You can widen it once you trust the setup.

On macOS the file would look like this (replace username with your account name):

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/username/Desktop/mcp-test"
      ]
    }
  }
}

On Windows, the path uses double backslashes: "C:\\Users\\username\\Desktop\\mcp-test".

If the file already has other servers in it, don't replace everything. Add "filesystem": {...} as another entry inside mcpServers, with a comma between entries.

Here's what each part means, per the docs:

• "filesystem" is just a friendly name. It's what you'll see in Claude Desktop.
• "command": "npx" tells Claude Desktop to use Node's npx tool to run the server.
• "-y" auto-confirms installing the package.
• "@modelcontextprotocol/server-filesystem" is the server package.
• Every path after that is a folder the server may access. Nothing else.

The docs add a warning worth reading twice: the server "runs with your user account permissions, so it can perform any file operations you can perform manually" inside those folders. That's why the folder list is the most important line in this file.

Save the file.

Step 3: Restart properly

Closing the window isn't enough. Fully quit Claude Desktop and open it again, so it reads the new config and starts the server.

Step 4: Check that it's connected

In a new chat, click the "Add files, connectors, and more /" button in the bottom-left of the message box. Hover over Connectors, click Manage connectors, and select filesystem. You should see the list of tools the server exposes.

If "filesystem" isn't there, skip to the troubleshooting section below.

Step 5: A first task you can verify

Start with something you can check with your own eyes. With two or three files in mcp-test, try:

List the files in my mcp-test folder and tell me what each one contains.

Then something that writes:

Create a file called notes.txt in mcp-test with a three-line summary of those files.

Claude should ask for approval before the operation. Read what it wants to do, approve it, then open the folder and look. If the file is there with the content you expect, the connection works end to end.

The docs' own examples go further: saving a poem to your desktop, finding work files in Downloads, sorting images into a new folder. Moving and renaming are real changes to real files, so try those on copies first.

When it doesn't show up

The docs list these checks, in this order:

1. Restart completely (quit, not just close the window).
2. Check the JSON syntax. A missing comma or an extra bracket is enough to break it. Pasting the file into any JSON validator will point to the line.
3. Use absolute paths. /Users/username/Desktop/mcp-test, not Desktop/mcp-test or ~/Desktop/mcp-test.
4. Read the logs. On macOS they're in ~/Library/Logs/Claude, on Windows in %APPDATA%\Claude\logs, on Linux in ~/.config/Claude/logs. mcp.log covers connections in general; mcp-server-filesystem.log has that server's own output.
5. Run the server by hand to see the error directly:

npx -y @modelcontextprotocol/server-filesystem /Users/username/Desktop/mcp-test

If Node isn't installed or the path is wrong, this is usually where you'll see it.

Undo it

To disconnect, open the config again (Settings → Developer → Edit Config), delete the "filesystem" entry, save, and fully restart. Knowing how to remove a server is part of setting it up.

The same idea in Cursor

Cursor reads MCP servers from an mcp.json file: .cursor/mcp.json inside a project for project-only tools, or ~/.cursor/mcp.json in your home folder for tools everywhere, according to the Cursor docs. The mcpServers block above has the same shape. Cursor also offers one-click installs from its Customize page, and by default it asks for approval before using an MCP tool. You can click the arrow next to the tool name to see the arguments it will send.

No install at all: remote connectors

Some services run their MCP server on the internet. In Claude, those are added as custom connectors: Settings → Connectors → Add → "Add custom connector", paste the server URL, then sign in when asked (often via OAuth). The remote servers guide also shows that you can turn specific tools on or off in that connector's settings. Use that: if you only need read access, switch off the tools that write or delete.

Before you connect the next one

One server you understand is worth more than ten you don't. Before adding anything else, run the five questions from Before You Connect an MCP Server: A 5-Question Trust Check: who publishes it, what it runs, what it can reach, and so on. The docs say the same thing in short: only connect servers from trusted sources, review the permissions you grant, and remove connectors you no longer use.

Quick checklist

• [ ] Node.js installed (node --version works)
• [ ] Config opened via Settings → Developer → Edit Config
• [ ] Server entry added, other entries kept, JSON valid
• [ ] Only one narrow test folder listed, with an absolute path
• [ ] Claude Desktop fully quit and reopened
• [ ] "filesystem" visible under Manage connectors
• [ ] One read task and one write task verified by opening the folder
• [ ] You know how to remove the entry again

Where to go next

• MCP Made Simple: Connect Claude, Cursor & Your AI Tools to Everything (No Code Required): the full guide to the using side of MCP. It covers the mental model, setup in Claude Desktop, Claude Code and Cursor, the config file explained, a troubleshooting chapter, how to choose servers (with the trust check), real workflows for files, code and research, and a 7-day action plan.
• MCP Quick-Start Cheat Sheet (Free): a free 5-page sheet to keep open while you set things up.

This article was written with the assistance of AI and reviewed by the author.