# Filesystem [Health: Active]

**Category:** 📂 File Systems  
**Repository:** https://github.com/domdomegg/filesystem-mcp.git  
**GitHub Stars:** 3  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/filesystem-2

## Description
MCP server for filesystem operations - read, create, and edit files

## Tools
Capabilities this server exposes over MCP:

- **view** — Read file contents or list directory (with line numbers)
- **create** — Create or overwrite a file
- **str_replace** — Replace an exact string in a file
- **insert** — Insert text at a specific line

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "filesystem": {
    "command": "npx",
    "args": ["-y","filesystem-mcp"]
  }
}
```

## Documentation

## What the Filesystem MCP server does

The Filesystem MCP server exposes a small set of file and directory operations through MCP. Its `view` tool reads a file or lists a directory, while including line numbers when displaying file content. The `create` tool writes a new file or replaces the contents of an existing one.

Two editing tools handle targeted changes. `str_replace` looks for an exact string in a file and replaces it. `insert` adds text at a selected line. Together, these operations support both full-file generation and narrow edits to existing documents, configuration, or source code.

Typical workflows include saving email attachments into a local folder, producing a Markdown report from information gathered by another service, changing a value in a configuration file, or renaming a function with an exact replacement. A client can also read a file and create a separate copy before making changes.

## How it works

An MCP-compatible AI client invokes one of the four exposed tools with the target path and the operation-specific content or text. `view` is used for inspection, `create` for full writes, `str_replace` for exact substitutions, and `insert` for line-based additions. The tools can be combined in a sequence: inspect a file, apply a targeted edit, or write a new result to disk.

The server is intended for operations on the filesystem available to the client environment. The README examples describe local folders, project files, notes, source code, and shell configuration files as possible targets. External information sources such as email or calendars are part of example workflows involving other tools; they are not listed as capabilities of this server.

## Setup and configuration

Use the linked `install-mcp` setup instructions to generate the configuration for an MCP client. The README specifically names Claude Code, Claude Desktop, Cursor, Cline, and VS Code, and notes that the installer supports additional clients.

For repository development, the documented prerequisites are Git and Node.js. After cloning the repository, install dependencies with `npm install`, run tests with `npm run test`, and build with `npm run build`. These commands describe contribution and build work rather than a required end-user workflow.

## Tools and capabilities

- `view`: Read file contents or list a directory, with line numbers for file content.
- `create`: Create a file or overwrite an existing file.
- `str_replace`: Replace an exact string in a file.
- `insert`: Insert text at a specific line.

## Limitations and notes

The Filesystem MCP server documents file and directory operations only. It does not document built-in Gmail, calendar, email attachment, or source-control integrations. Those systems may appear in example workflows where another tool supplies information, but they should not be treated as functions exposed by this server.

Releases follow semantic versioning, and publishing is handled through the project’s Node package workflow.

_Full upstream README: https://allmcps.com/mcp/filesystem-2/readme_