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.
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.
Add this to claude_desktop_config.json (or your client's equivalent), then restart.
{
"mcpServers": {
"filemayor": {
"command": "npx",
"args": ["filemayor", "mcp"]
}
}
}Drop one entry into your client's MCP config. No build step, no glue code — npx filemayor mcp starts the server on demand.
Claude Desktop, Cursor, or Zed picks up the FileMayor tools automatically on the next launch.
"Diagnose my Downloads", "dedupe this folder", "archive anything older than a year." The model plans; you approve.
Approved plans run locally and journal every move. Changed your mind? undo --all reverses the entire session.
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.
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.