fm_initLABSCO SUMMARY
Preview-then-commit, so a batch of moves is reviewable before it happens.
The agent proposes the moves and you read the plan as a list before a single file changes place. Because the session is shared with the command-line tool, that reviewing does not have to happen inside the chat — you can look at what was staged, and commit it, from your own terminal.
What it is
A .NET global tool that runs as a command line and as an MCP server. Moves are staged rather than executed: the agent opens a session at a base directory, stages each move, previews the whole set, then commits or cancels it. The command line and the MCP server share one session store, so a batch staged by the agent can be inspected — and committed — from your own terminal.
What you get
- A session opened at a base directory, with every path taken relative to it
- Moves staged one at a time, for a single file or a whole directory
- A preview of everything staged, read before any file is touched
- Commit, which executes the staged batch in one go, or cancel, which discards it
- Destination folders created automatically when the target path does not exist yet
- Directory moves that carry their nested structure with them
- Overwriting an existing destination only when the move is staged with the overwrite option
- Paths outside the session's base directory rejected rather than followed
Requirements
The .NET tooling used to install a global tool, after which the command it installs is what the MCP client launches. Nothing else: no account, no key, and no service to reach.
Setup effort
One command — dotnet tool install --global FileMoverMcp
USE CASES
01
Reorganising a folder with a review step
Open a session on the folder, stage every move, read the preview, then commit the whole batch in one go.
02
Backing out of a plan you do not like
Preview lists what is staged; cancel discards the session and leaves every file where it was.
03
Moving a directory into a path that does not exist yet
The nested structure travels with the directory, and destination folders that are missing get created.
6 tools
Listed in project docs. Your client may show a different list.
fm_movefm_previewfm_commitfm_cancelfm_helpBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
dotnet on PATH (the .NET SDK, for dotnet tool install)
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
dotnet tool install --global FileMoverMcpMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add filemover -- fm --mcpCursor
CURSOR · JSON
{
"mcpServers": {
"filemover": {
"command": "fm",
"args": [
"--mcp"
]
}
}
}
