Labsco
MCP SERVER

Readonly Filesystem MCP Server

by danielsuguimoto

Give an agent your project directory to read, and nothing to write with.

Local Filesystem Access
Summary
The filesystem server with the destructive half removed.

These are the tools you reach for when an agent has to read a codebase, partial reads, multi-file reads, recursive search, with the write path absent rather than merely discouraged. The directory list you pass on the command line is still what decides how much is on the table.

What it is

A read-only fork of the reference filesystem server. It reads, lists, searches and describes files inside the directories you name on the command line, and it carries no write, move or delete tool at all.

What you get
  • A file's contents as text, whole or between a from and to line number (read_file)
  • Several files in one call, where one failed read does not abort the rest (read_multiple_files)
  • A directory listing with [FILE] and [DIR] prefixes (list_directory)
  • A recursive, case-insensitive search with glob excludePatterns, returning full paths to matches (search_files)
  • Size, creation, modified and access times, type and permissions for a path (get_file_info)
  • The directories this server is allowed to touch (list_allowed_directories)
Requirements

Npx -y @danielsuguimoto/readonly-server-filesystem followed by each directory you want exposed; it will not operate outside them. Under Docker, mount those directories at /projects and add the ro flag.

Setup effort

One command — npx -y @danielsuguimoto/readonly-server-filesystem