The filesystem MCP server, and a safer way to let Claude organise

The filesystem MCP server is the first thing most people connect to Claude, and for good reason. It is free, it is maintained by the Model Context Protocol project itself, and it lets Claude read, write, rename and move files in folders you choose. It is also the tool behind a lot of nervous posts asking what happens when Claude reorganises the wrong folder. For pictures, screenshots and saved links, Muse, a $29 Mac library with its own MCP server, is the safer fit, because anything an AI app removes goes to a Trash only you can empty.

This post sets out exactly what it can and cannot change, how to set it up so a mistake costs you little, and when a library app is the better fit for the job.

What can the filesystem MCP server do?

According to the server's own documentation, it offers thirteen tools. They fall into three groups:

• Reading: read a text file, read an image or other media file, read several files at once, list a folder (with or without sizes), show a folder tree, search for files by name pattern, and get a file's details.
• Writing: create or overwrite a file, edit part of a file, and create a folder.
• Moving: move or rename a file or folder. A move fails if something already exists at the destination.

A thirteenth tool lists the folders the server is allowed to touch. Those folders are whatever you name when you set it up, and it cannot see anything outside them.

Notice what is missing. There is no delete tool. Claude cannot remove a file through this server. That is reassuring, but it is not the whole story.

Can Claude lose or damage my files through it?

Yes, in two ways, even without a delete tool.

The first is overwriting. The write tool creates a new file or replaces an existing one completely, and the documentation itself adds "exercise caution with this". The edit tool changes a file in place. Neither keeps the previous version. If Claude writes over a document you cared about, the old one is gone unless Time Machine or another backup has it.

The second is scattering. Moving and renaming are the heart of "organise this folder" requests, and a plan that looked sensible can leave three hundred files renamed by a pattern you did not want, spread across folders Claude invented. Nothing is lost, strictly, but putting it back by hand can take longer than the tidy-up saved.

There is also a quieter risk. Claude reads what is in your files, and text inside a file can influence what it does next. A folder of downloaded documents is not always a folder of trustworthy instructions.

How to set it up safely

None of this is a reason to avoid it. It is a reason to set it up with a small blast radius:

1. Give it one working folder, not your home folder. Make a folder such as Claude Workspace and list only that. Copy files in when you want Claude to work on them.
2. Keep a backup running. Time Machine, or any versioned backup, turns an overwrite from a loss into an inconvenience.
3. Start with reading. Ask for a summary or a plan first ("suggest how you would rename these"), check it, then ask it to carry the plan out.
4. Work in batches. Twenty files at a time are easy to check. Two thousand are not.

A setup scoped to a single folder looks like this in Claude Desktop's config file:

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

Our Claude Desktop setup guide covers where that file lives and what to do when a server does not appear.

Filesystem server or a library app: which fits?

The filesystem server is general purpose. It sees files as names, folders and text. That makes it right for code, documents, notes and anything you want edited where it lives. It is less suited to a pile of pictures, screenshots and saved links, because to find "the orange poster" it has to open files one by one and look.

A library app that includes its own MCP server works the other way round. The app has already done the indexing, so an AI app asks it questions instead of walking your disk. Muse is one example. Things you save are copied into Muse's library folder, which stays plain folders you can open in Finder, and Claude works through Muse's own actions rather than your file system.

In Muse, anything an AI app removes goes to the Trash, which only you can empty. Before the first change an AI app or script makes each day, Muse saves a copy of your library and keeps the last seven, with Undo AI Changes in Settings > Library > Backup. Items you have hidden never appear to an AI app at all. The Connect AI Apps guide lists every action.

Plenty of people will want both: the filesystem server for a projects folder, and a library app for the visual things they collect. They sit side by side in the same config file without any trouble.