Filesystem MCP

Filesystem MCP server, bridged over HTTP with supergateway (baked into the image) so any MCP client that speaks HTTP/SSE can use it.

  • AI
  • Tools & Utilities
Filesystem MCP server, bridged over HTTP with supergateway (baked into the image) so any MCP client that speaks HTTP/SSE can use it. Exposes whatever directory you mount, read-write by default - mount read-only (:ro) if you only want it browsing/reading.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

36/100 Low

Maintained
69last commit 65 days ago
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
1016 GB minimum RAM

Availability: platform listings confirmed today, links checked 24 days ago

GitHub stars
0
Open issues
0
Last commit
2026-09-17
Activity
stale

Checked 8 days ago - source: GitHub (louij2/filesystem-mcp)

Resources & Compatibility

Minimum requirements: 16 GB RAM, 8 CPU core(s). ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install fsspec before starting Run the standard fsspec installation shown on this page before starting filesystem-mcp, because it supplies the code that opens folders and files. Without it, the app can't access or cache your files. source
  • Build or pull the image Pull louij2/filesystem-mcp from Docker Hub, or build locally from the repo with: docker build -t filesystem-mcp:latest . The image is based on louij2/docker-mcp, which provides the stdio-to-HTTP bridge. source
  • Build order If rebuilding from source instead of pulling, build the base image louij2/docker-mcp:latest first. source

Fetched 16 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need to build the base docker-mcp image before building filesystem-mcp?

If you are rebuilding the image family from scratch, build louij2/docker-mcp first. filesystem-mcp is built FROM louij2/docker-mcp:latest, so you can also pull the base image instead.

What package must be present before starting filesystem-mcp?

Install fsspec before starting filesystem-mcp. It supplies the code that opens folders and files, and without it the app cannot access or cache files.

How do I choose between read-only and read-write file access?

Mount the directory tree you want exposed as read-only or read-write and point the server at it. The upstream package README documents the CLI args.

How does the container expose the filesystem MCP server to clients?

The image uses the shared stdio-to-HTTP bridge pattern from docker-mcp. The docker-mcp README documents that pattern.

Answers sourced from filesystem-spec.readthedocs.io, github.com

Community

Collected 53 days ago - public community threads