Filesystem Official

Give an agent scoped read and write access to directories you choose.

LLM Mart 29 views 5k listing impressions

The reference filesystem server, and the one most people meet first. It exposes reading, writing, moving and searching files as MCP tools, restricted to the directories you list when you start it.

Why the scoping matters more than the features

An agent with unscoped filesystem access is an agent that can read your SSH keys because a web page told it to. The allow-list is the whole security model here: the server refuses paths outside it, so the blast radius of a bad instruction is whatever you handed over and nothing else. Point it at a project directory, not at a home directory.

Where it fits

Best for an agent that has to work across a codebase or a document set — reading several files to answer, then writing the change back. If all you need is "read this one file", your client probably already does that without a server.

Worth knowing

  • Writes are real and immediate. Run it against a directory under version control, so a wrong edit is a git diff rather than an archaeology exercise.
  • Search is content-based and will happily read every file in scope; a directory with a large node_modules in it is a slow directory.

Related servers

PostgreSQL Official

Let an agent inspect a Postgres schema and run read-only queries.

stdio
@modelcontextprotocol/server-postgres 39 views
Fetch Official

Fetch a web page and hand the agent readable text instead of raw HTML.

stdio
mcp-server-fetch 33 views
Git Official

Read repository history, diffs and branches as tools an agent can call.

stdio
mcp-server-git 27 views

Read-only MCP server for the OrchestKit docs: full-text search + Markdown fetch. No auth.

24 views