Filesystem (local) logo

Filesystem (local)

Beta

The reference MCP server for reading, writing, moving and searching files in the directories named on its command line.

  • Developer Tools
  • Local
Runs
On the developer's Mac
Launched with
npx, Docker
Platform
macOS
Publisher
Model Context Protocol

How it works

Every agent request passes through Ferentin policy before it reaches Filesystem (local).

It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y @modelcontextprotocol/server-filesystem or docker run -i --rm mcp/filesystem.

Ferentin's endpoint agent finds Filesystem (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.

  1. AI agentAsks for something
  2. Ferentin policies
  3. Filesystem (local) MCP serverRuns on the developer's Mac
  4. Governed resultChecked, logged, returned

About Filesystem (local)

The reference MCP server for reading, writing, moving and searching files in the directories named on its command line.

Frequently asked about Filesystem (local)

How do I connect Filesystem (local) to Ferentin?
Enroll your Macs with the Ferentin endpoint agent, then add Filesystem (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
Is the Filesystem (local) integration generally available?
The Filesystem (local) integration is currently beta on Ferentin.