Local file tools for your AI agent
Connect Claude Code, Codex, Cursor and other agents to FileHop over MCP. They can convert, compress, merge and organize files on your computer, within limits you set.
Off by default. Limited to folders you share. Every call logged.
Download FileHop FreeWhat your agent can do
Ask in plain language. Your agent picks the tool and FileHop does the work on your computer.
Sort out a messy folder
"Find duplicates in Downloads and move invoices into a folder by year."
Process video and audio
"Trim this recording, shrink it for email and extract the audio."
Convert in bulk
"Convert these images to WebP and these spreadsheets to CSV."
Query your data
"Show me the schema of this Parquet file and export the top customers."
Set it up in a minute
Access stays off until you turn it on.
1. Turn it on
In FileHop, open Settings > Agents and turn on Let AI agents use FileHop.
2. Connect your agent
Use Connect for Claude Code, Codex, Claude Desktop, Cursor, VS Code, Windsurf or Gemini CLI, or copy the config for another client.
3. Share folders
Choose which folders agents can reach, and whether each is read-only or read and write.
What this does and doesn't do
What it gives you
- ✓ One local app for files, PDF, image, video, audio, data and archives, with typed tools instead of ad hoc shell commands.
- ✓ No overwrites: moves and copies pick unique names, renames refuse a taken name, and deleting sends files to the OS Trash.
- ✓ An activity log with Stop and Undo on each call, including refused calls.
- ✓ Conversion and compression run locally, with no hosted converter or per-file credits.
What it doesn't do
- — It doesn't stop an agent's shell access. An agent that can run commands can still do anything your account can.
- — It doesn't keep content away from your agent's provider. A cloud agent's provider receives whatever the agent reads.
- — It doesn't include an AI model. You bring your own agent.
- — Agents can't yet edit Word, Excel or PowerPoint files through FileHop.
Tool groups
Each toolset can be switched on or off.
Guardrails
Limits are set in FileHop, and apply to every call made through it.
- · Access is off by default, and turning it off pauses all agents immediately.
- · Agents reach only folders you share. The ~/FileHop workspace is always shared while access is on.
- · .ssh, .aws and Keychains are always denied.
- · Very broad folder grants come with a warning.
- · Delete confirmation is on by default where your agent app supports confirmations.
- · Undo restores from Trash, moves files back and sends files the agent created to Trash. It never overwrites.
- · The log is tamper-evident, using a hash chain. That makes changes detectable, not impossible.
Frequently Asked Questions
What is a local file conversion MCP server?
MCP lets an AI agent call tools. A local server runs those tools on your own computer, instead of sending files to a hosted API. FileHop serves its tools from the desktop app.
Which agents work with FileHop?
Claude Code, Codex, Claude Desktop, Cursor, VS Code, Windsurf and Gemini CLI have Connect in Settings. Other MCP clients can use the copied config.
Do my files stay on my computer?
FileHop's processing runs locally. But a cloud agent's provider receives whatever the agent reads, so share only folders you're comfortable with.
Can an agent delete my files?
With FileHop's tools, delete means moving files to the OS Trash, and each call can be undone from the activity log. FileHop can't control an agent's own shell commands.
Can agents edit Word or Excel files?
Not through FileHop today. They can extract text, convert and work with data files.
Does FileHop include an AI model?
No. FileHop runs no model. You connect the agent you already use.
Is the log tamper-proof?
No. It's tamper-evident: a hash chain shows whether entries changed. Anything running as your user could still rewrite it.
Can I limit which tools are available?
Yes. Each toolset can be switched on or off in Settings.
Connect your agent to FileHop
Available for Mac and Windows.
Download FileHop Free