How to organize files with Claude: a practical guide

Claude can think about your files. Moving them safely is a different problem.

Claude is remarkably good at reasoning about messy directories. Describe your Downloads folder and it will immediately suggest a sensible structure — separate installers from documents, archive files older than a year, deduplicate the screenshots. The plan is usually solid. The gap is between the plan and your actual filesystem.

Out of the box, Claude cannot move files. If you give it filesystem access through a generic shell tool or a raw MCP server, it can — but with no journal, no preview step, and no undo. You are one confident but mistaken AI response away from a folder you cannot reconstruct.

The right architecture gives Claude the ability to reason and plan while keeping a safety layer between its decisions and your files. That is exactly what FileMayor's MCP server does.

What the MCP integration looks like

Model Context Protocol (MCP) lets Claude Desktop and Claude Code connect to external tools as first-class capabilities. FileMayor ships an MCP server that exposes its core operations — diagnose, plan, apply, undo — to Claude as typed tools rather than raw shell commands.

When you connect FileMayor via MCP, Claude gains four specific abilities:

• Explain — scan a folder and return a structured health report: duplicates, stale files, oversized directories, naming inconsistencies.
• Cure — generate a detailed reorganisation plan with a justification for every proposed move. Nothing is applied yet.
• Apply — execute an approved plan, with every operation written to a write-ahead journal before the move happens.
• Undo — roll back an entire session to the exact pre-operation state, even after a system crash.

The key design choice: Claude proposes, you approve, FileMayor executes safely. Claude never bypasses the review step.

Setup in two minutes

1. Install FileMayor

FileMayor is a Node.js CLI, free on Mac, Windows, and Linux:

npm install -g filemayor

2. Add it to your MCP config

Open your Claude Desktop or Claude Code MCP configuration and add:

{
  "mcpServers": {
    "filemayor": {
      "command": "npx",
      "args": ["-y", "@filemayor/mcp"]
    }
  }
}

Restart Claude Desktop. You will see FileMayor appear in the tools panel. No API key, no account, no configuration beyond this.

3. Start with a diagnosis

The safest first message to Claude once FileMayor is connected:

Diagnose my Downloads folder and tell me what you find.

Claude will call filemayor explain and return a health score plus a breakdown of problems. No files are moved. You are just looking.

Real examples of what you can ask

Once connected, Claude understands natural-language instructions about your filesystem and translates them into safe FileMayor operations:

• “Archive everything in Downloads older than 6 months.”
• “Find duplicates in my Documents folder and show me the plan before doing anything.”
• “Move all the screenshots on my Desktop into a Screenshots folder.”
• “Organise my project folder by file type.”
• “What did I last change? Undo the last session.”

For every operation that would move files, Claude generates a plan first. You can ask it to explain any step, modify the plan, or cancel it. Only when you say “apply this” does anything change on disk.

Claude reasons about your files. FileMayor makes sure nothing moves until you say so — and that it can all come back if you change your mind.

Why not just use a shell tool with Claude?

Claude Code and many Claude Desktop setups offer a generic shell or Bash tool. You could, in principle, ask Claude to run mv and cp directly. Three reasons not to:

No preview step

A shell tool applies immediately. If Claude misunderstood your instruction — or if it was simply wrong about which files matched a pattern — the move has already happened.

No rollback

mv has no memory. There is no “undo last session”. Recovery means digging through backups or reconstructing the original state by hand.

No safety layers

FileMayor runs six independent checks between a plan and execution — the Chevza Doctrine. These catch destructive operation shapes, scope violations, and semantic errors that look reasonable in the plan but would cause real damage on disk. A raw shell tool has none of this.

The combination of Claude's natural-language understanding and FileMayor's safety architecture gives you something neither provides alone: an AI that can actually reorganise your filesystem without the risk that usually comes with it.

Getting started

FileMayor is free, installs in under a minute, and works on Mac, Windows, and Linux. The MCP server requires no additional configuration beyond the JSON snippet above.

If you are already using Claude Desktop or Claude Code daily, adding FileMayor takes two minutes and gives Claude one of the most useful capabilities it can have for everyday work.

• Download FileMayor →
• Full MCP setup guide →