Skip to content
FileMayorby Chevza

Let your AI act on your filesystem.

The FileMayor MCP server gives Claude, Cursor, Zed, and any MCP-aware client the power to diagnose folders, plan moves, and apply them — under the same journaled, reversible guardrails as the CLI. One config entry. No data leaves the machine.

One entry in your MCP config.

Add this to claude_desktop_config.json (or your client's equivalent), then restart.

{
  "mcpServers": {
    "filemayor": {
      "command": "npx",
      "args": ["filemayor", "mcp"]
    }
  }
}
Claude DesktopClaude CodeCursorZed

Plan in chat. Apply with an undo.

01

Add the server

Drop one entry into your client's MCP config. No build step, no glue code — npx filemayor mcp starts the server on demand.

02

Restart the client

Claude Desktop, Cursor, or Zed picks up the FileMayor tools automatically on the next launch.

03

Ask in plain language

"Diagnose my Downloads", "dedupe this folder", "archive anything older than a year." The model plans; you approve.

04

Apply with rollback

Approved plans run locally and journal every move. Changed your mind? undo --all reverses the entire session.

An AI with hands — and a leash.

Giving a model write access to your filesystem sounds reckless. It is not — because the model only ever proposes. The FileMayor engine, not the AI, decides what is allowed, executes locally, and keeps a reversible record of every move.

  • Local-only execution

    The engine runs on your machine. No file contents are uploaded — ever.

  • Same guardrails

    Identical Chevza Doctrine safety layers as the CLI and desktop app.

  • Journaled & reversible

    Every operation is logged; undo from chat or the command line.

  • Zero glue code

    One config entry. npx handles the rest. Nothing to maintain.

FileMayor MCP — FAQ.

What is the FileMayor MCP server?
It is a Model Context Protocol server that exposes FileMayor's filesystem operations to AI assistants. Once installed, an MCP-aware client like Claude Desktop can diagnose folders, propose reorganisation plans, and apply them — using the same journaled, reversible engine as the FileMayor CLI and desktop app.
Which AI clients support the FileMayor MCP server?
Any client that speaks the Model Context Protocol. That includes Claude Desktop, Claude Code, Cursor, and Zed. You add one entry to the client's MCP configuration pointing at the filemayor CLI, restart, and the FileMayor tools become available in chat.
Is it safe to let an AI move my files?
The MCP server runs under the same six-layer Chevza Doctrine guardrails as the rest of FileMayor. The AI proposes a plan; nothing is touched until it is applied, the Guardrail layer refuses destructive batches, and every operation is journaled so undo --all reverses the whole session. Execution is local-only — no file contents leave the machine.
Does the MCP server send my files to the model?
No. Only metadata — names, sizes, paths, extensions — is shared so the model can reason about structure. File contents never leave your machine, and all execution happens locally.
How much does the FileMayor MCP server cost?
The MCP server is included. Personal use is available on the Free tier; unlimited bulk operations and the AI Curative Triad are part of Pro ($19/month). The same license applies across the CLI, desktop app, and MCP server.

Connect FileMayor to your AI.

Install the server, restart your client, and ask it to clean up a folder. The full walkthrough — including the Claude Code Skill — is in the guide.