RunLocalAI
server
Open source
free (OSS, MIT)

MCP Filesystem Server

Anthropic's reference MCP server for filesystem access. Read, write, search, move, and list files inside a configured allowlist of directories. The canonical example for understanding how MCP tool exposure works in practice — most third-party MCP servers borrow its argument-validation patterns.

By Fredoline Eruo·Last verified May 6, 2026·60,000 GitHub stars

Overview

Anthropic's reference MCP server for filesystem access. Read, write, search, move, and list files inside a configured allowlist of directories. The canonical example for understanding how MCP tool exposure works in practice — most third-party MCP servers borrow its argument-validation patterns.

Stack & relationships

How MCP Filesystem Server relates to other entries in the catalog — recommended pairings, alternatives, dependencies, and edges to avoid. Each edge carries a one-line operator note from our editorial team.

MCP Filesystem Server ↔ ecosystem

Recommended stack

  • Commonly deployed with
    Claude Desktop

    The reference deployment example for MCP. Configure filesystem allowlists in Claude Desktop's MCP config; the server starts on app launch.

  • Commonly deployed with
    Claude Code

    Same wiring as Claude Desktop. Most agent workflows that need local-file access pull this server in.

  • Pairs with
    MCP Git Server

    Together they give an agent full local-repo awareness — filesystem reads files, git reads metadata (status / diff / log / blame).

Featured in these stacks

The L3 execution stacks that pick this tool as a recommended component, with the one-line note explaining the role it plays in each.

  • Stack · L3·Workstation tier·Role: File access (the agent's hands on the codebase)
    Build a local coding-agent stack (May 2026)

    The Anthropic reference filesystem MCP server with strict directory allowlisting. Required for OpenHands to read and write project files; allowlist limits blast radius when the agent goes off the rails.

  • Stack · L3·Workstation tier·Role: MCP filesystem (file access with allowlisting)
    Build a memory-enabled local agent stack (May 2026)

    Strict directory allowlist limits the agent's blast radius. Required for any agent that edits files; non-optional for a memory-enabled agent that may take destructive actions based on remembered context.

Pros

  • Anthropic-maintained reference implementation
  • Strict directory allowlisting prevents path-escape attacks
  • Stdio + remote transport support

Cons

  • No content-type heuristics — large binary files come through raw
  • Requires per-directory configuration for each project

Compatibility

Operating systems
macOS
Linux
Windows
GPU backends
n/a
LicenseOpen source · free (OSS, MIT)

Get MCP Filesystem Server

Official site
https://modelcontextprotocol.io
GitHub
https://github.com/modelcontextprotocol/servers

Frequently asked

Is MCP Filesystem Server free?

MCP Filesystem Server has a paid tier (free (OSS, MIT)). Check the pricing page for current terms.

What operating systems does MCP Filesystem Server support?

MCP Filesystem Server supports macOS, Linux, Windows.

Which GPUs work with MCP Filesystem Server?

MCP Filesystem Server supports n/a. CPU-only inference is also possible but slow.

Reviewed by RunLocalAI Editorial. See our editorial policy for how we evaluate tools.