Fileman already has a real Claude Code story today:
In plain language: Claude Code can help with the planning desk, but it still does not get to walk into the warehouse and move boxes on its own.
Claude Code is a good current fit because Fileman already ships:
This is not “future roadmap” wording. It is the current shipped MCP boundary.
Use Claude Code with Fileman when you want it to:
Do not describe the current Claude Code integration as:
applyapply.execute is intentionally absent from Fileman MCP v1.
Claude Code already exposes a first-party MCP management command, so the shortest current route is:
claude mcp add fileman -- bash /absolute/path/to/fileman/tooling/runtime/run_mcp_stdio.sh
If you want to inspect or remove the entry later:
claude mcp list
claude mcp remove fileman
If your Claude Code setup wants the raw stdio shape instead of the helper command, the portable core is:
{
"name": "fileman",
"command": "bash",
"args": ["/absolute/path/to/fileman/tooling/runtime/run_mcp_stdio.sh"]
}
If you prefer an installed entrypoint, use fileman-mcp when it is available in your environment.